Intune problems are usually policy and timing problems
Microsoft Intune is powerful, but most rollout problems are not bugs — they are policy conflicts, assignment timing, or Conditional Access gates that block users before their device has caught up. The diagnostic discipline that resolves Intune incidents fastest is to trace the device’s journey: enrolment, profile assignment, compliance evaluation, and finally the Conditional Access decision. A problem at any stage produces a different symptom, and treating them all as “Intune is broken” wastes hours.
This article covers the problems I see most during Intune MDM implementations: devices stuck in pending, compliance policies that silently do not apply, Conditional Access locking out legitimate users, and BYOD MAM policies that misfire. For the rollout architecture and enrolment strategy, see the companion guide on Intune MDM implementation and policies.
Problem 1: Devices stuck in pending or failing to enrol
A device that stays in pending enrolment usually has one of three causes: the Autopilot profile has not been assigned to the device’s group, the device is not Entra ID joined during enrolment, or a network requirement (such as access to the Intune endpoints) is blocked. The diagnostic starting point is the device object in the Intune portal and the enrolment error code.
Common error codes point to specific causes: 0x80180014 means the device is not in an assigned group; 0x80192B0A is often a licensing or tenant issue; 0xC000005E points to a network or DNS problem reaching the Intune service. Resolve the named cause before re-attempting enrolment — retrying without a fix just regenerates the same error.
- Confirm the Autopilot profile is assigned to a group containing the device
- Verify the user has an Intune-licensed account and the device can reach Intune endpoints
- Check the enrolment error code in the device object before retrying
- For hybrid join, confirm the Intune connector for AD is healthy and syncing
Problem 2: Compliance policies silently not applying
A device shows as compliant when it should not — or non-compliant when it should — because compliance evaluation has not run or a conflicting policy exists. Intune evaluates compliance on a schedule (typically every 8 hours) and on check-in, so a recently changed policy may take hours to reflect. Forcing a sync from the device or the portal accelerates evaluation.
The subtler problem is conflicting compliance policies: two policies targeting the same device with different BitLocker or OS-version requirements produce an unpredictable merged result. Consolidate compliance into a single baseline policy per device group, and use the policy conflict report in the portal to find overlaps.
| Symptom | Cause | Resolution |
|---|---|---|
| Compliance not updating after a change | Evaluation interval not elapsed | Force a device sync or wait for the 8h cycle |
| Device compliant but blocked | Conditional Access using stale compliance | Re-evaluate compliance, then re-check CA |
| Inconsistent compliance across devices | Conflicting policies targeting same group | Consolidate into one baseline per group |
| BitLocker shows non-compliant | Attestation not reported to Entra ID | Verify TPM attestation and device health attestation |
Problem 3: Conditional Access blocking legitimate users
The most disruptive Intune problem is a Conditional Access policy that blocks access for users who should be allowed — typically because their device is compliant but the CA policy evaluated before compliance refreshed, or because the policy requires a compliant device for an app the user genuinely needs on an unmanaged device.
The diagnostic path is the Entra ID sign-in logs: find the failed sign-in, open the Conditional Access tab, and see which policy applied and why. If the policy required a compliant device and the device was non-compliant at sign-in time, the block is correct — the fix is to make the device compliant, not to weaken the policy. Use report-only mode to measure the impact of a new CA policy before enforcing it.
- Use the Entra ID sign-in logs to see which CA policy blocked a user and why
- Run new Conditional Access policies in report-only mode for a week before enforcing
- Exclude break-glass admin accounts from all Conditional Access policies
- Confirm compliance refreshed before assuming a CA block is wrong
Problem 4: BYOD MAM app protection policies not protecting data
For BYOD, app protection policies (MAM) protect corporate data inside managed apps without enrolling the personal device. The common failure is a policy that is assigned but not applied because the user’s app is not a managed (Intune-enrolled) app, or the policy’s data-transfer rules are too permissive.
Verify the policy targets the right groups and app platform, that the apps are Intune-enrolled (check the user’s app in the Company Portal or the managed apps list), and that the “Save copies of org data” and “Restrict cut, copy, and paste” controls are set to the required level. A policy that allows saving to personal storage defeats the purpose of MAM.
Connect-MgGraph -Scopes "DeviceManagementApps.Read.All"
$user = "user@contoso.com"
Get-MgUserManagedDevice -UserId $user |
Select-Object DeviceName, OperatingSystem, ComplianceState, LastSyncDateTime
# App protection policy status for the user
Get-MgDeviceAppManagementManagedAppRegistration -Filter "userId eq '<objectid>'"Trade-offs and next steps
Intune design balances security against user friction. A strict compliance baseline (BitLocker on, OS within N-2, healthy attestation) maximises security but can block users during a legitimate device issue; a permissive baseline avoids lockouts but weakens the access gate. The right balance is a realistic baseline with a grace period for non-compliance, paired with Conditional Access in report-only mode for any new policy.
When problems recur, the next step is usually to simplify: consolidate compliance into one baseline per device group, pilot every configuration profile before broad assignment, and tie compliance to Conditional Access so the access decision is consistent. For the broader identity and Conditional Access architecture, see the Entra ID SSO implementation guide.
- Use one compliance baseline per device group to avoid conflicts
- Add a grace period for non-compliance to avoid lockouts during device issues
- Pilot every configuration profile before broad assignment
- Tie compliance to Conditional Access for a consistent access gate
Lessons learned
- Trace the device journey: enrolment, profile, compliance, then Conditional Access
- Check the enrolment error code before retrying enrolment
- Use the Entra ID sign-in logs to diagnose Conditional Access blocks
- Run new CA policies in report-only mode before enforcing
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.