Study guide
3.5 Microsoft Entra Domain Services
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.5 Microsoft Entra Domain Services
Key Takeaways Explain This Topic AI
Microsoft Entra Domain Services provides managed Active Directory domain controllers as a cloud PaaS service, supporting Kerberos, NTLM, LDAPS, DNS, and Group Policy without managing IaaS VMs.
Directory synchronization operates strictly one-way from Microsoft Entra ID to Entra Domain Services; objects created in the managed domain never replicate back to Entra ID or on-premises AD DS.
Secure LDAP (LDAPS) requires a valid .PFX certificate containing the domain DNS name or wildcard, external DNS records, and an NSG rule permitting inbound TCP port 636 from authorized management IP ranges.
To support multi-region disaster recovery and low-latency cloud authentication, up to five replica sets can be deployed across distinct Azure regions in peered Virtual Networks.
Administrative access is restricted to the AAD DC Administrators group with delegated control over AADDC Users and Computers OUs; Domain Admins, Enterprise Admins, and Schema Admins roles do not exist.
Last updated: August 2026
Microsoft Entra Domain Services
Many enterprise workloads and legacy line-of-business applications migrating to Microsoft Azure rely on traditional Active Directory protocols—such as Kerberos authentication, NTLM, Lightweight Directory Access Protocol (LDAP/LDAPS), DNS name resolution, and Group Policy Objects (GPOs) . However, deploying, patching, backing up, and securing dedicated Windows Server domain controller virtual machines in Azure IaaS introduces significant administrative overhead.
Microsoft Entra Domain Services provides fully managed domain services in Azure as a Platform-as-a-Service (PaaS) solution, delivering full protocol compatibility with legacy Active Directory without requiring administrators to manage domain controller infrastructure.
1. Managed Domain Architecture & Synchronization Flow
When Microsoft Entra Domain Services is provisioned, Azure deploys two redundant managed domain controllers into a dedicated subnet within an Azure Virtual Network (VNet). +-----------------------------------------------------------------------------------+
- | MICROSOFT ENTRA DOMAIN SERVICES ARCHITECTURE & FLOW |
- | |
- | [On-Premises AD DS] -----> (Entra Connect) -----> [Microsoft Entra ID] |
- | | |
- | (One-Way Sync) |
- | v |
- | +------------------------------------------------------------------------------+ |
- | | AZURE VIRTUAL NETWORK | |
- | | +------------------------------------------------------------------------+ | |
- | | | Dedicated Subnet: aadds-subnet (No other VMs or NICs allowed) | | |
- | | | [Managed DC 01] [Managed DC 02] | | |
- | | | - Kerberos / NTLM - Kerberos / NTLM | | |
- | | | - LDAP / Secure LDAPS (TCP 636) - LDAP / Secure LDAPS (TCP 636) | | |
- | | | - DNS Server - DNS Server | | |
- | | +------------------------------------------------------------------------+ | |
- | | | (VNet Peering) | |
- | | +------------------------------------------------------------------------+ | |
- | | | Application Subnet: Workload VMs (Joined to aadds.contoso.com) | | |
- | | | [Legacy App VM 01] [Legacy App VM 02] | | |
- | | +------------------------------------------------------------------------+ | |
- | +------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------+
Core Architectural Principles:
Dedicated Subnet Requirement: The managed domain controllers must be deployed in a dedicated subnet inside an Azure VNet. This subnet cannot contain standard workload VMs, storage endpoints, or other network interfaces.
One-Way Unidirectional Synchronization: Identity data synchronizes strictly from Microsoft Entra ID into Microsoft Entra Domain Services .
Objects (users, groups, credentials) created in Entra ID (or synced from on-premises AD DS) appear in Entra Domain Services.
Critical Rule: You cannot create users or groups directly in Entra Domain Services and have them sync back to Entra ID or on-premises AD DS. The cloud directory is the authoritative master.
Supported Protocols: Windows and Linux IaaS VMs joined to the managed domain can authenticate via Kerberos or NTLM , perform directory searches via LDAP/LDAPS , query domain DNS , and apply Group Policy Objects (GPOs) .
Comparison: Entra Domain Services vs. IaaS Domain Controllers vs. Entra ID
- Dimension Microsoft Entra ID Entra Domain Services Windows Server IaaS DCs
- Service Model Identity-as-a-Service (Cloud) Platform-as-a-Service (Managed) Infrastructure-as-a-Service (VMs)
Primary Protocols OAuth 2.0, OIDC, SAML, WS-Fed Kerberos, NTLM, LDAP/LDAPS, DNS Kerberos, NTLM, LDAP/LDAPS, DNS
- Device Joining Entra Joined / Registered Domain Joined (Traditional AD) Domain Joined (Traditional AD)
- Group Policy Support None (Intune MDM policies) Yes (Built-in & Custom GPOs) Yes (Full GPO control)
- Schema Extensions Directory Extension Attributes No (Schema is locked) Yes (Full Schema Admin)
- Administrative Scope Global / Identity Administrator AAD DC Administrators Group Domain / Enterprise Admins
- Forest Trust Support None One-Way Outbound (Resource Forest) Two-Way / Transitive Trusts
2. Password Hash Synchronization Prerequisites for Entra Domain Services
Kerberos and NTLM authentication require password hashes in legacy cryptographic formats ( NTLM hashes and Kerberos keys ). Microsoft Entra ID does not generate or store NTLM/Kerberos credential hashes by default for standard cloud authentication. +-----------------------------------------------------------------------------------+
- | PASSWORD HASH GENERATION REQUIREMENTS |
- | |
- | [1. HYBRID SYNCHRONIZED ACCOUNTS] |
- | - Must have Password Hash Synchronization (PHS) enabled in Entra Connect. |
- | - Entra Connect extracts and syncs NTLM hashes to Entra ID. |
- | - Hashes are then automatically populated into Entra Domain Services. |
- | |
- | [2. CLOUD-ONLY USER ACCOUNTS] |
- | - Entra ID does NOT have legacy NTLM hashes for cloud-created users. |
- | - Cloud users MUST change or reset their password once via Azure Portal |
- | or SSPR to generate and store the required NTLM/Kerberos hashes. |
- +-----------------------------------------------------------------------------------+
Important
Cloud User Password Change Requirement: After enabling Microsoft Entra Domain Services, cloud-only user accounts cannot authenticate to the managed domain until they perform a password change or reset . Changing the password triggers the cloud authentication service to compute and store the legacy NTLM hash required by the managed domain controllers.
3. Secure LDAP (LDAPS) Configuration & Hardening
To allow applications hosted in external VNets, on-premises networks, or over the Internet to query the managed domain, Secure LDAP (LDAPS / TCP port 636) must be configured. +-----------------------------------------------------------------------------------+
- | SECURE LDAPS DEPLOYMENT STEPS |
- | |
- | [1. OBTAIN CERTIFICATE] ---> .PFX containing private key, Key Length >= 2048-bit|
- | Subject / SAN: *.aadds.contoso.com or exact FQDN |
- | | |
- | v |
- | [2. ENABLE IN PORTAL] ---> Upload .PFX to Entra Domain Services blade |
- | Toggle: "Secure LDAP" = Enabled |
- | Toggle: "Allow Secure LDAP access over Internet" |
- | | |
- | v |
- | [3. EXTERNAL DNS] ---> Create public DNS A record (ldaps.contoso.com) |
- | pointing to the external IP displayed in portal |
- | | |
- | v |
- | [4. NSG LOCKDOWN] ---> Inbound Rule: Allow TCP 636 from specific |
- | management IP addresses only (Deny 0.0.0.0/0) |
- +-----------------------------------------------------------------------------------+
Certificate Prerequisites:
Format: PKCS#12 ( .pfx ) file containing the private key and full certificate chain.
Subject Name / SAN: Must match the managed domain's DNS name (e.g., aadds.contoso.com ) or use a wildcard matching the domain (e.g., *.aadds.contoso.com ).
Trust: Must be issued by a trusted public Certificate Authority (CA) or an enterprise internal CA whose root certificate is installed on all querying client machines.
Network Security Group (NSG) Rule Configuration:
When external LDAPS is enabled, Azure assigns an external public IP address to the managed domain controllers. You must configure an NSG rule on the dedicated subnet:
- Protocol: TCP
- Destination Port: 636
Source: Restrict strictly to authorized corporate public IP CIDR ranges. Never leave source set to Any (0.0.0.0/0) to prevent LDAP brute-force and amplification attacks.
4. Multi-Region Resilience: Replica Sets
For enterprise workloads distributed across multiple Azure regions, Microsoft Entra Domain Services supports Replica Sets . +-----------------------------------------------------------------------------------+
- | MULTI-REGION REPLICA SET ARCHITECTURE |
- | |
- | +-----------------------------+ +-----------------------------+ |
- | | PRIMARY REGION: EAST US | | REPLICA REGION: WEST US | |
- | | Subnet: 10.10.0.0/24 | | Subnet: 10.20.0.0/24 | |
- | | [Managed DC 01] [Managed DC 02] | [Replica DC 01] [Replica DC 02] |
- | +-----------------------------+ +-----------------------------+ |
- | ^ ^ |
- | |========== (Azure VNet Peering) =============| |
- | (AD DS Intra-Domain Replication) |
- +-----------------------------------------------------------------------------------+
Key Capabilities of Replica Sets:
Multi-Region Redundancy: Deploy up to 5 replica sets (1 primary + 4 replicas) across distinct Azure regions sharing the same managed domain namespace.
Low Latency: Workload VMs in secondary regions authenticate locally against replica domain controllers rather than traversing cross-region VNets.
VNet Peering Requirement: All VNets hosting replica sets must be connected using full-mesh Azure Virtual Network Peering to allow intra-domain Active Directory replication between managed domain controllers.
5. Administrative Model & Hard Limitations
Microsoft Entra Domain Services enforces strict administrative boundaries to maintain PaaS platform integrity.
The AAD DC Administrators Group:
Members of this built-in group receive delegated administrative rights:
Join virtual machines to the managed domain.
Access and manage the AADDC Computers and AADDC Users Organizational Units (OUs).
Create and manage custom child OUs, custom Group Policy Objects (GPOs), and DNS records using standard Remote Server Administration Tools (RSAT).
Hard Platform Boundaries (Critical Exam Traps):
No Domain Admins or Enterprise Admins: You are never granted Domain Admins or Enterprise Admins group membership.
No Schema Extensions: The Active Directory schema is locked; third-party applications requiring schema modifications cannot be installed.
No Direct RDP/SSH to Domain Controllers: Administrators cannot establish Remote Desktop or PowerShell remoting sessions directly to the underlying managed domain controller VMs.
Trust Creation (SKU Dependent): Standard managed domains do not support creating domain trusts. However, the Enterprise / Resource Forest SKU supports creating a one-way outbound forest trust from Entra Domain Services to an on-premises Active Directory forest, allowing on-premises users to access cloud resources using Kerberos without syncing user passwords to the cloud.