Study guide

3.3 Hybrid Identity and Entra Connect Concepts

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.3 Hybrid Identity and Entra Connect Concepts

Key Takeaways Explain This Topic AI

Hybrid identity gives users one identity across on-premises Active Directory and Microsoft Entra ID, synced by Microsoft Entra Connect (formerly Azure AD Connect).

Synchronization copies identity objects to the cloud; authentication can stay cloud-managed (PHS or PTA) or be handed off on-premises (federation).

Password Hash Sync (PHS) syncs a hash-of-a-hash to Entra ID so authentication happens fully in the cloud — Microsoft's recommended default.

Pass-through Authentication (PTA) validates the password against on-premises AD in real time via lightweight agents, with no password stored in the cloud.

Federation (e.g., AD FS) hands authentication entirely to a separate on-premises trust system — the most complex option, used for specialized requirements.

Last updated: June 2026

What hybrid identity solves

Most organizations already run on-premises Active Directory Domain Services (AD DS) before adopting the cloud. Hybrid identity lets them give users one identity and one set of credentials that works both on-premises and in Microsoft Entra ID, instead of two separate accounts. Users sign in with the same username and password whether they open an internal app or a Microsoft 365 service.

The tool that makes this happen is Microsoft Entra Connect (formerly Azure AD Connect ) — an on-premises agent that synchronizes identity objects from AD DS up to the Entra ID tenant. There is also a lighter-weight option, Microsoft Entra Connect cloud sync , which uses a small provisioning agent and pushes configuration to the cloud (useful for multi-forest and disconnected-forest scenarios).

Key split to remember: synchronization (copying the objects) and authentication (where the password is actually checked) are separate decisions . Connect always syncs the objects; you then choose how sign-in is validated.

The three sign-in (authentication) methods

When configuring hybrid identity, an organization picks one of three authentication methods. This is one of the most commonly tested comparisons in the Entra domain.

Method Where the password is verified On-premises footprint Notes

Password Hash Synchronization (PHS) In the cloud (Entra ID) Smallest — just Entra Connect A non-reversible hash of the AD password hash is synced to the cloud; recommended default

Pass-through Authentication (PTA) On-premises AD, in real time Medium — lightweight PTA agents Password is never stored in the cloud; on-prem account policies enforced at sign-in

Federation (e.g., AD FS) On-premises federation service Largest — AD FS farm + infra Entra ID hands off authentication to a separate trusted system

Microsoft recommends PHS for most organizations because it is simplest, removes dependence on highly available on-premises infrastructure, and still enables cloud features like leaked-credential detection in Identity Protection.

Password Hash Sync, Pass-through Auth, and Federation in depth

Password Hash Synchronization (PHS). Entra Connect computes a hash of the existing AD password hash and syncs that value to Entra ID. The original password is never transmitted, and the synced value cannot be reversed back into the password or used against the on-premises directory. Because authentication then happens entirely in the cloud , sign-in keeps working even if the on-premises servers or network are down.

Pass-through Authentication (PTA). Sign-in requests are validated directly against on-premises AD by one or more lightweight agents , so the password is never present in Entra ID in any form . PTA enforces on-premises account state at sign-in time — a disabled, locked-out, or expired account, or sign-in outside permitted hours, is rejected immediately. This suits organizations with strict security/compliance requirements that want on-prem to remain authoritative.

Federation. Entra ID delegates authentication to a separate trusted system such as AD FS (Active Directory Federation Services) or a third-party IdP. It supports advanced needs (smart cards, certain third-party MFA, specific compliance rules) but carries the largest footprint and most complexity , so Microsoft is steering most customers from federation toward cloud authentication (PHS/PTA).

Choosing a method — and exam cues

Use the scenario wording to pick the method:

Simplest, least infrastructure, cloud handles sign-in, keep working if on-prem is down → Password Hash Sync (PHS) .

Password must NOT be stored in the cloud / validate against on-prem in real time / enforce on-prem account policy at sign-in → Pass-through Authentication (PTA) .

Use an existing AD FS / third-party identity system, advanced or specialized authentication requirements → Federation .

Common traps: PHS does not send the plaintext password (it sends a non-reversible hash), so "PHS exposes passwords" is wrong. PTA needs agents but no full federation farm. And remember the layered distinction — synchronizing objects with Entra Connect is separate from choosing PHS/PTA/Federation for authentication. For SC-900, you need the purpose and trade-offs of each, not the deployment steps.

Seamless SSO, staged rollout, and the cloud-first direction

Two supporting concepts round out hybrid sign-in. Seamless single sign-on (Seamless SSO) automatically signs corporate users in when they are on a domain-joined device on the corporate network, so they aren't re-prompted for the Microsoft cloud — it can be added to PHS or PTA (federation has its own SSO). Staged rollout lets an organization migrate a subset of users from federation to cloud authentication (PHS/PTA) for testing before switching the whole tenant.

The broader trend the exam reflects is cloud-first : Microsoft now steers most customers away from federation toward PHS or PTA , because keeping authentication in the cloud is simpler, more resilient, and unlocks cloud-native protections like leaked-credential detection in Identity Protection (which depends on the password hash being present in the cloud, i.e., PHS).

Seamless SSO removes extra prompts for users on the corporate network.

Staged rollout migrates pilot users off federation before a full cutover.

PHS is required for cloud leaked-credential detection.

The recommended modern default is cloud authentication (PHS, then PTA) over federation.

Knowing this direction helps you eliminate "federation" as the answer whenever a scenario stresses simplicity, resilience, or built-in cloud protection.