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.

2.3.2. Conditional Access Policies

💡 First Principle: Conditional Access is a policy engine that evaluates signals about a sign-in attempt — who is signing in, from what device, from where, at what risk level — and then decides: grant access, grant with additional requirements, or block. It's the automated security checkpoint that enforces context-aware access decisions at scale.

Without Conditional Access, every user who passes authentication gets the same level of access, regardless of whether they're on a managed corporate device or an unknown personal machine in a foreign country. Conditional Access lets you say: "Users signing in from trusted locations on compliant devices get seamless access. Everyone else must complete MFA. Users signing in at high risk level are blocked entirely."

A Conditional Access policy has two parts:

Conditions (the "if" side):
  • Users or groups targeted
  • Cloud apps included or excluded
  • Sign-in risk level (low / medium / high — from Entra ID Protection)
  • Device platform (Windows, iOS, Android)
  • Location (named locations, countries)
  • Device compliance state (Intune-managed, compliant)
Controls (the "then" side):
  • Require MFA
  • Require compliant device
  • Require Entra hybrid joined device
  • Block access
  • Require approved client app
  • Require password change (for high-risk sign-ins)

Testing before enforcing. A policy in Report-only mode is evaluated at every sign-in and the result it would have had is logged, but nobody is blocked or prompted. The What If tool simulates a sign-in by a chosen user, app, device platform and location and lists the policies that would apply, without touching real users. After the fact, the Conditional Access tab of a sign-in event in the Entra sign-in logs shows each policy that applied and its result. A broad policy aimed at all users and all cloud apps, enforced without testing and without an excluded emergency access account, is the classic way to lock everyone out, administrators included.

Emergency access (break-glass) accounts. Microsoft recommends two or more cloud-only accounts that hold the Global Administrator role, are protected by a strong, phishing-resistant sign-in method stored securely, and are used only in an emergency. At least one of them is excluded from all Conditional Access policies, so when a policy misfires or an MFA or identity outage blocks every normal administrator, it can still sign in and fix or disable the policy. Because these accounts bypass normal controls, alert on every sign-in that uses one.

Common designs. Exempt the office: include any location, then exclude the trusted named location. Block countries you don't operate in: define named locations by country and block sign-ins from outside the allowed ones. Protect only admin tools: target the Microsoft Azure Management app (Azure portal, Azure PowerShell and CLI) instead of all cloud apps. Choice of controls: a grant can require one of the selected controls — for example a compliant device or MFA — so managed laptops pass on compliance while other devices complete MFA. A compliant-device requirement is met only by devices that Intune has enrolled and marked compliant; for a personal phone, enroll it in Intune or use the approved client app / app protection policy (MAM) grant instead of weakening the policy.

⚠️ Exam Trap: Conditional Access policies are evaluated at sign-in time — they don't retroactively revoke active sessions. If a user is already signed in when a new policy is applied, they may retain access until their token expires or they sign in again.

Reflection Question: You create a Conditional Access policy that requires MFA for all users when signing in from outside the corporate office. A user complains they are being asked for MFA even when inside the office. What configuration element is most likely missing from your policy?

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