Study guide
3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health
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.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health
Key Takeaways Explain This Topic AI
The sourceAnchor is the immutable link between an on-premises object and its cloud counterpart, surfaced in Entra ID as immutableId; it can never change for the life of the object.
mS-DS-ConsistencyGuid is the recommended sourceAnchor over objectGUID because it survives a cross-forest migration, whereas objectGUID is regenerated when the object moves.
Soft matching joins a cloud object to an on-premises object by matching UserPrincipalName or primary SMTP proxy address; hard matching sets immutableId directly through Microsoft Graph.
The Synchronization Rules Editor applies inbound and outbound rules by precedence value, where the lowest number wins; custom rules should occupy precedence numbers below 100 to survive upgrades.
Microsoft Entra Connect Health installs monitoring agents on sync servers, domain controllers, and AD FS servers to surface sync errors such as AttributeValueMustBeUnique, replication failures, and authentication latency.
Last updated: August 2026
- SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health
- 1. SourceAnchor, ImmutableID, and Identity Matching Mechanics
The sourceAnchor is an attribute in on-premises AD DS that uniquely and immutably identifies an identity object throughout its entire lifecycle. In Microsoft Entra ID, this attribute is stored in the cloud as the immutableId (represented as a Base64-encoded string). +-----------------------------------------------------------------------------------+
- | SOURCEANCHOR TO IMMUTABLEID CONVERSION |
- | |
- | [On-Premises AD DS Object] [Microsoft Entra ID Object] |
- | Attribute: mS-DS-ConsistencyGuid Attribute: immutableId |
- | Format: Raw Binary GUID Format: Base64 String |
- | Hex: 6a 3b 84 a9 e2 11 4e 88... String: ajuEqeIRCk6I... |
- | | ^ |
- | +-----------> [Base64 Conversion] ---------------+ |
- +-----------------------------------------------------------------------------------+
mS-DS-ConsistencyGuid vs. objectGUID :
objectGUID (Legacy Anchor): Generated automatically by AD DS upon object creation. While unique within a domain, objectGUID is strictly immutable in AD DS. If a user account is migrated to another forest or domain using Active Directory Migration Tool (ADMT), AD DS generates a new objectGUID in the destination domain. Because the cloud immutableId remains linked to the old GUID, the user's cloud identity is duplicated or orphaned.
mS-DS-ConsistencyGuid (Modern Best Practice): A writable binary attribute in AD DS. During initial synchronization, Entra Connect reads the object's objectGUID , writes that exact binary value into the user's mS-DS-ConsistencyGuid attribute in AD DS, and uses it as the sourceAnchor. If the user is subsequently migrated to another forest, migration scripts can copy the original mS-DS-ConsistencyGuid value to the new account in the target forest, preserving the exact link to the user's existing Entra ID mailbox, licenses, and OneDrive data.
Soft Match vs. Hard Match Mechanics:
When synchronizing an on-premises user to an existing cloud-only user (e.g., during cloud-to-hybrid onboarding), Entra Connect uses matching rules:
Soft Match (Attribute Matching):
Matches an unmanaged cloud user to an on-premises user if UserPrincipalName matches exactly, OR if the primary SMTP address in proxyAddresses matches mail .
Limitation: Soft matching only functions if the cloud user object has never been synced before ( immutableId is $null ). Once matched, Entra Connect converts the cloud user to a synced object and binds its immutableId permanently.
Hard Match (Direct Anchor Binding):
Explicitly populates the cloud user's immutableId with the Base64-encoded binary GUID of the on-premises account using PowerShell.
Used to remediate broken sync links or resolve duplicate object creation. # Converting an On-Premises Active Directory objectGUID to Base64 ImmutableID
- $adUser = Get-ADUser -Identity "ranchen" -Properties objectGUID, mS-DS-ConsistencyGuid
- $guidBytes = $adUser.objectGUID.ToByteArray()
- $immutableId = [Convert]::ToBase64String($guidBytes)
- Write-Output "Base64 ImmutableID: $immutableId"
- # Performing a Hard Match in Microsoft Entra ID via Microsoft Graph PowerShell
- Connect-MgGraph -Scopes "User.ReadWrite.All"
- Update-MgUser -UserId "ranchen@contoso.com" -OnPremisesImmutableId $immutableId
- 2. Synchronization Rules Editor & Precedence Management
Custom attribute flows are implemented using the Synchronization Rules Editor ( syncruleseditor.exe ). +-----------------------------------------------------------------------------------+
- | SYNCHRONIZATION RULE PRECEDENCE |
- | |
- | [Rule Precedence: 1 to 99] ---> Custom Inbound / Outbound Rules (Highest) |
- | [Rule Precedence: 100 to 399] ---> Out-of-the-Box Default Rules (Baseline) |
- | [Rule Precedence: 400+] ---> Catch-All & Fallback Rules (Lowest) |
- | |
- | RULE: If two rules contribute to the same Metaverse attribute, |
- | the rule with the LOWER numeric precedence value WINS. |
- +-----------------------------------------------------------------------------------+
Rule Types and Transformation Expressions:
Inbound Rules: Transform attributes from a Connector Space into the Metaverse.
Outbound Rules: Transform attributes from the Metaverse into a Connector Space.
Link Types:
Provision / Projection: Creates a new object in the target space if no match exists.
Join: Matches an existing CS object to an existing Metaverse object using join criteria (e.g., sAMAccountName equals accountName ).
Transformations:
Direct: Direct 1-to-1 attribute mapping (e.g., givenName -> givenName ).
Constant: Hardcodes a static value (e.g., setting accountEnabled to True ).
Expression: Uses declarative logic (e.g., IIF(IsNullOrEmpty([mail]), [userPrincipalName], [mail]) or Left([department], 10) ).
Warning
Never Modify Default Synchronization Rules Directly: Default rules (precedence ≥ 100) are overwritten during Entra Connect upgrades. To customize attribute flow, disable the default rule, clone it, assign the cloned rule a lower precedence number (e.g., 50), and modify the clone.
3. Microsoft Entra Connect Health & Operational Monitoring
Microsoft Entra Connect Health provides cloud-based monitoring, alerting, and diagnostic telemetry for hybrid identity components. +-----------------------------------------------------------------------------------+
- | MICROSOFT ENTRA CONNECT HEALTH ECOSYSTEM |
- | |
- | +------------------------------------------------------------------------------+ |
- | | MICROSOFT ENTRA CONNECT HEALTH CLOUD PORTAL | |
- | | - Centralized Health Dashboard & Email Alert Notifications | |
- | | - Sync Error Reports (Duplicate Attributes, Data Validation, Large Object) | |
- | | - Password Hash Sync Latency & Performance Diagnostics | |
- | +------------------------------------------------------------------------------+ |
- | ^ (HTTPS 443) ^ (HTTPS 443) ^ (HTTPS 443) |
- | | | | |
- | +-------------------+ +-------------------+ +--------------------+ |
- | | Sync Health Agent | | AD DS Health Agent| | AD FS Health Agent | |
- | | (Entra Connect) | | (Domain Ctrlrs) | | (WAP & AD FS Farm) | |
- | +-------------------+ +-------------------+ +--------------------+ |
- +-----------------------------------------------------------------------------------+
Core Monitoring Agents:
Entra Connect Health Agent for Sync: Installed on the Entra Connect server. Monitors synchronization errors, run cycle durations, password hash synchronization heartbeat, and staging mode status.
Entra Connect Health Agent for AD DS: Installed on physical/virtual on-premises domain controllers. Monitors AD replication latency, SYSVOL replication, Kerberos/NTLM authentication traffic, and PDC Emulator performance.
Entra Connect Health Agent for AD FS: Installed on internal AD FS federation servers and perimeter Web Application Proxy (WAP) servers. Tracks token issuance rates, bad password lockouts, and federation metadata validation.
Common Synchronization Errors & Remediation:
Duplicate Attribute Conflict ( AttributeValueMustBeUnique ): Occurs when two on-premises objects share the same UserPrincipalName or ProxyAddresses (SMTP alias). Entra ID requires tenant-wide uniqueness for these attributes. Entra ID generates a quarantine proxy address (e.g., user@contoso.onmicrosoft.com with a modified alias) until the on-premises duplicate is cleared.
Data Validation Failure: Occurs when an attribute contains illegal characters, unsupported format strings, or exceeds maximum length constraints.
Large Object Error: Occurs when a single security group exceeds membership limits or contains excessive nested attributes beyond the synchronization threshold.
Staging Mode and Disaster Recovery:
Staging Mode configures the Entra Connect sync engine to execute all import and synchronization cycles (building and updating its local Connector Spaces and Metaverse) while suspending all export operations to Microsoft Entra ID and AD DS. # Checking Current Synchronization Scheduler & Staging Mode Status
Get-ADSyncScheduler
# Output includes:
- # SyncCycleEnabled : True
- # StagingModeEnabled : True <-- (Exports are suspended)
- # CustomizedSyncCycleInterval : 00:30:00
- # Exporting and analyzing pending changes on a Staging Server using csexport.exe
- cd "C:\Program Files\Microsoft Azure AD Sync\Bin"
- .\csexport.exe "contoso.onmicrosoft.com - AAD" export.xml /f:x
- .\CSExportAnalyzer.exe export.xml > pending_changes.csv
Tip
Warm Standby Disaster Recovery Architecture: Deploy a secondary Entra Connect server in Staging Mode connected to the same SQL database or a replicated instance. If the primary sync server suffers a catastrophic hardware failure, promoting the staging server to primary requires only running Set-ADSyncScheduler -StagingModeEnabled $false —eliminating prolonged sync downtime.