Study guide

4.1 Conditional Access Purpose

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

4.1 Conditional Access Purpose

Key Takeaways Explain This Topic AI

Conditional Access is a Microsoft Entra ID P1/P2 policy engine that evaluates an if-then statement of assignments (conditions) and access controls at sign-in.

It is the practical enforcement layer for Zero Trust: identity is verified explicitly on each access attempt, not trusted permanently after one logon.

A policy gathers signals in Phase 1, then in Phase 2 either blocks or grants access, prompting for unmet grant controls in a fixed order.

When multiple policies apply to a user, all of them must be satisfied (assignments combine with logical AND).

Conditional Access requires at minimum a name, users/groups, target resources, and a grant or block control.

Last updated: June 2026

What Conditional Access actually is

Conditional Access is the policy engine of Microsoft Entra ID that brings signals together to make access decisions and enforce organizational policy. Microsoft describes every Conditional Access policy as an if-then statement : if a set of conditions (assignments) is met, then the policy applies a set of access controls. It is the mechanism that turns the abstract Zero Trust principle "verify explicitly" into an enforced rule at the moment a user tries to reach an application.

Conditional Access is not free with every tenant. It requires at least a Microsoft Entra ID P1 license; risk-based conditions additionally require P2 . This licensing distinction is a favorite SC-900 trap, so remember that basic MFA can be turned on in free tenants via security defaults, but policy-driven MFA requires Conditional Access (P1).

It is an Entra capability — not a Sentinel analytics tool, not a Defender product.

It enforces least privilege and explicit verification on each access attempt.

It can block access outright or grant access only when extra requirements are met.

Security defaults is the simpler, free, all-or-nothing alternative; Conditional Access is the granular, licensed version.

The two-phase decision flow

Microsoft enforces every policy in two phases . Knowing this flow makes scenario questions much easier.

Phase 1 — collect session details. Entra gathers the context it needs: who the user is, what app they want, the network location, the device identity and state, the client app, and any risk level supplied by Microsoft Entra ID Protection. Phase 1 runs even for policies set to report-only mode, which lets admins test a policy's impact before enforcing it.

Phase 2 — enforcement. Entra compares the gathered details against the policy. If any policy uses the block control, evaluation stops and the user is denied. Otherwise the user is prompted to satisfy any unmet grant controls, always in this fixed order:

  • Order Grant control prompted
  • 1 Multifactor authentication
  • 2 Device marked compliant (Intune)
  • 3 Microsoft Entra hybrid joined device
  • 4 Approved client app
  • 5 App protection policy
  • 6 Password change
  • 7 Terms of use

After all grant controls pass, session controls (sign-in frequency, persistent browser, app-enforced restrictions) shape the resulting session.

Where Conditional Access sits in the identity story

Conditional Access lives between authentication and resource access . It does not create user accounts (that is identity administration in Entra ID), it does not prove who you are by itself (that is the job of authentication methods and MFA), and it does not classify or label data (that is Microsoft Purview). Instead, it consumes the result of authentication plus contextual signals and decides whether the access should be allowed under the current conditions.

A critical exam fact: when multiple Conditional Access policies apply to the same user, all of them must be satisfied. Microsoft combines all assignments with logical AND . So a user hit by one policy requiring MFA and another requiring a compliant device must satisfy both. There is no "most permissive policy wins."

Account creation → identity administration in Entra ID.

Proving identity at sign-in → authentication / MFA.

Deciding access by policy and context → Conditional Access .

Labeling and retaining data → Microsoft Purview.

Minimum policy and product-matching guardrails

Microsoft states a Conditional Access policy must contain at least : a name , assignments (users/groups and target resources), and access controls (a grant or block decision). If a question lists policy pieces, those are the required ones.

The safest way to pick the right answer is to name the problem before the product. If the scenario is about who may reach a cloud resource under which circumstances , stay in the Entra Conditional Access lane. Defender protects and investigates workloads; Sentinel does SIEM and SOAR; Purview handles compliance and data governance.

Entra / Conditional Access : policy-based access decisions on cloud resources.

Defender : protection and threat investigation.

Sentinel : SIEM, SOAR, hunting, incidents.

Purview : compliance, classification, retention, audit.

If the problem says "require stronger sign-in only from untrusted networks" or "block legacy authentication," that is textbook Conditional Access.

Why Conditional Access is the heart of Zero Trust

Conditional Access is the place where the three Zero Trust guiding principles become real enforcement. Verify explicitly means every access request is authenticated and authorized using all available data points — that is exactly the signal collection Conditional Access performs. Use least-privileged access is supported because a policy can grant only limited or time-bound sessions rather than open-ended access. Assume breach is honored because access is re-evaluated on each request instead of being trusted forever after one logon.

For SC-900 it is worth stating plainly: Conditional Access is the operational engine that an organization uses to implement Zero Trust for identity and access.

A related concept is continuous access evaluation (CAE) . Traditionally an access token is valid for about an hour, so a user who is disabled or whose risk spikes could keep access until the token expires. CAE lets Entra and supporting services (like Exchange Online and SharePoint Online) react in near real time to critical events — a user being disabled, a password reset, or an elevated risk detection — by revoking the session almost immediately. CAE is enabled by default and reinforces the "assume breach" idea that trust must be re-checked, not granted once.

Finally, remember the report-only capability: before enforcing a policy, admins set it to report-only so Entra logs what would have happened without blocking anyone, letting them measure impact and avoid lockouts.

Verify explicitly → collect and evaluate signals each time.

Least privilege → grant limited or time-bound sessions.

Assume breach → re-evaluate access continuously (CAE).

Report-only → test policy impact before enforcement.