Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

1.2.2. Compliance as the Bridge to Access

💡 First Principle: A compliance policy is a health check, not a lock. It evaluates a device against your rules and records a verdict; a separate system, Microsoft Entra Conditional Access, reads that verdict at sign-in and decides whether to let the user reach company resources. Splitting judgement from enforcement lets you measure first, then enforce.

Here's the chain in a real sign-in. A user opens Outlook on their laptop. Microsoft Entra ID evaluates the Conditional Access policies that apply to the user and the app. One policy requires the device to be marked as compliant. Entra ID looks up the device's compliance state, which Intune last recorded when the device checked in. If the device is compliant, access is granted; if it's noncompliant — or isn't enrolled and so has no compliance state at all — access is blocked.

Three defaults shape how that chain behaves, and each is a favorite exam detail:

  • Devices with no compliance policy assigned are marked Compliant by default. The tenant setting Mark devices with no compliance policy assigned as defaults to Compliant; Microsoft recommends changing it to Not compliant when you rely on Conditional Access, or a device that slipped through your assignments will pass.
  • Compliance has a validity period. A device that doesn't report within the Compliance status validity period — 30 days by default, configurable from 1 to 120 — becomes noncompliant, so long-abandoned devices stop counting as healthy.
  • Noncompliance has a schedule. A compliance policy's actions for noncompliance decide what happens and when: marking the device noncompliant (immediately by default, or after a grace period you schedule), emailing the user, sending a push notification to a mobile device, remotely locking a mobile device and adding the device to a retire list that an admin then acts on. A grace period gives users time to fix a problem before they lose access.

Compliance signals can also come from outside Intune. When Microsoft Defender for Endpoint is connected, a compliance policy can require the device to be at or under a machine risk score, so a device Defender considers high-risk becomes noncompliant and Conditional Access cuts it off. That is Zero Trust in practice: verify explicitly at every sign-in, using live device health instead of network location.

⚠️ Exam Trap: If a scenario says noncompliant devices can still reach Exchange Online, the missing piece is almost never the compliance policy — it's the Conditional Access policy that requires a compliant device, or the default that marks unassigned devices as compliant.

Reflection Question: You assign a compliance policy that requires BitLocker to all Windows devices and see 40 devices marked noncompliant, yet those users can still open SharePoint. What two separate configurations could explain it, and which portal holds each?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned