R1X (@StackZen) profile picture

M365 | Intune | Entra ID | Linux | Shell Scripting | Python | Docker | Git | AWS | GCP | CCNA |

Joined February 2026
Part 2:Compliance policy+Conditional Access Compliance Policy =the judge. Conditional Access =the guard. Policy marks a device Compliant or Not. CA reads that mark and allows or blocks access. Trap: no policy assigned=Compliant by default.Change it. #Intune #ConditionalAccess
2
13
Eg:a laptop with BitLocker off tries to open Outlook. Compliance policy → Not compliant CA rule “Require compliant device” → access blocked User sees: “Your device must be managed /compliant” The user fixes BitLocker, the device re-checks in, and access comes back automatically
9
Learning Intune in my Hyper-V lab, here’s what clicked: Compliance policy ≠ enforcement. It only gives a device a “Compliant / Not compliant” tag. Without Conditional Access, nothing acts on that tag. Judge without a guard = no security. #intune #Microsoft
2
45
Nuance: a new device can show “Not compliant” or “Not evaluated” right after enrollment, before its first check-in. If CA requires compliance, users get blocked for a short time. That’s why many setups use a grace period or exclude the enrollment flow.
36