Study guide
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering
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.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering
Key Takeaways Explain This Topic AI
Entra Connect Sync moves objects through a three-tier pipeline: a Connector Space per connected directory, a central Metaverse that consolidates identities, and outbound provisioning into Microsoft Entra ID.
Express Settings requires a single AD forest with fewer than 100,000 objects, installs SQL Server Express LocalDB, and enables Password Hash Synchronization plus password writeback by default.
Custom installation is mandatory for multi-forest topologies, an existing full SQL Server instance, alternate sign-in identifiers, or non-default sync options.
Scoping filters can be applied by domain, by organizational unit, or by attribute value; OU filtering is the most common and lowest-risk method for excluding service and test accounts.
Filtering must be planned before the first sync cycle, because removing objects from scope later deletes their cloud counterparts and any cloud-only data attached to them.
Last updated: August 2026
Microsoft Entra Connect Sync Architecture & Deployment
In a hybrid enterprise infrastructure, directory synchronization forms the foundational bridge connecting on-premises Active Directory Domain Services (AD DS) forests with Microsoft Entra ID (formerly Azure Active Directory). Microsoft Entra Connect Sync is the on-premises application designed to bridge this gap, ensuring that identities, security groups, credential hashes, and directory attributes remain continuously synchronized between physical domain controllers and the Microsoft cloud.
Mastering the internal architecture, database dependencies, anchor attribute mechanics, and troubleshooting tools of Entra Connect Sync is critical for the AZ-800 exam and for designing resilient hybrid enterprise architectures.
1. Entra Connect Sync Internal Architecture
Microsoft Entra Connect Sync operates as an identity broker utilizing a state-based synchronization pipeline. Rather than streaming changes directly from on-premises LDAP to the Microsoft Graph API, the sync engine processes directory data through staging areas and a consolidated identity repository. +-----------------------------------------------------------------------------------+
- | MICROSOFT ENTRA CONNECT SYNC PIPELINE & DATA FLOW |
- | |
- | [On-Premises AD DS] [Microsoft Entra] |
- | | ^ |
- | | (LDAP / RPC) | (Graph)|
- | v | |
- | +--------------------+ +----------------+ |
- | | AD DS Connector | | Entra Connector| |
- | | Space (CS) | | Space (CS) | |
- | +--------------------+ +----------------+ |
- | | ^ ^ | |
- | | Inbound | Export Export | | |
- | | Rules | (Password/Attr) (Push) | | |
- | v | | v |
- | +------------------------------------------------------------------------------+ |
- | | METAVERSE | |
- | | - Unified Object Repository (Users, Groups, Contacts) | |
- | | - Attribute Precedence & Rule Engine | |
- | | - Global Anchor Binding (mS-DS-ConsistencyGuid <-> ImmutableID) | |
- | +------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------+
The Three Architectural Components:
Connector Spaces (CS): A staging storage area maintained for each connected directory. There is an AD DS Connector Space representing on-premises objects and a Microsoft Entra Connector Space representing cloud directory objects. The connector space mirrors the raw, un-transformed state of the connected directory.
Metaverse (MV): The unified, centralized identity table. The Metaverse aggregates attributes from multiple connector spaces into a single holistic identity representation (e.g., combining a user's on-premises telephone number with an Exchange Online mailbox property).
Synchronization Engine & Rule Pipeline: Executes three distinct synchronization phases:
Import: Reads raw object changes from the source directory into its respective Connector Space.
Synchronization: Evaluates Inbound Synchronization Rules to project or join CS objects into the Metaverse, applies attribute precedence, and evaluates Outbound Synchronization Rules to stage changes from the Metaverse into the target Connector Space.
Export: Pushes staged attribute modifications, creations, and deletions from the target Connector Space to the external directory (e.g., uploading new user accounts to Microsoft Entra ID via Graph REST APIs).
Database Backend Sizing:
SQL Server Express / LocalDB: Installed automatically during Express installation. It has a strict 10 GB database size limit , which supports up to 100,000 directory objects . If the database reaches 10 GB, the sync engine halts with database full errors.
Full SQL Server (Standard / Enterprise): Mandatory for enterprise deployments managing >100,000 objects , or environments requiring high-availability SQL Always On availability groups, clustered database instances, or custom remote SQL placement.
2. Installation Modes: Express Settings vs. Custom Installation
Choosing the correct installation mode determines how directory credentials, database placement, authentication, and anchor attributes are configured.
- Installation Dimension Express Settings Custom Installation
- Target Topology Single Active Directory forest only Multi-forest, multi-domain, or complex topologies
- Object Sizing < 100,000 objects Up to millions of objects (with Full SQL)
Database Engine SQL Server 2019/2022 Express LocalDB (local) Existing remote/local Full SQL Server or SQL Express
Authentication Mode Password Hash Synchronization (PHS) PHS, Pass-through Auth (PTA), AD FS Federation, or PingFederate
SourceAnchor Auto-configured ( mS-DS-ConsistencyGuid ) Admin-selectable ( mS-DS-ConsistencyGuid or custom attribute)
- Filtering Options Syncs all domains and all OUs Granular Domain, OU, and Attribute filtering
- Staging Mode Disabled (immediate live production sync) Configurable as an active server or Staging Mode server
Important
Express Settings Account Requirements: Running Express Settings requires an on-premises Enterprise Admin account (to automatically create the MSOL_ directory synchronization account with required replication permissions in AD DS) and a cloud Hybrid Identity Administrator or Global Administrator account.
Directory Filtering Mechanisms in Microsoft Entra Connect Sync
Filtering Type Configuration Location Operational Behavior & Exam Notes
Domain-Based Filtering Entra Connect Configuration Wizard Excludes entire Active Directory domains from the sync scope. Unchecked domains never enter the AD DS Connector Space.
OU-Based Filtering Entra Connect Configuration Wizard The recommended standard for production. Only selected Organizational Units are imported into the Connector Space. Objects moved into an unselected OU are deleted from Entra ID on the next sync cycle (placed in Entra ID Recycle Bin for 30 days).
Attribute-Based Filtering Synchronization Rules Editor Uses custom inbound sync rules to evaluate object attributes (e.g., checking if extensionAttribute15 equals NoSync or adminDescription contains DoNotSync ). Sets the internal cloudFiltered = True attribute in the Metaverse.
Group-Based Filtering Initial Wizard Installation Only Pilot deployments only. Filters synchronization based on membership in a single specified security group. Exam Trap: Group-based filtering cannot be re-enabled after initial setup, does not support nested groups, and is officially unsupported for ongoing production synchronization.