A macOS utility that makes troubleshooting Jamf Pro ↔ Microsoft Entra ID (Intune) Device Compliance integration significantly easier.
Instead of manually checking endpoints, tweaking hidden preferences, and digging through logs, this tool bundles the most common troubleshooting steps into a single interface.
Because sometimes the problem is complicated…
and sometimes it's just the network.
Troubleshooting Jamf Pro Device Compliance with Microsoft Intune usually looks like this:
- Check if the network is blocking something
- Apply known fixes documented by Jamf
- Dive into logs and hope they make sense
This tool brings that workflow into one place and complements the official Jamf documentation.
You should reach for Device Compliance Troubleshooter when:
- Users cannot complete Entra ID (Azure AD) sign-in during device registration
- You suspect network restrictions but want a quick and reliable way to verify required endpoints
- You want to quickly test JamfAAD-related fixes without manually modifying plists or profiles
- You need a fast way to validate configuration changes locally before deploying them at scale
- You want to generate and deploy a configuration profile based on working settings
If you're thinking:
"Something is off… but I don't know where to start"
This tool gives you a structured starting point.
The first and most common issue is network restrictions.
These can silently break communication with:
- Microsoft Entra ID
- Microsoft Graph
- Intune
- Device Registration Service
- Apple networking endpoints
The Network Test module performs quick connectivity checks against required endpoints.
login.microsoftonline.com
graph.microsoft.com
manage.microsoft.com
enterpriseregistration.windows.net
device.login.microsoftonline.com
You can also add custom endpoints to match your environment.
Because if the network is broken, it's better to know immediately.
Jamf has identified several configuration tweaks that resolve common issues with Device Compliance authentication. These fixes are described in the official Jamf documentation.
- Use WKWebView for sign-in
- Retry token validation during JamfAAD check-in
- Disable UPN login hint
Apply them locally with one click and validate immediately.
Once you find a working setup:
- Generate a configuration profile
- Download it as
.mobileconfig - Upload it directly to Jamf Pro via API
No more manual profile building.
When everything else fails:
- Stream
jamfAADlogs - Search and filter logs
- Enable
logPIIfor deeper debugging
jamfAAD is not very talkative.
But when you're in a pinch, even a single log line can be enough.
Troubleshooting Device Compliance usually means:
- jumping between documentation
- testing endpoints manually
- building configuration profiles
- parsing logs in Terminal
- questioning your life choices
This tool puts everything into one place.
This tool is not an official Jamf product.
Use at your own risk — but hopefully with much less frustration.
Device Compliance Troubleshooter was created by the Apple Business Unit at Inetum Polska Sp. z o.o.
It is licensed under the Apache License, version 2.0.