Study guide
3.4 Hybrid Authentication Methods & Staged Rollout
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
3.4 Hybrid Authentication Methods & Staged Rollout
Key Takeaways Explain This Topic AI
Password Hash Synchronization (PHS) is the recommended default hybrid authentication method, providing cloud-autonomous authentication, maximum disaster recovery resilience, and leaked credentials detection.
Pass-through Authentication (PTA) validates credentials in real time against on-premises domain controllers via outbound HTTPS polling agents, enforcing on-premises logon hours and account restrictions immediately.
Seamless Single Sign-On (Seamless SSO) provides zero-prompt Kerberos authentication for domain-joined machines on the corporate network using the AZUREADSSOACC computer account in AD DS.
Password Writeback enables cloud-initiated Self-Service Password Resets (SSPR) to be synchronized instantly back to on-premises AD DS over an encrypted Service Bus relay.
Staged Rollout allows organizations to migrate pilot groups of users from federated authentication (AD FS) to cloud authentication (PHS or PTA) without converting the entire domain namespace at once.
Last updated: August 2026
Hybrid Authentication Methods & Staged Rollout
Selecting and deploying the appropriate hybrid sign-in architecture is one of the most critical decisions in hybrid identity administration. The sign-in method determines where authentication occurs (in the cloud vs. on-premises), how disaster recovery scenarios are handled when on-premises WAN links fail, how security policies (such as logon hours and leaked credential detection) are enforced, and how seamless single sign-on is delivered to end users.
1. Deep Dive: Hybrid Authentication Methods
Microsoft Entra ID supports three primary hybrid authentication methods, each with distinct architectural and operational profiles. +-----------------------------------------------------------------------------------+
- | HYBRID AUTHENTICATION ARCHITECTURES |
- | |
- | [1. PASSWORD HASH SYNC (PHS)] |
- | User Entry ---> [Microsoft Entra Cloud Auth Engine] (100% Cloud Autonomous) |
- | (Authenticates against 1000x SHA-256 Hash of NTLM Hash) |
- | |
- | [2. PASS-THROUGH AUTHENTICATION (PTA)] |
- | User Entry ---> [Entra Service Bus Queue] <=== (Outbound HTTPS Poll) === |
- | [On-Premises PTA Agents] ---> [AD DS Domain Controllers] |
- | |
- | [3. FEDERATION (AD FS)] |
- | User Entry ---> [Browser Redirect] ---> [Perimeter WAP] ---> [Internal AD FS] |
- | (AD FS Validates against AD DS & Issues Signed SAML Token) |
- +-----------------------------------------------------------------------------------+
1. Password Hash Synchronization (PHS):
Cryptographic Pipeline: Entra Connect reads the user's NTLM password hash from on-premises AD DS via directory replication APIs (Netlogon/DRSUAPI). It expands the 16-byte binary hash to 64 bytes, adds a per-user 10-byte salt , and feeds the result into PBKDF2 using 1,000 iterations of HMAC-SHA256 . This generated hash of a hash is transmitted over TLS 443 to Entra ID. The password hash sync process runs every 2 minutes and that frequency cannot be modified — it is independent of the 30-minute directory synchronization cycle.
Security Impossibility: The resulting cloud hash cannot be reversed into the on-premises NTLM hash or plaintext password. It is mathematically impossible to use the cloud hash to authenticate against on-premises resources.
Leaked Credentials Detection: Integrates with Microsoft Entra ID Protection . Microsoft compares the user's synced password hashes against billions of exposed credentials found on the dark web and threat intelligence feeds, automatically flagging high-risk accounts.
Maximum Resilience (Cloud Autonomous): If on-premises domain controllers, WAN connections, or internal data centers go offline, cloud authentication continues uninterrupted.
2. Pass-through Authentication (PTA):
Mechanism: User authentication requests are submitted to Entra ID, which places them into an encrypted Azure Service Bus queue .
PTA Agents: Lightweight agents installed on Windows Server domain member servers poll this queue over outbound HTTPS (TCP 443) . The agent retrieves the request, calls the Win32 LogonUser API to validate the credentials against on-premises domain controllers in real time, and writes the validation result back to the queue.
Real-Time Policy Enforcement: Immediately enforces on-premises account lockouts, disabled states, expired passwords, and Active Directory Logon Hours / Workstation Restrictions .
High Availability Guidance: PTA runs with a single agent, but that agent is a single point of failure for every sign-in. For production, Microsoft recommends a minimum of 3 Authentication Agents on independent servers, and enforces a system limit of 40 agents per tenant . Extra agents give redundancy but not deterministic load balancing; Microsoft benchmarks one agent at 300-400 authentications per second on a 4-core, 16 GB server.
3. Federation with Active Directory Federation Services (AD FS):
Mechanism: Entra ID redirects the user's browser to the on-premises Web Application Proxy (WAP) in the perimeter network, which forwards to internal AD FS servers. AD FS validates the user against AD DS (supporting smart cards, x509 certificates, or hardware tokens) and issues a cryptographically signed SAML 2.0 or WS-Federation token.
Operational Overhead & Vulnerability: High infrastructure complexity (load balancers, WAP servers, AD FS servers, public SSL certificates). Single Point of Failure: If the on-premises AD FS farm or WAN link goes down, all cloud sign-ins fail immediately unless fallback mechanisms are configured.
Hybrid Sign-In Method Decision Matrix
- Capability / Metric Password Hash Sync (PHS) Pass-through Auth (PTA) Federation (AD FS)
- Authentication Location Microsoft Entra ID (Cloud) On-Premises AD DS On-Premises AD FS Farm
On-Premises Dependency None during sign-in (Autonomous) High (Requires active agent & DC) Critical (Single point of failure)
- Sign-In Latency Minimal (< 50ms) Moderate (Queue polling) Variable (Multiple redirects)
- Leaked Credentials Detection Yes (Entra ID Protection) No No
- Enforces AD DS Logon Hours No (Enforced only at sync) Yes (Real-time evaluation) Yes (Real-time evaluation)
- Smart Card / Cert-Based Auth Supported via Entra CBA Supported via Entra CBA Yes (Native on-premises)
- Infrastructure Complexity None (Zero extra VMs) Low (Lightweight agents) High (WAP, AD FS, SQL, Certs)
Recommended Use Case Default standard for 99% of orgs Strict compliance / logon hours Legacy smart cards / custom claims
2. Seamless Single Sign-On (Seamless SSO)
Microsoft Entra Seamless Single Sign-On (Seamless SSO) automatically signs users in when they are on their corporate devices connected to the corporate network, without prompting for passwords. +-----------------------------------------------------------------------------------+
- | SEAMLESS SSO KERBEROS AUTHENTICATION FLOW |
- | |
- | [1. User Workstation] |
- | - Accesses https://portal.azure.com |
- | - Entra ID returns HTTP 401 Challenge with SPN: |
- | "HTTP/autologon.microsoftazuread-sso.com" |
- | |
- | [2. Workstation Requests Kerberos Ticket] |
- | - Sends TGS-REQ to On-Premises Domain Controller |
- | - DC generates Kerberos Ticket encrypted with AZUREADSSOACC secret |
- | |
- | [3. Workstation Presents Ticket to Entra ID] |
- | - Entra ID decrypts ticket using shared AZUREADSSOACC key |
- | - Entra ID validates identity and issues SAML/OAuth token |
- +-----------------------------------------------------------------------------------+
The AZUREADSSOACC Computer Account:
When Seamless SSO is enabled in Entra Connect, a computer account named AZUREADSSOACC is created in the on-premises Active Directory domain. Entra Connect shares the Kerberos decryption keys of this computer account securely with Microsoft Entra ID.
Group Policy Configuration:
For client browsers to automatically transmit Kerberos tickets without security prompts, administrators must configure two Group Policy settings under User Configuration > Administrative Templates > Windows Components > Internet Explorer > Internet Control Panel > Security Page :
Site to Zone Assignment List: Add https://autologon.microsoftazuread-sso.com with a value of 1 (Intranet Zone).
Allow updates to status bar via script: Set to Enabled for the Intranet Zone.
Crucial Maintenance: Rolling the Kerberos Decryption Key:
To maintain security and prevent Kerberos ticket forging attacks (Golden Ticket), the Kerberos decryption key of AZUREADSSOACC must be rolled over periodically (recommended at least every 30 days). # Importing the Microsoft Entra Connect SSO PowerShell Module
Import-Module "C:\Program Files\Microsoft Azure Active Directory Connect\AzureADSSO.psd1"
- # Connecting to Microsoft Entra ID with Hybrid Identity Administrator Credentials
- $creds = Get-Credential
- New-AzureADSSOAuthenticationContext -Credentials $creds
- # Rolling the Kerberos Decryption Key across all synced forests
- Get-AzureADSSOStatus | Update-AzureADSSOForest -OnPremCredentials (Get-Credential)
- 3. Self-Service Password Reset (SSPR) & Password Writeback
Password Writeback is a bi-directional synchronization feature that allows users who reset or change their password in Microsoft Entra ID (via the SSPR portal, MySignIns, or modern auth prompts) to have that new password instantly written back to on-premises AD DS. +-----------------------------------------------------------------------------------+
- | SSPR PASSWORD WRITEBACK DATA FLOW |
- | |
- | [User Resets Password in Cloud] ---> [Microsoft Entra SSPR Service] |
- | | |
- | (Encrypted Service Bus Relay) |
- | v |
- | [On-Premises AD DS] <--- (Netlogon API) <--- [Entra Connect Sync Engine] |
- | - Enforces AD Password Policies (Length, Complexity, History) |
- | - Unlocks Locked User Accounts (if enabled) |
- +-----------------------------------------------------------------------------------+
Key Operational Rules for Password Writeback:
No Inbound Ports Required: Password writeback uses an outbound-initiated encrypted WebSocket connection over TCP port 443 to Azure Service Bus.
On-Premises Policy Enforcement: When Entra Connect writes the password back to AD DS, on-premises Active Directory password policies (minimum length, complexity, password history, and minimum password age) are fully enforced. If the new password violates on-premises password history, the reset fails in the cloud UI with a descriptive policy error.
Account Unlock Writeback: SSPR can be configured to simultaneously unlock a locked on-premises AD DS account without requiring the user to wait for lockout duration expiration.
4. Staged Rollout: Migrating from Federation to Cloud Auth
Historically, migrating an enterprise domain from Federated (AD FS) authentication to Cloud Authentication (PHS or PTA) was an all-or-nothing cutover. If any issues occurred, all users in the domain were impacted.
Staged Rollout eliminates this risk by allowing administrators to selectively pilot and transition specific groups of users to cloud authentication while the domain remains configured as Federated. +-----------------------------------------------------------------------------------+
- | STAGED ROLLOUT MIGRATION ARCHITECTURE |
- | |
- | [FEDERATED DOMAIN: CONTOSO.COM] |
- | | |
- | +---------------------+---------------------+ |
- | | | |
- | v v |
- | [USERS IN STAGED ROLLOUT GROUP] [ALL OTHER DOMAIN USERS] |
- | - Authenticate via PHS or PTA - Authenticate via AD FS / WAP |
- | - Use Seamless SSO - Full Federation Prompts |
- | - Zero impact on federation - Legacy Fallback Intact |
- +-----------------------------------------------------------------------------------+
Staged Rollout Capabilities:
Supported Features: Password Hash Sync, Pass-through Authentication, Seamless SSO, and Certificate-based Authentication (CBA).
Granular Group Assignment: Cloud-created or synced security groups are assigned to specific Staged Rollout features in the Microsoft Entra Admin Center. When a member of that group initiates login, Entra ID intercepts the request and handles authentication directly via PHS/PTA rather than redirecting the browser to AD FS.
Seamless Fallback: If a pilot user experiences authentication issues, simply removing the user from the Staged Rollout security group instantly reverts their authentication back to AD FS.
Final Domain Conversion to Managed:
Once all user groups have been validated successfully in Staged Rollout, the administrator converts the domain from Federated to Managed using Microsoft Graph PowerShell: # Converting an Entra ID domain from Federated to Managed authentication
- Connect-MgGraph -Scopes "Domain.ReadWrite.All"
- Update-MgDomain -DomainId "contoso.com" -AuthenticationType "Managed"