Study guide
2.2 Conditional Access Policies
Microsoft Certified: Cloud and AI Security Engineer Associate SC-500
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Skills Measured & Weightings 1.3 Study Path, Prerequisites & Exam Strategy
2 Microsoft Entra ID Secure Access
2.1 Privileged Identity Management (PIM) 2.2 Conditional Access Policies 2.3 MFA and Passwordless Authentication 2.4 Application Identities, OAuth Consent & Managed Identities
3 Azure Key Vault Secrets and Keys
3.1 Deploy and Configure Key Vault 3.2 Access Control and Firewall for Key Vault 3.3 Keys, Secrets, Certificates & Defender for Key Vault
4 Governance, Policy & RBAC
4.1 Azure Policy for Security Controls 4.2 Defender for Cloud Compliance & Security Standards 4.3 Resource Locks and Azure RBAC 4.4 Custom Roles, Overprivileged Access, Backup & IaC Security
5 Secure Storage Accounts
5.1 Storage Account Security Fundamentals 5.2 Storage Firewalls and Access Policies 5.3 Defender for Storage
6 Secure Databases
6.1 Azure SQL Platform Security 6.2 Database Auditing 6.3 Defender for Databases
7 Network Security Groups & Virtual Network Manager
7.1 Network Security Groups and Application Security Groups 7.2 Azure Virtual Network Manager Security Admin Rules 7.3 Virtual WAN and VPN Security
8 Private Access, Private Link & Azure Firewall
8.1 Microsoft Entra Private Access 8.2 Private Endpoints and Private Link 8.3 Azure Firewall 8.4 Network Watcher Diagnostics and Effective Rules
9 Security for AI Workloads
9.1 Purview DSPM for AI and Data Overexposure 9.2 Copilot Studio Protection and Agent Management 9.3 Microsoft Entra Agent ID Security 9.4 Defender for AI, Foundry Guardrails & AI Gateway
10 Secure Servers and Virtual Machines
10.1 Disk Encryption 10.2 Azure Bastion and JIT VM Access 10.3 Azure Arc and Defender for Servers 10.4 Trusted Launch, VM Security Features & Machine Configuration
11 Application Platform Security
11.1 Containers: AKS, ACR, ACI, Container Apps & Defender for Containers 11.2 Azure Functions and Logic Apps Security 11.3 Azure App Service Security 11.4 Web Application Firewall and API Management Protection
12 Defender for Cloud Security Posture
12.1 Defender CSPM and Secure Score 12.2 Workload Protection Plans and Multicloud Connectors 12.3 Vulnerability Management and Defender EASM
13 Microsoft Sentinel Activity and Event Collection
13.1 Workspaces, Roles & Content Hub 13.2 Data Connectors, Syslog/CEF & Windows Event Collection 13.3 Custom Tables, Retention & Purview Audit 13.4 Automation Rules and Playbooks
14 Microsoft Security Copilot & Final Review
14.1 Microsoft Security Copilot Workspaces and Roles 14.2 Plugins and Security Agents 14.3 Final Review and Exam-Day Strategy
2.2 Conditional Access Policies
Key Takeaways Explain This Topic AI
A Conditional Access policy is an if-then rule: assignments (who/what) + conditions (when/where/how) + access controls (grant/block and session restrictions)
Multiple matching policies all apply; grant controls combine (AND by default when multiple controls are selected) so users must satisfy every applicable policy
Report-only mode evaluates impact without enforcing; use it and the What If tool before turning policies on
Always exclude carefully managed break-glass (emergency access) accounts from policies that could lock out all admins
Common SC-500 controls include require MFA, require authentication strength, require compliant or hybrid joined device, and session controls such as sign-in frequency
Last updated: July 2026
2.2 Conditional Access Policies
Quick Answer: Conditional Access (CA) policies are if-then statements: if a user/app/condition matches, then block access or grant it only after controls such as MFA , authentication strength , or a compliant device . Use report-only and the What If tool before enforcing, and exclude break-glass accounts so you never lock out the tenant.
Conditional Access sits at the center of SC-500 identity security. PIM answers “who may elevate and when”; Conditional Access answers “under what real-time conditions may this identity reach this resource.”
Policy Building Blocks
Every enforceable policy needs at minimum:
A name
Assignments — users/groups (or workload identities) and target resources (cloud apps, user actions, authentication contexts)
Access controls — Grant (allow with requirements) or Block
Conditions refine when the policy fires. Session controls refine the post-grant experience.
Assignments: who and what
Assignment area Examples Notes for the exam
Users and groups All users, specific groups, directory roles, guests Can include or exclude; exclusions are how you protect break-glass
Workload identities Service principals / apps (with Workload ID licensing scenarios) Machine identities can be targeted separately from users
Target resources Office 365, Microsoft Admin Portals, All cloud apps, specific apps, user actions (register security info), authentication contexts “All cloud apps” is broad—pair carefully with exclusions
Evaluation timing tip: Policies that target roles or groups apply when a new token is issued. Adding a user to a group does not retroactively rewrite an already-valid token. For elevated roles, combining CA with PIM activation is a best practice so evaluation aligns with elevation.
Conditions: when the policy applies
Condition What it evaluates SC-500 use
Sign-in risk Entra ID Protection risk level (requires ID Protection capability) Block or require stronger auth on high risk
User risk Compromised credential risk for the user Often force password change + MFA
Device platforms iOS, Android, Windows, macOS, etc. Platform-specific controls (note: platform signal can be spoofable; not sole control)
Locations / network Named locations, trusted IPs, geographies, compliant network Block unexpected countries; trust corp egress carefully
Client apps Browser, mobile apps and desktop clients Legacy patterns; modern policies default to all client types
Filter for devices Device attributes Target only specific device fleets
All configured assignments in a policy are combined with logical AND . If multiple CA policies match a single sign-in, the user must satisfy all of them.
Access controls: grant and block
Block access is absolute for matching conditions—powerful and dangerous if scoped too wide.
Grant access can require one or more of:
- Multifactor authentication
- Authentication strength (built-in MFA, passwordless MFA, phishing-resistant MFA, or custom)
- Device marked as compliant (Intune)
- Microsoft Entra hybrid joined device
- Approved client app / app protection policy
- Password change
- Terms of use
- Custom controls
When multiple grant controls are selected, administrators choose:
- Require all the selected controls (AND — default)
- Require one of the selected controls (OR)
Enforcement order (conceptual): session details are collected (including for report-only policies); then enabled policies enforce. Block stops immediately. Grant requirements are prompted in a defined order (MFA, compliant device, hybrid join, approved client, app protection, password change, terms of use, custom controls). After grants succeed, session controls apply.
Session controls
Session controls limit what happens after sign-in is allowed:
App enforced restrictions (Exchange Online / SharePoint Online limited experience)
Conditional Access App Control via Microsoft Defender for Cloud Apps (block download, monitor sessions, force labeling)
- Sign-in frequency (how often reauthentication is required)
- Persistent browser session
- Continuous access evaluation customization / resilience defaults
- Report-Only Mode and the What If Tool
- Tool / mode Purpose
- Report-only Policy is evaluated and logged as if enforced, but not enforced for end users
What If Simulate a user, app, device, location, and client to see which policies would apply and the expected result
Insights and reporting Review impact before flipping a policy to On
Safe rollout pattern for SC-500 design questions:
- Build the policy in report-only
- Use What If for break-glass, executives, contractors, and mobile-only users
- Review sign-in logs for would-block / would-require-MFA outcomes
- Switch to On during a controlled window
- Keep exclusions minimal and documented
- Break-Glass Accounts
Emergency access (break-glass) accounts prevent total lockout if CA, MFA provider outage, or misconfiguration blocks all admins.
Exam expectations:
- Create at least two cloud-only emergency accounts with Global Administrator
- Use long, complex passwords stored offline in a secure process (or other resilient secret storage)
- Exclude them from Conditional Access policies that could prevent emergency sign-in
- Monitor sign-ins aggressively (alert on any use)
- Do not use them for daily administration (pair with PIM for normal admins)
If every Global Administrator is subject to a broken “require compliant device” policy and no one has a compliant device path, the tenant is locked. Break-glass exclusions are the safety valve.
Common Policies You Should Recognize
Policy intent Typical design
MFA for administrators Users: directory roles (GA, etc.); Apps: all / admin portals; Grant: MFA or phishing-resistant strength
- MFA for all users All users (exclude break-glass); All cloud apps; Grant: MFA
- Block legacy authentication Conditions targeting legacy clients; Block
- Require compliant device for sensitive apps Grant: compliant device (or hybrid join OR compliant)
- High sign-in risk Condition: high risk; Block or require passwordless/phishing-resistant strength
Register security info only from trusted location User action: register security information; trusted locations
- Phishing-resistant for admins Grant: authentication strength = phishing-resistant MFA
- Workload Identities and CA
Modern tenants also protect apps and service principals . Policies can target workload identities for risky sign-ins or location anomalies. For SC-500, know that CA is not only for human users—machine identities are part of the attack surface and can be brought into the same policy model when licensed/configured.
- Interaction with PIM and Authentication Strength
- PIM limits standing privilege; CA limits sign-in path quality
- On activation, requiring MFA in PIM complements CA requiring MFA or authentication strength at token issuance
Authentication strength is a CA grant control that specifies allowed method combinations (for example, only FIDO2 / Windows Hello for Business / certificate-based MFA for phishing-resistant)
SC-500 Scenario Walkthrough
Scenario: Contoso wants admins to use phishing-resistant methods for Microsoft Admin Portals, all users to use MFA for Office 365, and no policy to lock out emergency accounts.
Design:
Policy A — Users: admin directory roles; Target: Microsoft Admin Portals; Grant: phishing-resistant authentication strength; Exclude: break-glass group
- Policy B — Users: all users; Exclude: break-glass; Target: Office 365; Grant: MFA
- Deploy both as report-only , validate with What If for a GA, a standard user, and a break-glass account
- Enable Policy B, then Policy A after impact review
- Keep day-to-day GA rights in PIM eligible assignments so elevation and strong CA combine
- Common Exam Traps
Multiple policies stack — satisfying MFA on one policy does not skip a second policy that also requires a compliant device.
Report-only ≠ off — it still evaluates and produces reports; enforcement is what changes when you set On .
Exclude break-glass — a frequent correct answer when the risk is admin lockout.
Block all locations except trusted without planning remote work / break-glass is a classic misconfiguration story.
Assignments vs conditions vs controls — “who” is assignment; “sign-in risk” is condition; “require MFA” is grant control.
Conditional Access is the real-time gate. The next section deepens the authentication methods and strengths those grant controls depend on—MFA, passwordless, and phishing-resistant options.