Intune device not compliant

This can happen when the device record and the detailed compliance evaluation are not fully aligned yet.

Supported causes from Intune documentation:

1. The device hasn’t checked in recently
   Intune notes that if a device hasn’t checked in since the compliance policy was updated, the device can show Not evaluated or have stale compliance information. In the Troubleshoot pane, Last check in should be recent. By default, Intune devices check in every 8 hours, and if Last check in is more than 24 hours old, there may be an issue with the device.
2. A compliance setting previously reported Error
   Intune can keep access behavior and compliance transitions for several days when a setting goes into Error. For example, a device can remain effectively noncompliant after an error until compliance evaluation completes successfully again.
3. Encryption-related delay
   If the compliance policy requires device encryption, a Windows device can show Not compliant while BitLocker encryption is still finishing. After encryption completes, the device shows Compliant.
4. Different views show different levels of detail
   In Intune, the device overview status and the policy details/report views are separate reporting surfaces. The detailed policy view can show a policy as Compliant while the device summary still reflects an older overall state until the next successful sync/evaluation.

Practical checks:

1. In Intune admin center, open the device and verify Last check-in is recent.
2. On the Windows device, force a sync: Settings > Accounts > Access Work or School > select the work account or MDM enrollment > Info > Sync.
3. In Intune, review Devices > Compliance > Monitor and check the device in the compliance reports.
4. If encryption is required, confirm BitLocker encryption has fully completed.
5. If the issue remains after the next check-in cycle, use the built-in Intune troubleshooting view to inspect Intune compliant, Microsoft Entra compliant, and policy-specific compliance state.

If the detailed policy state is already Compliant, the most likely explanation is a reporting delay or stale device summary status that should update after sync/check-in.

• Monitor results of your Intune Device compliance policies
• BitLocker-encrypted Windows 10 device shows as Not compliant in Intune
• Monitor results of your Intune Device compliance policies
• Troubleshooting policies and profiles in Microsoft Intune