Forum Discussion
Device In Azure AD showing as not compliant, yet in Intune the device is fine and compliant
Hello All I have several devices that are now failing SSO logins because of Conditional Access retuning as the device is not Compliant, Checking the device in Azure AD (Entra) is clearly show...
My understanding from speaking to a Microsoft engineer is that the Intune database and Azure AD (Entra ID) database are separate, and that there is a sync between that two, this can be anywhere between 5-15 minutes, however I have seen this take as long as 2 hours. As far as I know, there is no way to force the databases to sync globally, or from the UI.
Has anyone figured out the reason or fix for this? I am having the issue where the device was reporting compliance just fine now it says the device isn't compliant in the CA logs however when you go to the device in azure it shows it is compliant
pdantro Someone has posted a fix above but its more of a workaround since Microsoft haven't fixed it/ established a cause.
i.e. Make a compliance policy that's impossible to achieve, let everything become non compliant, then revert the compliance policy to desired settings. (That's how I personally fixed it too)
