Study guide

11.2 Entra Playbook for Identity, Access, and Governance

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

11.2 Entra Playbook for Identity, Access, and Governance

Key Takeaways Explain This Topic AI

Microsoft Entra ID is the current name for the cloud identity service; Azure Active Directory is the former name and is not a separate product.

Authentication proves who an identity is, while authorization decides what that identity can access.

Conditional Access, multifactor authentication, roles and RBAC, ID Governance, access reviews, PIM, and ID Protection all live in the identity lane.

Entra PIM provides just-in-time activation of administrative roles, which is different from Defender for Cloud just-in-time VM network access.

Last updated: October 2026

Use Entra When the Scenario Is About Identity

The Microsoft Entra domain is one of the largest parts of SC-900 (about 25 to 30 percent), and many product-selection questions open with identity language. If the prompt mentions users, groups, devices, workload identities, authentication methods, multifactor authentication, password protection, Conditional Access, role assignment, access reviews, privileged identity, or sign-in risk, begin with Microsoft Entra. You will not build a tenant on the exam, but you must know which capability owns each task.

Microsoft Entra ID is the current name for the cloud identity and access service. Microsoft renamed Azure Active Directory (Azure AD) to Microsoft Entra ID, with standalone plan names (Entra ID Free, P1, P2) updated in 2023. On the exam, use the current Entra name. This naming detail matters because old study notes that still say Azure AD can make a single service look like two separate answers in a product-selection list.

Requirement in a scenario Entra capability to recognize Exam reasoning

Verify user identity with more than a password Multifactor authentication The task is stronger authentication.

Grant access only when signals meet policy Conditional Access The task is policy-based access control.

Assign permissions to manage Entra or Azure resources Entra roles and RBAC The task is authorization and least privilege.

Review whether users still need access Access reviews (ID Governance) The task is identity governance.

Require just-in-time privileged role activation Privileged Identity Management The task is reducing standing privilege.

Detect risky users or risky sign-ins Microsoft Entra ID Protection The task is identity risk detection.

Authentication Versus Authorization

The exam consistently separates these four identity concepts, and product-selection items often hinge on telling them apart:

Authentication (AuthN) answers who or what is signing in.

Authorization (AuthZ) answers what the authenticated identity is allowed to do.

Federation establishes trust between identity providers so users access resources across organizational boundaries with a single identity.

Directory services store identity information and support lookup, management, and the single sign-on experience.

Hybrid identity questions often describe an organization that already runs on-premises Active Directory and wants users to reach cloud resources. The answer is not a firewall or a compliance tool — the scenario is still about identity, and Microsoft Entra ID supports hybrid identity and identity governance patterns that modernize access while preserving existing directory investments.

The Two Just-in-Time Traps

Conditional Access shows up constantly because it links Zero Trust thinking (verify explicitly, use least-privilege access, assume breach) to identity controls. A Zero Trust prompt that asks to evaluate sign-in signals and enforce a control such as MFA is an Entra Conditional Access item. A prompt that asks to reduce standing administrative access is an Entra PIM item.

The most tested nuance is the meaning of "just-in-time." Entra PIM uses eligible assignments so an admin must activate a privileged role only when needed, for a limited, optionally approval-gated window — just-in-time access to administrative roles . Microsoft Defender for Cloud also has a just-in-time feature, but it controls just-in-time network access to VM management ports such as RDP and SSH. If the scenario is about admin role activation, choose Entra PIM; if it is about locking down inbound RDP/SSH to a virtual machine, choose Defender for Cloud. Same phrase, different products.

Do not overfit every security word to Defender. Identity is a security control, and the SC-900 outline explicitly treats identity as the primary security perimeter. Defender products detect and protect against threats, but they do not decide whether identities can sign in, receive permissions, keep access, or activate privileged roles — those decisions are Entra's job, and recognizing that boundary clears a large share of identity questions quickly.

Governance, Risk, and the External-Identity Distinctions

The identity lane is wide, and SC-900 expects you to place several governance and risk capabilities precisely:

Microsoft Entra ID Governance is the umbrella for lifecycle controls: access reviews (periodically recertify access), entitlement management (bundle resources into access packages users can request), and lifecycle workflows (automate joiner-mover-leaver tasks).

Microsoft Entra ID Protection detects and remediates identity risk — risky users and risky sign-ins — and can feed risk signals into Conditional Access so risky logins are blocked or challenged with MFA.

Microsoft Entra External ID handles business-to-business and business-to-customer identities, replacing the externally branded Azure AD B2B/B2C offerings for new scenarios.

Microsoft Entra Permissions Management offered multicloud permission visibility and least privilege across Azure, AWS, and Google Cloud, but Microsoft stopped selling it on April 1, 2025 and retired it on November 1, 2025.

A reliable trap distinguishes ID Protection from Defender for Identity . Both have "identity" in the name. ID Protection scores risk for cloud identities (risky sign-ins, leaked credentials, impossible-travel patterns) inside Entra. Defender for Identity monitors on-premises Active Directory using domain-controller signals to catch lateral movement and credential theft. If the scenario is cloud sign-in risk, pick Entra ID Protection; if it is on-premises domain attack detection, pick Defender for Identity.

Map Verbs to Entra Capabilities

A verb-first scan makes Entra items fast: prove who you are maps to authentication and MFA; decide what you can reach maps to authorization, roles, and RBAC; gate access on conditions maps to Conditional Access; recertify ongoing access maps to access reviews; request bundled resources maps to entitlement management; limit standing admin power maps to PIM; detect compromised identities maps to ID Protection; handle partners and customers maps to External ID. Because the Entra domain carries roughly 25 to 30 percent of the exam, fluency here pays off disproportionately.

When you can name the verb and snap to the matching Entra capability without hesitation, you avoid the two classic identity mistakes — defaulting to Conditional Access for every access question, and pulling threat-protection answers like Defender into what is fundamentally an access-control or governance decision.