Study guide

3.1 Microsoft Entra ID Foundations

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

3.1 Microsoft Entra ID Foundations

Key Takeaways Explain This Topic AI

Microsoft Entra ID (formerly Azure Active Directory / Azure AD) is Microsoft's cloud-based identity and access management (IAM) service and identity provider.

Entra ID is multi-tenant: every organization gets its own tenant (a dedicated directory instance) identified by a tenant ID and an initial onmicrosoft.com domain.

It is the identity backbone for Microsoft 365, Azure, and thousands of SaaS apps via single sign-on (SSO) and the OAuth 2.0 / OpenID Connect / SAML protocols.

Entra ID is NOT a cloud-hosted copy of on-premises Active Directory Domain Services — it has no domain join, LDAP, Kerberos, NTLM, OUs, or Group Policy.

Identity is the primary security perimeter in Zero Trust; authentication proves who you are, authorization decides what you may access.

Last updated: June 2026

What Microsoft Entra ID is

Microsoft Entra ID is Microsoft's cloud-based identity and access management (IAM) service. It was renamed from Azure Active Directory (Azure AD) in 2023, and the rename is one of the most heavily tested facts on SC-900 — if an answer choice says "Azure AD," it is usually the old name for the same product. Entra ID acts as an identity provider (IdP) : a trusted system that authenticates users, apps, and devices and then issues security tokens that downstream services accept as proof of identity.

Entra ID is the identity backbone for:

  • Microsoft 365 (Exchange Online, SharePoint, Teams, etc.)
  • Microsoft Azure (subscriptions, resource management, RBAC)
  • Thousands of third-party SaaS apps integrated for single sign-on (SSO)
  • Custom line-of-business apps that register against Entra ID

It speaks modern, open authentication protocols — OAuth 2.0 , OpenID Connect (OIDC) , and SAML 2.0 — which is how one sign-in can unlock many apps without re-entering credentials.

A useful framing: Entra ID is the identity control plane for Microsoft's cloud. Every request to Microsoft 365, Azure, or an integrated SaaS app is brokered through it — it authenticates the principal, applies access policy, and issues the token the target service trusts. Because so much converges on it, securing Entra ID is the foundation of securing everything else, which is why the exam devotes an entire objective area to it.

Tenants: one directory per organization

Entra ID is multi-tenant . When an organization signs up for Microsoft 365 or Azure, it receives its own tenant — a dedicated, isolated instance of the directory. A tenant is identified by a tenant ID (a GUID) and gets an initial domain like contoso.onmicrosoft.com , to which the organization can add its own verified custom domains (e.g., contoso.com ).

The tenant is the security and administrative boundary : users, groups, app registrations, and policies in one tenant are isolated from every other tenant. Identities from other tenants can be invited in as guests (covered in 3.x External Identities), but they remain external.

  • Concept Meaning on SC-900
  • Tenant A dedicated, isolated Entra ID directory instance for one organization
  • Tenant ID The GUID that uniquely identifies a tenant
  • Initial domain The default *.onmicrosoft.com domain created with the tenant
  • Token Signed proof of identity/permissions that apps trust
  • Single sign-on (SSO) Authenticate once, then access many connected apps

Entra ID is not on-premises Active Directory

The single biggest conceptual trap is assuming Entra ID is just "Active Directory in the cloud." It is not. On-premises Active Directory Domain Services (AD DS) and Microsoft Entra ID solve overlapping problems with very different technology.

  • Capability On-premises AD DS Microsoft Entra ID
  • Protocols Kerberos, NTLM, LDAP OAuth 2.0, OIDC, SAML, REST
  • Structure Forests, domains, OUs Flat directory of objects in a tenant
  • Computer management Domain join, Group Policy Device registration/join, no GPO (uses Intune)
  • Built for Internal Windows networks Cloud and web/SaaS apps over the internet
  • Query interface LDAP Microsoft Graph API

Entra ID has no Organizational Units (OUs) and no Group Policy Objects (GPOs) ; device configuration is handled by Microsoft Intune , not GPO. The two can work together through hybrid identity (section 3.3), but they are distinct services.

Why identity is the perimeter — and authentication vs. authorization

In the Zero Trust model, the traditional network firewall is no longer the only perimeter because users, devices, and apps connect from anywhere. Identity becomes the primary security perimeter : nearly every access decision begins with who or what is requesting access, so Entra ID is where security starts.

Two terms appear in almost every Entra question and must be kept separate:

Authentication (AuthN) — proving who an identity is (a correct password, a passkey, an MFA approval). "Are you really you?"

Authorization (AuthZ) — deciding what an authenticated identity is allowed to do (a role assignment, a Conditional Access grant). "Now that we know who you are, what can you do?"

A reliable exam reflex: a sign-in/proof scenario is authentication ; a permission/access-allowed scenario is authorization . Entra ID handles both, but they are different steps in the same flow, and mixing them up is the classic distractor.

Finally, know where Entra ID sits in the licensing story, because SC-900 occasionally pairs a capability with the tier that unlocks it. The Free tier provides core directory, user/group management, SSO, and self-service password change. Microsoft Entra ID P1 adds Conditional Access, dynamic groups, self-service password reset with writeback, and hybrid features. Microsoft Entra ID P2 adds the advanced governance and protection tier — Privileged Identity Management (PIM) and Identity Protection (covered in Chapter 4).

You do not need to memorize a full SKU chart, but you should recognize that the richer access-management and protection features are paid tiers, while basic identity is included with Microsoft 365 and Azure subscriptions. The exam rewards knowing that Entra ID is the identity control plane and that its premium features deliver the Zero Trust controls the rest of this guide builds on.