2.3.2. Compliance Policies Across Platforms
💡 First Principle: A compliance policy turns "is this device healthy enough?" into a recorded verdict, on a schedule you control. Because the verdict and its consequences are separate, you can measure first and enforce later, give users time to fix problems, and combine health signals from Windows, mobile platforms and Defender into one state that Conditional Access can read.
You create policies at Devices > Manage devices > Compliance > Create policy, for Android device administrator, AOSP, Android Enterprise, iOS/iPadOS, Linux, macOS and Windows 10 and later. Licensing is Intune alone; Conditional Access adds the Microsoft Entra ID P1 requirement. Assign policies to user groups (all of a user's devices are checked) or device groups (cleaner reporting) — Linux policies go to device groups only.
Windows settings fall into a few families:
- Device Health (Windows Health Attestation): Require BitLocker, Require Secure Boot, Require code integrity. BitLocker health is measured at boot, so a freshly encrypted device may need a reboot before it reports compliant. Devices without TPM 2.0 report not compliant for Secure Boot.
- Device properties: minimum and maximum OS versions in major.minor.build.revision form, or a list of valid OS build ranges.
- System security: password rules, Encryption of data storage on a device (a weaker OS-drive check than Require BitLocker), Firewall, TPM, antivirus and antispyware.
- Microsoft Defender: antimalware, minimum version, up-to-date security intelligence, real-time protection, and Require the device to be at or under the machine risk score (Clear, Low, Medium or High) when Defender for Endpoint is connected.
Windows also evaluates certain settings in near real time — firewall, antivirus, BitLocker, Defender status, OS build, real-time protection and Secure Boot — requesting re-evaluation when local state changes. A Group Policy that disables the firewall overrides Intune, and a policy requiring the firewall then reports not compliant.
iOS/iPadOS policies can block jailbroken devices, require a minimum OS build (including Rapid Security Response builds), set a mobile threat defense level, and mark devices noncompliant when a listed restricted app is installed. Android Enterprise policies have separate profiles for corporate devices (fully managed, dedicated, COPE) and personally owned work profiles; they check the Play Integrity verdict, rooted devices, minimum OS and a minimum security patch level. On Android 12 and later, use Password complexity (None, Low, Medium, High), because Google deprecated the older password type and length settings for personal work profiles.
Actions for noncompliance set what happens and when. Every policy includes Mark device noncompliant at 0 days — immediate — and you can't remove it, only reschedule it to create a grace period. Schedules run from 0 to 365 days in 0.25-day steps (0.25 days is 6 hours).
| Action | Platforms | What to know |
|---|---|---|
| Mark device noncompliant | All | Always present; reschedule to add a grace period |
| Send email to end user | All | Uses a notification template; can copy Entra groups |
| Send push notification to end user | Android DA, Android Enterprise, iOS/iPadOS | Delivery isn't guaranteed |
| Remotely lock the noncompliant device | Android, iOS/iPadOS, macOS | Not Windows |
| Add device to retire list | Android, iOS/iPadOS, macOS, Windows | Nothing is retired until an admin acts on the list |
Worked example of a grace period. You schedule Mark device noncompliant at 3 days. A laptop fails the BitLocker check at 09:00 on Monday. Until 09:00 on Thursday it reports InGracePeriod; after that it reports NonCompliant. When several policies apply, the most severe status wins, in this order: Unknown < NotApplicable < Compliant < InGracePeriod < NonCompliant < Error. A device that is Compliant for one policy and InGracePeriod for another therefore shows InGracePeriod.
Two tenant-wide settings from Phase 1 frame all of this, at Endpoint security > Device compliance > Compliance policy settings: Mark devices with no compliance policy assigned as (Compliant by default) and the Compliance status validity period (30 days by default, 1 to 120).
⚠️ Exam Trap: A red "Not compliant" in the admin center is a verdict, not a block. The compliance policy only evaluates and reports; access is blocked by a Microsoft Entra Conditional Access policy whose grant requires a compliant device. If a scenario says noncompliant devices still open SharePoint, the missing piece is the Conditional Access policy, not a stricter compliance setting.
Reflection Question: A user's laptop fails the "Require BitLocker" check right after encryption finishes, and a second laptop shows InGracePeriod even though one of its two policies reports Compliant. Explain both results.