Did you register your iPad with Microsoft authenticator for Device Compliance?
Hello,
Jamf to EntraID typically isn’t immediate. Depending on your sync settings and the systems involved, it can take anywhere from a few minutes to a few hours for the compliance status to be reflected in EntraID. This delay could be due to the time it takes for Jamf to communicate with Intune (if you're using that as the MDM solution) and then for Intune to update EntraID. For iPadOS/iOS devices, ensure the device is fully enrolled in Jamf and has the appropriate compliance policies pushed to it. If the device was added to the Jamf smart group but the compliance status still shows as "n/a" in EntraID, it could be due to an issue with the initial sync or enrollment.
While there isn’t a direct "push" feature between Jamf and EntraID, there are a few methods that might help you force the sync:
Trigger a manual sync in Jamf: Go to your Jamf Pro dashboard, navigate to the device, and look for options to sync or refresh the device status. This may kick off a re-evaluation of the device status.
Check Intune Sync: If you’re using Intune for MDM management, ensure that Intune is properly syncing device compliance with EntraID. You may need to go into the Intune Admin Center and manually trigger a sync or review the sync settings.
Re-enroll the device: As a last resort, you could try unenrolling and re-enrolling the test device to see if that resets the compliance status. This often helps clear any stale status info. Check the Jamf logs and EntraID logs (in the Azure portal) for any errors or warnings about the sync process. Sometimes there are communication issues or misconfigurations that could be silently blocking the sync.
Did you register your iPad with Microsoft authenticator for Device Compliance?
yes using the self service Register policy.
Hello,
Jamf to EntraID typically isn’t immediate. Depending on your sync settings and the systems involved, it can take anywhere from a few minutes to a few hours for the compliance status to be reflected in EntraID. This delay could be due to the time it takes for Jamf to communicate with Intune (if you're using that as the MDM solution) and then for Intune to update EntraID. For iPadOS/iOS devices, ensure the device is fully enrolled in Jamf and has the appropriate compliance policies pushed to it. If the device was added to the Jamf smart group but the compliance status still shows as "n/a" in EntraID, it could be due to an issue with the initial sync or enrollment.
While there isn’t a direct "push" feature between Jamf and EntraID, there are a few methods that might help you force the sync:
Trigger a manual sync in Jamf: Go to your Jamf Pro dashboard, navigate to the device, and look for options to sync or refresh the device status. This may kick off a re-evaluation of the device status.
Check Intune Sync: If you’re using Intune for MDM management, ensure that Intune is properly syncing device compliance with EntraID. You may need to go into the Intune Admin Center and manually trigger a sync or review the sync settings.
Re-enroll the device: As a last resort, you could try unenrolling and re-enrolling the test device to see if that resets the compliance status. This often helps clear any stale status info. Check the Jamf logs and EntraID logs (in the Azure portal) for any errors or warnings about the sync process. Sometimes there are communication issues or misconfigurations that could be silently blocking the sync.
Thank you justin06coston. We will take a look at these steps and see how it goes.
