Study guide
1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning
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
1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning
Key Takeaways Explain This Topic AI
An Azure IaaS domain controller must use a static private IP configured on the Azure VNet NIC object, not inside the guest OS, and the VNet's custom DNS servers must point at the domain controllers.
The AD database (NTDS.dit), logs, and SYSVOL must sit on a dedicated Azure managed data disk with Host Caching set to None, because write-back caching can violate the directory's write-ordering guarantees.
Domain Controller Cloning is the only supported image-copy DC deployment method; it relies on VM-GenerationID and a DCCloneConfig.xml answer file.
Cloning prerequisites include an online PDC Emulator running Windows Server 2012 or later, source DC membership in the Cloneable Domain Controllers group, and no unsupported services reported by Get-ADDCCloningExcludedApplicationList.
Azure IaaS domain controllers should be spread across Availability Zones or an Availability Set so a single rack or datacenter fault cannot remove every authentication endpoint in the region.
Last updated: August 2026
- Domain Controllers in Azure IaaS & Virtualized DC Cloning
- 1. Azure IaaS Virtual Machine Domain Controller Best Practices
Deploying Active Directory Domain Controllers onto Azure IaaS Virtual Machines introduces distinct architectural constraints governing virtual networking, storage write caching, and high-availability placement. +-----------------------------------------------------------------------------+
- | AZURE IAAS VM DOMAIN CONTROLLER ARCHITECTURE |
- | |
- | [AZURE VIRTUAL NETWORK (VNet)] |
- | +---------------------------------------------------------------------+ |
- | | Subnet: 10.10.1.0/24 | |
- | | | |
- | | +-----------------------------+ +-----------------------------+ | |
- | | | VM: AZ-DC01 (Zone 1) | | VM: AZ-DC02 (Zone 2) | | |
- | | | Azure NIC Private IP: | | Azure NIC Private IP: | | |
- | | | Static = 10.10.1.4 | | Static = 10.10.1.5 | | |
- | | | (OS Adapter = DHCP!) | | (OS Adapter = DHCP!) | | |
- | | | | | | | |
- | | | [OS Disk C:] (Cache: R/W) | | [OS Disk C:] (Cache: R/W) | | |
- | | | | | | | |
- | | | [Data Disk F:] | | [Data Disk F:] | | |
- | | | - NTDS.dit & Logs | | - NTDS.dit & Logs | | |
- | | | - Host Caching: NONE | | - Host Caching: NONE | | |
- | | +-----------------------------+ +-----------------------------+ | |
- | +---------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------+
Critical Azure IaaS Rules for Domain Controllers:
IP Addressing Configuration (The VNet Rule):
Azure VNet NIC Level: MUST be configured with Static Private IP Allocation in the Azure portal, Azure CLI, or Bicep/ARM template.
Guest OS Level: MUST remain set to Obtain an IP address automatically (DHCP) .
Why? If an administrator manually assigns a static IP within the Windows Server guest network adapter properties, any change in Azure VNet routing or DHCP lease renewal can cause the VM to lose network connectivity, severing communication with Azure fabric management agents.
Disk Layout and Host Write Caching (The Integrity Rule):
Dedicated Data Disk: AD DS database ( NTDS.dit ), transaction logs ( edb.log ), and SYSVOL must reside on an attached data disk (Standard SSD or Premium SSD), NEVER on the OS disk ( C: ) or the Azure Temporary Disk ( D: ).
Host Caching Policy: Host Caching on the dedicated AD DS data disk MUST be set to None (or ReadOnly ).
Why? Azure OS disks have Read/Write host caching enabled by default. If a host crash occurs while writes are buffered in hypervisor host memory, uncommitted transactions are lost, causing Extensible Storage Engine (ESE) database corruption and irreversible Update Sequence Number (USN) rollback.
Temporary Disk Prohibition: The Azure temporary disk ( D: ) is volatile and wiped upon VM resizing, host migration, or deallocation. Storing NTDS or SYSVOL on D: causes immediate domain controller failure upon reboot.
Resilience & Availability Architecture:
Deploy at least two domain controllers per domain in Azure across distinct Availability Zones (e.g., Zone 1 and Zone 2 in regions that support zones) or within an Availability Set (minimum 2 Fault Domains and 2 Update Domains).
Configure the Azure Virtual Network DNS server settings to list the private IP addresses of the Azure domain controllers, with fallbacks to on-premises DNS servers across ExpressRoute or Site-to-Site VPN.
2. Domain Controller Virtualization & Cloning ( dccloneconfig.xml )
Domain Controller Cloning allows rapid deployment of new virtualized domain controllers by copying an existing virtualized DC's virtual hard disk (VHDX), bypassing the traditional promotion process. +-----------------------------------------------------------------------------+
- | VIRTUALIZED DC CLONING WORKFLOW |
- | |
- | [1. SOURCE DC PREREQUISITES] |
- | - Hypervisor supports VM-GenerationID (Hyper-V / Azure) |
- | - PDC Emulator online & running Windows Server 2012+ |
- | - Source DC added to 'Cloneable Domain Controllers' security group |
- | | |
- | v |
- | [2. APPLICATION ALLOWLIST] |
- | - Run: Get-ADDCCloningExcludedApplicationList |
- | - Generate: New-ADDCCloneConfigFile / CustomDCCloneAllowList.xml |
- | | |
- | v |
- | [3. CLONE CONFIGURATION] |
- | - Author dccloneconfig.xml in %SystemRoot%\NTDS folder |
- | - Specify: CloneComputerName, SiteName, IPAddress, SubnetMask, DNS |
- | | |
- | v |
- | [4. VM SNAPSHOT / COPY & BOOT] |
- | - Shut down source VM, copy VHDX, create new VM attached to copy |
- | - Hypervisor presents new VM-GenID -> NTDS detects dccloneconfig.xml |
- | - DC initializes new invocation ID, resets SID, joins replication topology|
- +-----------------------------------------------------------------------------+
Cloning Prerequisites & Artifacts:
VM-GenerationID (VM-GenID): The hypervisor (Hyper-V Windows Server 2012+ or Azure IaaS) exposes a 128-bit integer via the ACPI table. When a VM is cloned or restored from a snapshot, the hypervisor changes this ID. Active Directory detects the change and safely resets its local invocation ID and discards its RID pool to prevent USN rollback.
Cloneable Domain Controllers Security Group: The source DC computer object must be added as a member of this built-in domain security group.
Application Allowlist Files:
DefaultDCCloneAllowList.xml : Located in %SystemRoot%\System32 , containing Microsoft-tested services and applications safe for cloning.
CustomDCCloneAllowList.xml : Located in %SystemRoot%\NTDS , generated via PowerShell to permit third-party services that pass cloning compatibility checks.
- dccloneconfig.xml Syntax: <configurations>
- <configuration>
- <IPv4Configuration>
- <IPAddress>10.10.1.6</IPAddress>
- <SubnetMask>255.255.255.0</SubnetMask>
- <DefaultGateway>10.10.1.1</DefaultGateway>
- <DNSClient>10.10.1.4</DNSClient>
- <PreferredWINSServer></PreferredWINSServer>
- <AlternateWINSServer></AlternateWINSServer>
- </IPv4Configuration>
- <Position>Top</Position>
- <SiteName>Azure-EastUS</SiteName>
- <ComputerName>AZ-DC03</ComputerName>
- </configuration>
- </configurations>
Caution
Sysprep Prohibition on Domain Controllers: NEVER run sysprep.exe /generalize on a domain controller. Sysprep is completely unsupported on active DCs and corrupts directory databases and machine security identifiers. DC Cloning via dccloneconfig.xml is the only supported image-copy deployment method.
3. Upgrading, Demoting, and Metadata Cleanup
When retiring legacy domain controllers or migrating to newer Windows Server versions, administrators must follow structured decommissioning protocols.
Graceful Demotion with PowerShell
To retire a functional domain controller, execute Uninstall-ADDSDomainController : # Gracefully demote an additional domain controller
$LocalAdminPassword = ConvertTo-SecureString 'LocalAdminP@ss2026!' -AsPlainText -Force
- Uninstall-ADDSDomainController `
- DemoteOperationMasterRole:$true `
- RemoveDnsDelegation:$true `
- LocalAdministratorPassword $LocalAdminPassword `
- Force:$true
- Forceful Demotion & Metadata Cleanup
If a domain controller suffers catastrophic hardware failure and cannot be brought online, it must be forcefully demoted and its directory metadata purged:
Run Uninstall-ADDSDomainController -ForceRemoval -LocalAdministratorPassword $pwd on the damaged server (if bootable) to strip local AD DS binaries.
On a healthy surviving DC, open Active Directory Users and Computers , locate the failed DC under the Domain Controllers OU, and delete the computer object. In Windows Server 2012 and later, deleting the DC object automatically triggers automated metadata cleanup , removing the nTDSSettings object, replication connection objects, and FRS/DFSR references.
Verify cleanup in Active Directory Sites and Services under the relevant site's Servers container, and manually delete orphaned DNS SRV records in the _msdcs.<ForestRoot> zone using DNS Manager.