Study guide

2.6 Identity Perimeter, Authentication, Authorization, and Federation

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

2.6 Identity Perimeter, Authentication, Authorization, and Federation

Key Takeaways Explain This Topic AI

Identity is the primary security perimeter because access requests can originate from any network, device, location, or application.

Authentication (AuthN) proves who or what an identity is; authorization (AuthZ) determines what that verified identity is allowed to do — authentication always comes first.

An identity provider (IdP) centralizes authentication, authorization, and auditing and issues security tokens containing claims, which enables single sign-on (SSO).

A directory service stores identity objects (users, devices, groups); AD DS is Microsoft's on-premises directory, and Microsoft Entra ID is the cloud identity and access service.

Federation establishes a trust relationship between separate identity providers so users authenticate with existing credentials across organizations or domains; trust is not automatically two-way.

Last updated: June 2026

Identity is the modern control point

Microsoft's SC-900 outline treats identity as the primary security perimeter . The reasoning ties directly to Zero Trust: modern work no longer happens only inside one protected corporate network. Users, devices, workloads, and applications access resources from homes, offices, public networks, partner environments, and cloud services. Because the network boundary alone cannot define trust, access decisions start with identity — you authenticate and authorize the identity behind each request rather than trusting its origin network.

An identity can belong to a person, a service or application, or a device. The 'four pillars of identity' the exam often references are administration (creating and managing identities), authentication (proving identity), authorization (deciding access), and auditing (tracking activity). Keep these distinct — distractors love to swap two of them.

Authentication vs. authorization

These two are related but sequential and must not be confused:

Term Question it answers Examples

Authentication (AuthN) 'Who or what are you?' — proving identity Password, biometric, one-time passcode, certificate, security key

Authorization (AuthZ) 'What are you allowed to do?' — granting access Role assignments, permissions, access policies

Authentication always happens first ; authorization follows only after the identity is verified. A reliable exam tell: if the prompt asks who the user is, the answer is authentication; if it asks what the signed-in user can access or do, the answer is authorization. A distractor claiming 'authorization happens before authentication' is always wrong.

Identity providers, tokens, and single sign-on

An identity provider (IdP) creates, maintains, and manages identity information while providing authentication, authorization, and auditing services to applications. In modern authentication , an application redirects the user to the IdP; after the IdP verifies the user, it issues a security token that the application trusts. Tokens carry claims — statements about the identity such as user identifier, name, roles, group memberships, issue time, and permissions. The application reads the claims rather than handling credentials itself, which centralizes and strengthens security.

Single sign-on (SSO) is a key IdP benefit: a user authenticates once to the IdP and can then access every application that trusts the same provider without re-entering credentials. SSO improves both usability and control — administrators enforce policies (like MFA and Conditional Access) and can disable a user's access in one place, instantly cutting off all connected apps.

Directory services

A directory service stores and exposes identity-related objects so they can be managed and queried:

Active Directory Domain Services (AD DS) — Microsoft's on-premises directory for domain-based networks. It stores users, devices, and groups, verifies credentials at sign-in, and defines access rights to network resources.

Microsoft Entra ID (formerly Azure Active Directory / Azure AD ) — Microsoft's cloud-based identity and access management service for internet and cloud scenarios. This rebrand is heavily tested: 'Azure AD' and 'Microsoft Entra ID' are the same product, and the current name is Microsoft Entra ID .

Don't confuse a directory (which stores objects) with federation (which establishes trust between providers).

Federation across boundaries

Federation establishes a trust relationship between two separate identity providers so users can authenticate with credentials they already have and access resources in a different organization or domain. The user's home IdP performs authentication; the relying organization's IdP trusts that result and grants access based on it — the user never needs a second set of credentials in the partner system. A familiar everyday example is signing in to a third-party website using an existing account from another provider.

A tested nuance: federation trust is not automatically bidirectional . If both organizations need their users to access each other's resources, a two-way trust must be explicitly configured. A one-way trust lets one side's users into the other, but not vice versa.

Why these concepts matter for SC-900

These identity fundamentals set up the Microsoft Entra chapters (which cover Conditional Access, MFA, identity protection, and identity governance). Domain 1 does not require you to design an identity architecture, but it does demand precise vocabulary. Most wrong answers on identity questions come from two confusions: (1) mixing authentication (sign-in proof) with authorization (access permission), and (2) confusing a directory service (stores objects) with federation (establishes cross-boundary trust).

  • Concept One-line distinction
  • Identity provider Central service that authenticates and issues tokens
  • Directory service Stores identity objects (users, devices, groups)
  • Single sign-on One authentication grants access to many trusting apps
  • Federation Trust between separate IdPs across organizations/domains

Master these distinctions and you can resolve nearly every Domain 1 identity question quickly and correctly.

Modern vs. legacy authentication

The exam contrasts modern authentication with older models. In legacy setups, an application often handled credentials directly or relied on a single on-premises directory. Modern authentication instead delegates the sign-in to a trusted identity provider that returns a token of claims — this is what makes SSO, MFA, Conditional Access, and federation possible across cloud and on-premises resources. Microsoft Entra ID acts as that cloud identity provider for Microsoft 365 and thousands of integrated apps.

Tokens are time-limited and signed, so an application can validate a token without contacting the IdP for every request, yet still trust its claims. This is why a single, well-protected identity provider is so central to Zero Trust: it concentrates verification, policy enforcement, and auditing at one strongly defended control point.

When you see an SC-900 scenario about centralizing sign-in, issuing claims, enabling SSO, or extending trust to a partner, anchor your answer to identity-provider and federation concepts rather than to network or encryption controls — that focus is what separates correct answers from plausible-sounding distractors.