Study guide

3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies

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.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies

Key Takeaways Explain This Topic AI

Microsoft Entra Cloud Sync relocates the compute-intensive sync engine and metaverse into the Microsoft Entra cloud control plane, relying on lightweight on-premises provisioning agents.

Cloud Sync natively supports disconnected multi-forest topologies where isolated corporate networks have no Active Directory forest trusts, network routing, or site-to-site VPNs between them.

High availability is achieved by deploying multiple lightweight provisioning agents within the same domain, allowing automatic active-active failover without clustered infrastructure.

Cloud Sync operates on a rapid 2-minute synchronization cycle (micro-batches) compared to the default 30-minute scheduler interval in Entra Connect Sync.

While Cloud Sync supports user, group, contact, and gMSA synchronization alongside password hash sync and password writeback, legacy features like device writeback require traditional Entra Connect Sync.

Last updated: August 2026

Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies

As enterprise organizations evolve through global expansion, corporate divestitures, and mergers and acquisitions (M&A), identity architectures often span multiple disparate Active Directory forests. Traditional Microsoft Entra Connect Sync requires a heavyweight on-premises server footprint with line-of-sight network connectivity to every domain controller across all synchronized forests.

Microsoft Entra Cloud Sync represents a modern, cloud-first synchronization paradigm that moves the synchronization rules engine, metaverse processing, and transformation logic into the Microsoft Entra ID cloud service, utilizing lightweight on-premises provisioning agents to bridge isolated directories.

1. Microsoft Entra Cloud Sync Architecture

Unlike traditional Entra Connect Sync where the synchronization engine and database reside on a dedicated Windows Server on-premises, Microsoft Entra Cloud Sync decouples the data collection mechanism from the synchronization compute engine. +-----------------------------------------------------------------------------------+

  • | MICROSOFT ENTRA CLOUD SYNC MULTI-FOREST ARCHITECTURE |
  • | |
  • | +------------------------------------------------------------------------------+ |
  • | | MICROSOFT ENTRA ID CLOUD | |
  • | | - Cloud Synchronization Engine & Metaverse | |
  • | | - Expression-Based Attribute Mapping Engine | |
  • | | - Portal-Managed Scoping Filters & Monitoring | |
  • | +------------------------------------------------------------------------------+ |
  • | ^ (Outbound HTTPS 443) ^ (Outbound HTTPS 443)|
  • | | | |
  • | +---------------------------+ +---------------------------+ |
  • | | FOREST A: CORP (HQ) | | FOREST B: ACQUIRED ENTITY | |
  • | | [Provisioning Agent 01] | | [Provisioning Agent 03] | |
  • | | [Provisioning Agent 02] | | [Provisioning Agent 04] | |
  • | | (High Availability Group)| | (Isolated Perimeter) | |
  • | +---------------------------+ +---------------------------+ |
  • | * No Forest Trust Required * * No Network VPN Required * |
  • +-----------------------------------------------------------------------------------+

Core Architectural Characteristics:

Cloud-Hosted Metaverse & Sync Engine: All attribute precedence, mapping logic, object reconciliation, and join rules execute within the Microsoft Entra ID cloud control plane. On-premises servers do not require SQL Server instances or extensive RAM/CPU resources.

Lightweight On-Premises Provisioning Agent: A minimal service ( AADConnectProvisioningAgent.exe ) installed on a domain-joined Windows Server 2016/2019/2022. The agent communicates strictly outbound over HTTPS (port 443) to the cloud provisioning service.

Rapid Synchronization Frequency: Cloud Sync processes changes in continuous micro-batches every 2 minutes , dramatically reducing attribute propagation latency compared to Entra Connect Sync's default 30-minute sync cycle.

Built-In High Availability: Multiple provisioning agents can be installed in the same Active Directory domain. The cloud service automatically distributes workload and manages failover across active agents without requiring failover clustering or manual Staging Mode promotion.

Comprehensive Feature Matrix: Entra Connect Sync vs. Entra Cloud Sync

  • Architectural Feature Microsoft Entra Connect Sync Microsoft Entra Cloud Sync
  • Sync Engine Location On-Premises Windows Server Microsoft Entra ID Cloud Service
  • Database Requirement SQL Server Express (10GB) or Full SQL Server Cloud-managed (No on-prem database)
  • Agent / Server Footprint Heavyweight (Dedicated 4-8 vCPU, 16-32 GB RAM) Lightweight Agent (2 vCPU, 4 GB RAM)
  • High Availability Model Active / Passive (Staging Mode required) Active / Active (Multi-agent cloud pooling)

Sync Interval 30 minutes by default; CustomizedSyncCycleInterval can only make it less frequent, because AllowedSyncCycleInterval is the floor Microsoft Entra ID enforces, and a delta sync must still run within 7 days 2 minutes (near real-time micro-batches)

Disconnected Forest Support No (Requires network line-of-sight to all DCs) Yes (Agents communicate outbound via HTTPS)

  • Password Hash Sync (PHS) Supported Supported
  • Password Writeback (SSPR) Supported Supported
  • Group Writeback Supported (M365 & Security Groups) Supported (Cloud Security & M365 Groups)
  • Device Writeback Supported Not Supported

Custom Directory Extensions Up to 100 attributes via GUI/PowerShell Supported (via Cloud Portal directory schema)

Exchange Hybrid Attributes Full support (msExchMailboxGuid, etc.) Supported for standard hybrid mailbox sync

2. Disconnected Multi-Forest & Merger/Acquisition Scenarios

A primary architectural driver for deploying Microsoft Entra Cloud Sync is integrating isolated, non-routable, or disconnected Active Directory forests into a single centralized Microsoft Entra tenant.

M&A Deployment Blueprint:

When an organization acquires a subsidiary with an existing Active Directory forest ( subsidiary.local ):

Traditional Connect Sync Challenge: To use traditional Entra Connect Sync, network engineers would need to establish site-to-site IPsec VPNs or ExpressRoute connections, configure complex DNS conditional forwarders, resolve overlapping IP address spaces (NAT), and open extensive firewall ports (TCP 389, 636, 88, 53, 445, 135, 49152-65535) between the sync server and the subsidiary DCs.

Cloud Sync Solution: The administrator simply deploys two lightweight provisioning agents onto domain member servers inside the subsidiary's network. The agents establish outbound HTTPS connections over TCP port 443 to Microsoft Entra ID. No site-to-site VPN, no forest trusts, and no inbound firewall openings are required. +-----------------------------------------------------------------------------------+

  • | COEXISTENCE: CONNECT SYNC AND CLOUD SYNC IN ONE TENANT |
  • | |
  • | +------------------------------------------------------------------------------+ |
  • | | SINGLE MICROSOFT ENTRA TENANT | |
  • | +------------------------------------------------------------------------------+ |
  • | ^ ^ |
  • | | (Connect Sync Pipeline) | (Cloud Sync Agent) | |
  • | +--------------------------+ +---------------------------+ |
  • | | HQ FOREST (CORP) | | ACQUIRED DISCONNECTED | |
  • | | - 80,000 Users | | FOREST | |
  • | | - Device Writeback | | - 12,000 Users | |
  • | | - Exchange Hybrid | | - Password Hash Sync | |
  • | +--------------------------+ +---------------------------+ |
  • | |
  • | CRITICAL RULE: Never synchronize the same OU or object with BOTH tools. |
  • +-----------------------------------------------------------------------------------+

Warning

Dual-Homed Synchronization Conflict: While Entra Connect Sync and Entra Cloud Sync can coexist within the same Microsoft Entra tenant, a single user or group object must never be in scope for both synchronization engines simultaneously . Dual-scoping creates severe attribute conflicts, identity flapping, and corrupted Metaverse anchor bindings.

3. Provisioning Agent Network Requirements & Troubleshooting

Provisioning agents require reliable outbound connectivity to Microsoft Entra cloud endpoints.

Network and Firewall Rules:

Outbound Ports Only: TCP Port 443 (HTTPS) and TCP Port 80 (used strictly for downloading certificate revocation lists [CRLs] and OCSP validation during TLS handshakes).

No Inbound Ports: No incoming firewall ports are ever opened on the on-premises perimeter.

Key Endpoint FQDNs:

  • *.msappproxy.net
  • *.servicebus.windows.net
  • login.microsoftonline.com
  • mscrl.microsoft.com:80 and crl.microsoft.com:80

Troubleshooting Agent Connectivity:

If a provisioning agent fails to appear as Active in the Microsoft Entra admin center:

Verify Windows Service Status: Ensure the service Microsoft Entra Connect Agent Updater and Microsoft Entra Connect Provisioning Agent are running under the configured Group Managed Service Account (gMSA) or virtual account.

Review Trace Logs: Inspect the primary agent log located on the host server at: C:\ProgramData\Microsoft\Azure AD Connect Provisioning Agent\Trace\AADConnectProvisioningAgent.log

Event Viewer Channels: Navigate to Applications and Services Logs > Microsoft > Azure AD Connect > ProvisioningAgent > Admin for detailed TLS handshake errors, network proxy authentication failures, or expired tenant registration tokens.

PowerShell Diagnostics: Utilize the built-in diagnostic module to test end-to-end communication with Microsoft cloud service bus endpoints: # Importing and running the Cloud Sync Agent Diagnostic Tool

Import-Module "C:\Program Files\Microsoft Azure AD Connect Provisioning Agent\Utility\Diagnostics\Microsoft.AzureADConnect.ProvisioningAgent.Diagnostics.dll"

  • Test-AADCloudSyncAgentConnectivity
  • 4. Scoping Filters & Expression-Based Attribute Mappings

In Microsoft Entra Cloud Sync, attribute transformations and object scoping are configured entirely within the Microsoft Entra Admin Center under Identity > Hybrid management > Microsoft Entra Connect > Cloud sync .

Scoping Filters:

Scoping filters restrict synchronization based on:

Organizational Unit (OU): Target specific distinguished names (e.g., OU=Users,OU=NorthAmerica,DC=corp,DC=contoso,DC=com ).

Attribute-Based Scoping: Filter objects based on attribute expressions (e.g., synchronizing only objects where department EQUALS 'Engineering' or extensionAttribute1 IS NOT NULL ).

Common Transformation Functions: +-----------------------------------------------------------------------------------+

  • | CLOUD SYNC TRANSFORMATION EXPRESSION EXAMPLES |
  • | |
  • | 1. Stripping Whitespace: |
  • | StripSpaces([userPrincipalName]) |
  • | |
  • | 2. Conditional Fallback: |
  • | IIF(IsNullOrEmpty([mail]), [userPrincipalName], [mail]) |
  • | |
  • | 3. Constructing Composite UPN: |
  • | Join("@", NormalizeDiacritics(StripSpaces([sAMAccountName])), "contoso.com") |
  • | |
  • | 4. Substring Extraction: |
  • | Mid([department], 1, 3) |
  • | |
  • | 5. DateTime Formatting: |
  • | FormatDateTime([accountExpires], "yyyyMMddHHmmss.0Z") |
  • +-----------------------------------------------------------------------------------+

Tip

Testing Attribute Expressions Safely: Use the Provision on Demand feature in the Entra Cloud Sync portal. Enter the distinguished name of a single on-premises user to simulate attribute mappings and view immediate step-by-step evaluation results before saving the configuration for the entire directory.