🔒 Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided MD-102 Domain 1
Domain 1 — Module 6 of 7 86%
6 of 27 overall

MD-102 Study Guide

Domain 1: Prepare Infrastructure for Devices

  • Device Identity: Join, Register & Hybrid Free
  • Build the Right Device Groups
  • Intune Enrollment Essentials Free
  • Auto-Enrollment & Bulk Enrollment
  • Intune RBAC & Windows Hello for Business
  • Compliance Policies & Conditional Access
  • Windows LAPS & Local Group Management

Domain 2: Manage and Maintain Devices

  • Windows Autopilot: Choose Your Path Free
  • Autopilot: Device Names, ESP & Rollout
  • Provisioning Packages & Windows 11 Upgrades
  • Windows 365: Your PC in the Cloud
  • Configure Windows Devices with Intune
  • Config Profiles: Android, iOS & macOS
  • Control Admin Rights with EPM
  • Intune Suite: Apps, Analytics & Remote Help
  • Cloud PKI & Tunnel for MAM
  • Remote Actions & Device Queries

Domain 3: Manage Applications

  • App Deployment: Prepare & Package
  • Deploy Apps with Intune & App Stores
  • Microsoft 365 Apps: Deploy, Customize & Manage
  • App Protection Policies & Conditional Access
  • App Configuration: Managed Apps & Managed Devices

Domain 4: Protect Devices

  • Endpoint Security: Antivirus, Firewall & Encryption
  • Attack Surface Reduction & Security Baselines
  • Defender for Endpoint: Integrate & Onboard
  • Plan and Manage Windows Updates
  • Cross-Platform Updates & Delivery Optimization

MD-102 Study Guide

Domain 1: Prepare Infrastructure for Devices

  • Device Identity: Join, Register & Hybrid Free
  • Build the Right Device Groups
  • Intune Enrollment Essentials Free
  • Auto-Enrollment & Bulk Enrollment
  • Intune RBAC & Windows Hello for Business
  • Compliance Policies & Conditional Access
  • Windows LAPS & Local Group Management

Domain 2: Manage and Maintain Devices

  • Windows Autopilot: Choose Your Path Free
  • Autopilot: Device Names, ESP & Rollout
  • Provisioning Packages & Windows 11 Upgrades
  • Windows 365: Your PC in the Cloud
  • Configure Windows Devices with Intune
  • Config Profiles: Android, iOS & macOS
  • Control Admin Rights with EPM
  • Intune Suite: Apps, Analytics & Remote Help
  • Cloud PKI & Tunnel for MAM
  • Remote Actions & Device Queries

Domain 3: Manage Applications

  • App Deployment: Prepare & Package
  • Deploy Apps with Intune & App Stores
  • Microsoft 365 Apps: Deploy, Customize & Manage
  • App Protection Policies & Conditional Access
  • App Configuration: Managed Apps & Managed Devices

Domain 4: Protect Devices

  • Endpoint Security: Antivirus, Firewall & Encryption
  • Attack Surface Reduction & Security Baselines
  • Defender for Endpoint: Integrate & Onboard
  • Plan and Manage Windows Updates
  • Cross-Platform Updates & Delivery Optimization
Domain 1: Prepare Infrastructure for Devices Premium ⏱ ~13 min read

Compliance Policies & Conditional Access

Compliance policies define the rules devices must follow. Conditional access enforces those rules by blocking non-compliant devices from company resources. Together, they're the backbone of Zero Trust device management.

What is a compliance policy?

☕ Simple explanation

Think of compliance policies like a building health and safety inspection.

The inspector has a checklist: fire exits clear? Smoke alarms working? Electrical wiring up to code? If you pass, you get your certificate. If you fail, you get a notice to fix the issues — and the building might be shut down until you do.

Compliance policies are the checklist for devices. Is the OS up to date? Is encryption turned on? Is there a passcode? If the device passes, it’s “compliant.” If it fails, it gets marked “non-compliant” — and conditional access can block it from accessing email, SharePoint, Teams, and everything else.

Intune compliance policies evaluate enrolled devices against a set of rules. Each rule checks a device property (OS version, encryption status, password complexity, jailbreak detection, etc.). Devices that meet all rules are marked compliant; devices that fail are marked non-compliant.

Compliance status alone doesn’t block anything — it’s just a label. The enforcement comes from Microsoft Entra Conditional Access, which can require devices to be compliant before granting access to cloud resources like Exchange Online, SharePoint, and Teams.

Compliance settings by platform

Chen Wei at Meridian Bank creates compliance policies for every platform in use. Each platform has different available settings:

FeatureWindowsiOS/iPadOSAndroidmacOS
Minimum OS versionYesYesYesYes
Password requiredYesYesYesYes
Password complexitySimple/alphanumeric/complexSimple/alphanumericNumeric/low/medium/highSimple/alphanumeric
Encryption requiredBitLockerBuilt-in (always on)Device encryptionFileVault
Firewall requiredYesNoNoYes
Antivirus requiredYes (Defender)NoNoNo
Jailbreak/root detectionNo (not applicable)YesYesNo
TPM requiredYesNoNoNo
Secure Boot requiredYesNoNoNo
Defender threat levelYesYesYesYes

Actions for non-compliance

When a device fails a compliance check, you don’t have to immediately block it. Intune supports a graduated response:

ActionTimingWhat Happens
Mark device non-compliantImmediately (or after grace period)Device status changes to non-compliant
Send email notificationAfter X daysUser receives an email explaining what’s wrong and how to fix it
Send push notificationAfter X daysNotification via Company Portal app
Retire deviceAfter X daysCompany data removed from device (nuclear option)

Example: Chen Wei configures: immediately mark non-compliant → Day 1: email user → Day 3: push notification → Day 14: retire device. This gives users time to fix issues before losing access.

💡 Exam tip: compliance policy without conditional access does nothing

A compliance policy on its own only labels a device as compliant or non-compliant. It doesn’t block access to anything.

To enforce compliance, you need a Conditional Access policy in Entra ID that says: “Require device to be marked as compliant.”

The exam may present a scenario where a compliance policy is configured but devices still access resources despite being non-compliant. The fix: add a conditional access policy that requires compliance.

Compliance policy = the rules. Conditional access = the enforcement.

Conditional access for compliance

How it works together

  1. Device enrolls in Intune
  2. Compliance policy evaluates the device → compliant or non-compliant
  3. User tries to access a cloud resource (e.g., Exchange Online)
  4. Conditional access checks: “Is this device compliant?”
    • Yes → access granted
    • No → access blocked (user sees a remediation message)

Creating a CA policy that requires compliance

In the Entra admin center → Protection → Conditional Access:

SettingConfiguration
NameRequire compliant device for M365 access
UsersAll users (exclude break-glass accounts!)
Cloud appsOffice 365 (covers Exchange, SharePoint, Teams, OneDrive)
ConditionsDevice platforms: Windows, iOS, Android, macOS
GrantRequire device to be marked as compliant
SessionDefault
ℹ️ Deep dive: compliance + CA for BYOD

For personal devices (Entra Registered/BYOD), the compliance check works differently:

  • If the device is enrolled in Intune → compliance policy evaluates normally
  • If the device is not enrolled → Intune can’t evaluate compliance, so the device is treated as non-compliant by default
  • This means: CA requiring compliance effectively forces enrollment for BYOD users who need access to M365 resources

Alternatively, you can use a CA policy that requires app protection policy instead of device compliance. This allows BYOD access through protected apps (Outlook, Teams, OneDrive) without requiring full device enrollment. This is Riko’s approach at Pixel and Co — creative designers with personal Macs don’t want full MDM on their devices.

Compliance policy settings in practice

Chen Wei’s Meridian Bank compliance policy (Windows)

SettingValueWhy
Minimum OS versionWindows 11 23H2Banking regulator requires recent OS
BitLocker requiredYesEncrypt all corporate data at rest
Firewall requiredYesNetwork protection
Antivirus requiredYesDefender must be active
TPM requiredYesHardware root of trust
Password minimum length12 charactersBanking security standard
Defender threat levelMedium or belowBlock high-risk devices
Grace period3 daysGive users time to update

Aroha’s CloudForge compliance policy (Windows)

SettingValueWhy
Minimum OS versionWindows 11 22H2Reasonable baseline for startup
BitLocker requiredYesProtect customer data
Password requiredYes (6+ characters)Basic security
Grace period7 daysStartup can be more flexible

Key exam concept: Compliance policies should match the organisation’s risk profile. A bank has stricter settings than a startup, but both need compliance + conditional access to enforce Zero Trust.

🎬 Video walkthrough

🎬 Video coming soon

Compliance Policies & Conditional Access — MD-102 Module 6

Compliance Policies & Conditional Access — MD-102 Module 6

~13 min

Flashcards

Question

What does a compliance policy do on its own (without conditional access)?

Click or press Enter to reveal answer

Answer

It only LABELS a device as compliant or non-compliant. It doesn't block access to anything. You need a conditional access policy that requires compliance to actually enforce access restrictions.

Click to flip back

Question

What are the four actions for non-compliance in Intune?

Click or press Enter to reveal answer

Answer

1. Mark device non-compliant (immediately or after grace period) 2. Send email notification 3. Send push notification 4. Retire device (remove company data). These can be scheduled at different time intervals.

Click to flip back

Question

Which platforms support jailbreak/root detection in Intune compliance policies?

Click or press Enter to reveal answer

Answer

iOS/iPadOS (jailbreak detection) and Android (root detection). Windows and macOS do not have jailbreak/root detection as they use different security mechanisms (TPM, Secure Boot, BitLocker, FileVault).

Click to flip back

Knowledge Check

Knowledge Check

Chen Wei creates a compliance policy requiring BitLocker encryption on all Windows devices. Two weeks later, he discovers that some devices without BitLocker are still accessing Exchange Online. What's the most likely cause?

Knowledge Check

Riko at Pixel & Co needs designers with personal Macs to access Outlook and Teams without enrolling their devices in Intune. Which conditional access approach should Riko use?

Knowledge Check

Chen Wei's compliance policy for iOS devices at Meridian Bank marks a device non-compliant on Day 0, emails the user on Day 1, sends a push notification on Day 3, and retires the device on Day 14. A user's iPhone is running an old iOS version. What happens on Day 5 if the user hasn't updated?


Next up: Windows LAPS & Local Group Management — securing local admin accounts and managing local group membership via Intune.

← Previous

Intune RBAC & Windows Hello for Business

Next →

Windows LAPS & Local Group Management

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.