Study guide

3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

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.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

Key Takeaways Explain This Topic AI

AD DS speaks Kerberos, NTLM and LDAP to domain-joined machines; Microsoft Entra ID speaks OAuth 2.0, OpenID Connect and SAML to applications and has no LDAP or Kerberos surface of its own.

Directory synchronisation flows one way, from AD DS to Microsoft Entra ID; only password writeback, device writeback and group writeback move data back on-premises.

Microsoft Entra Domain Services synchronises from Microsoft Entra ID, not from AD DS directly, so an on-premises change reaches the managed domain only after it has first reached the tenant.

A verified custom domain in the tenant is required before on-premises UPN suffixes can synchronise; unverified suffixes are rewritten to onmicrosoft.com.

Choose Entra Domain Services when a legacy application needs Kerberos or LDAP but nobody wants to run domain controllers; choose IaaS domain controllers when schema extensions, forest trusts under your control, or Domain Admin rights are required.

Last updated: August 2026

Integrating Microsoft Entra ID, AD DS & Entra Domain Services

The previous five sections each covered one integration technology in isolation. The exam, and real design work, asks a harder question: given a workload, which identity plane should it use , and what does that choice imply about synchronisation, administration and cost. Getting this wrong is expensive — you either run domain controllers you did not need, or you discover mid-migration that the application requires an LDAP bind that Microsoft Entra ID cannot serve.

1. Three Identity Planes, Three Protocol Surfaces

AD DS (on-premises or IaaS) Microsoft Entra Domain Services Microsoft Entra ID

Protocols Kerberos, NTLM, LDAP/LDAPS, Group Policy Kerberos, NTLM, LDAP/LDAPS, Group Policy OAuth 2.0, OpenID Connect, SAML, WS-Fed, SCIM, Graph

Object model Forest, domains, OUs, extensible schema Managed domain, custom OUs, fixed schema Flat tenant — users, groups, service principals, devices

Highest privilege you hold Enterprise Admin / Domain Admin AAD DC Administrators (no Domain Admin) Global Administrator

Who patches the DCs You Microsoft Not applicable

Typical consumer Domain-joined servers, file shares, legacy line-of-business apps Lift-and-shift apps needing Kerberos or LDAP with no DC to run SaaS, modern web APIs, mobile apps, conditional access

The single most important line in that table is the protocol row. Microsoft Entra ID is not a domain controller. It exposes no LDAP endpoint and issues no Kerberos ticket-granting tickets for arbitrary services, so an application that performs an LDAP simple bind, or a file share that expects Kerberos, cannot be pointed at a tenant no matter how completely its users have been synchronised.

2. The Direction of Flow

Synchronisation is not symmetrical, and the exam tests the asymmetry directly.

Three consequences follow:

AD DS is the source of authority for synchronised objects. A synchronised user cannot be meaningfully edited in the tenant; the attribute is overwritten on the next sync cycle. Editing must happen on-premises.

Only three things flow back. Password writeback (self-service password reset), device writeback (Hybrid Entra join scenarios) and group writeback are the exceptions; everything else is one-way.

Entra Domain Services synchronises from the tenant, never from AD DS. An on-premises password change therefore reaches the managed domain only after it has first synchronised to Microsoft Entra ID — which is exactly why password hash synchronisation must be enabled for a hybrid Entra Domain Services deployment, even if the organisation authenticates with pass-through authentication or federation for everything else.

3. Tenant and Forest Boundaries

Rule Consequence

One AD DS forest can synchronise to one Microsoft Entra tenant You cannot split a forest across two tenants during a divestiture without filtering or a second forest

One tenant can receive objects from multiple forests Merger and acquisition topologies are supported without consolidating forests first

One active Microsoft Entra Connect Sync server per tenant, plus staging servers Two active sync servers writing to the same tenant is unsupported and produces attribute thrash

Microsoft Entra Cloud Sync agents can run alongside Connect Sync Provided the two are scoped to disjoint sets of objects

A managed domain's DNS name is chosen at creation and is immutable Choose a routable name you own, distinct from the on-premises domain name

Custom domains matter more than they first appear. Before an on-premises UPN suffix such as @corp.contoso.com can survive synchronisation, the corresponding domain must be added and verified in the tenant. If it is not, every synchronised user is issued a UPN in the tenant's default <tenant>.onmicrosoft.com namespace, which breaks single sign-on because the user signs in with one name on-premises and a different one in the cloud. The non-routable .local suffix is the classic version of this failure: contoso.local can never be verified, so the forest must be given an alternative routable UPN suffix before synchronisation.

4. The Decision Framework

Work down this list and stop at the first row that matches:

If the workload needs… Choose Because

Schema extensions, Domain Admin rights, your own forest trusts, or full Group Policy control Domain controllers in Azure IaaS Only a forest you own exposes the schema and the top-level administrative groups

Kerberos, NTLM, LDAP or Group Policy, but no appetite to run or patch domain controllers Microsoft Entra Domain Services Microsoft operates the domain; you administer through AAD DC Administrators and custom OUs

Only modern authentication — OAuth, OIDC, SAML — plus conditional access and MFA Microsoft Entra ID alone No domain services are needed at all; adding them is pure cost

LDAP reads from a cloud-only application, with no on-premises directory at all Microsoft Entra Domain Services with secure LDAP Provides an LDAPS endpoint that the tenant itself does not expose

Existing on-premises identities extended to cloud applications AD DS + Entra Connect Sync or Cloud Sync Keeps AD DS authoritative while projecting identities into the tenant

Important

The exam's favourite scenario is a lift-and-shift line-of-business application that performs an LDAP bind and is being moved to Azure, where the customer explicitly states they do not want to manage domain controllers. Microsoft Entra ID cannot serve it; Azure IaaS domain controllers contradict the stated constraint. Microsoft Entra Domain Services is the answer that satisfies both halves of the requirement.

5. Reading the Requirement Correctly

Two phrases in a scenario change the answer entirely:

"Must not manage domain controllers" / "no patching or backup overhead" points at Entra Domain Services, which is a managed service Microsoft patches and backs up.

"Must extend the schema" / "requires Domain Admin" / "must establish a trust with a partner forest we control" points at IaaS domain controllers, because Entra Domain Services offers a fixed schema and no Domain Admin or Enterprise Admin membership.

And one phrase is a decoy: "users must sign in with their corporate credentials" is satisfied by every option in the table, because all three planes ultimately draw their identities from the same synchronised set. It never discriminates between architectures on its own.

Loading diagram... Directional Flow Between AD DS, Microsoft Entra ID and Entra Domain Services