2.3.3. Conditional Access That Requires Compliance
💡 First Principle: Conditional Access is where a compliance verdict becomes a consequence. It runs after the user's first authentication factor, reads signals about the user, the app and the device, and applies a grant control. Requiring a compliant device makes Intune's health check the price of admission — but only for the users, apps and platforms the policy actually targets.
Conditional Access needs Microsoft Entra ID P1, or a plan that includes it such as Microsoft 365 Business Premium. Policies live in the Microsoft Entra admin center under Entra ID > Conditional Access, and creating them requires at least the Conditional Access Administrator role. If Conditional Access licenses lapse, existing policies keep working but can't be updated.
Building the policy. Microsoft's recipe for requiring compliant devices is short:
- Create the Intune compliance policies first, and confirm at least one device reports compliant — otherwise the Conditional Access policy won't work as intended.
- Users: All users, excluding break-glass (emergency access) accounts and the Directory Synchronization Accounts role.
- Target resources: All resources.
- Grant: Require device to be marked as compliant.
- Enable the policy in Report-only mode first, review the impact, then switch it on.
What counts as compliant. A device must be registered in Entra ID before it can be marked compliant, and the grant supports Windows 10 and later, iOS, Android, macOS and Linux Ubuntu devices that are registered and enrolled in Intune. Intune can mark any of those platforms compliant; a non-Microsoft MDM partner can do so for Windows devices. On iOS, Android, macOS and some browsers, the device proves itself with a client certificate issued at registration, which the user selects on first browser sign-in. A Windows sign-in from Edge InPrivate counts as noncompliant, and the device-code sign-in flow can't satisfy device controls at all.
Combining grants. When a policy selects several grant controls, the default is Require all the selected controls. Require one of the selected controls creates softer alternatives that Microsoft itself suggests, such as "compliant device or hybrid joined device or MFA" for all users. The Require Microsoft Entra hybrid joined device grant works only for domain-joined Windows devices.
| Grant configuration | Compliant corporate laptop | Personal tablet, not enrolled, user completes MFA |
|---|---|---|
| Require device to be marked as compliant | Granted | Blocked |
| Require MFA and compliant device (Require all) | Granted after MFA | Blocked |
| Require MFA or compliant device (Require one) | Granted | Granted |
Side effects to plan for. The compliant-device grant doesn't block Intune enrollment itself, so users can still enroll a device to become compliant. Corporate Android enrollment authenticates in a Chrome tab, so exclude the Microsoft Intune cloud app from Android policies that require compliance or block. The Windows Enrollment Status Page can time out when a compliant-device policy covers all cloud apps on Windows while Store apps are tracked during setup; target compliance to devices or use offline licensing. For guests, cross-tenant access settings can trust a partner tenant's device compliance claims.
A related user action closes the loop from 2.1.2: a Conditional Access policy targeting Register or join devices can require MFA before anyone adds a device to the tenant.
⚠️ Exam Trap: A "require compliant device" policy doesn't catch devices that have no compliance policy assigned. The tenant setting Mark devices with no compliance policy assigned as defaults to Compliant, so a device that slipped through your assignments passes the grant. In a tenant that relies on Conditional Access, change that setting to Not compliant.
Reflection Question: You enable a policy that requires a compliant device for all users and all resources, and within an hour your directory synchronization account starts failing its sign-ins and a warehouse's Android devices can't finish enrollment. Which two exclusions did the policy miss, and what step would have shown you both problems before users noticed?