I registered a few devices via Self Service and the Device Compliance to our Azure AD. The registration process is fine and the devices show up after 2-3 min in Azure, but it takes many hours or a day that the device is marked as compliant? There is just "N/A". As long as the status isn't marked as compliant the user can't access apps which are restricted to company devices that must be compliant.
Does somebody have the same issues? I think it is not related to AzureAD because Jamf checks the compliance criteria by itself and send it to AAD. The devices are listed in the Smart Group with the compliance criteria's.
Update: As you can see in the following image, the device was not updated until the next day. The screenshot is from the AAD Audit Log.
First the device is marked as "managed" and on the next day as "compliant".
Thanks for your reply. Yes, if I registered my own Device it was marked as compliant within minutes in AAD. So I'm wondering why this is happening now.
This workflow would be pretty "inelegant" if we tell new colleagues that they have to wait hours or a day after registration to use their new IPhones. The IPhones were in use after registration.
Any ideas how to trigger the compliance update or maybe a workaround?