Study guide

2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID

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

2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID

Key Takeaways Explain This Topic AI

Standard domain joins require bidirectional connectivity over critical ports (DNS 53, Kerberos 88, LDAP 389, SMB 445) and proper DNS resolution pointing directly to domain controllers rather than public or ISP DNS.

Offline Domain Join (ODJ) utilizes djoin.exe to provision a metadata blob on a domain controller (/provision) and inject it into an isolated target machine (/requestODJ) without requiring network connectivity to a DC during OS installation.

Azure IaaS VMs are joined to on-premises AD DS or Microsoft Entra Domain Services using the JsonADDomainExtension VM extension, requiring that the Azure Virtual Network DNS servers point to the domain's private IP addresses.

Microsoft Entra Domain Services provides managed LDAP, Kerberos, and NTLM services in Azure; domain join requires membership in the 'AAD DC Administrators' group and placing computers into the 'AADDC Computers' OU or sub-OUs.

A broken secure channel between a domain-joined Windows Server and AD DS (frequently caused by hypervisor snapshot rollbacks) can be repaired without unjoining using 'Test-ComputerSecureChannel -Repair -Credential (Get-Credential)'.

Last updated: August 2026

Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID

Joining a Windows Server to an identity provider establishes a cryptographic trust boundary between the operating system's Local Security Authority (LSA) and the centralized directory service. In hybrid cloud architectures, administrators must join Windows Server instances to traditional Active Directory Domain Services (AD DS) on-premises, Microsoft Entra Domain Services in Azure virtual networks, and Microsoft Entra ID for cloud-native governance.

Understanding the network mechanics, automation options, offline provisioning capabilities, and troubleshooting protocols is vital for administering Windows Server hybrid core infrastructures.

1. Standard Domain Join Mechanics & Network Prerequisites

When a Windows Server joins an Active Directory domain, the client initiates the DC Locator process using DNS SRV records ( _ldap._tcp.dc._msdcs.<DomainName> ). It authenticates using administrative credentials, creates a computer object in the target Organizational Unit (OU), establishes a shared secret password for the machine account ( ComputerName$ ), and sets up a secure Netlogon channel. +-----------------------------------------------------------------------------------+

  • | DOMAIN JOIN NETWORK PORT MATRIX |
  • | |
  • | [JOINING SERVER] [DOMAIN CONTROLLER] |
  • | | | |
  • | |--- UDP/TCP 53 (DNS Name Resolution & SRV Records)------>| |
  • | |--- UDP/TCP 88 (Kerberos Authentication & TGT Request)-->| |
  • | |--- TCP 135 (RPC Endpoint Mapper)----------------------->| |
  • | |--- TCP/UDP 389 (LDAP Directory Search & Account Bind)-->| |
  • | |--- TCP 445 (SMB & Named Pipes / IPC$)------------------>| |
  • | |--- UDP/TCP 464 (Kerberos Password Change / Set Machine)->| |
  • | |--- TCP 49152-65535 (RPC Dynamic High Ports)------------>| |
  • | |--- UDP 123 (W32Time / NTP Clock Synchronization)------->| |
  • +-----------------------------------------------------------------------------------+

Standard Domain Join via PowerShell and Netdom # Perform standard domain join and place into specific OU with immediate restart

  • Add-Computer -DomainName "contoso.com" `
  • Credential (Get-Credential) `
  • OUPath "OU=AppServers,OU=Servers,DC=contoso,DC=com" `
  • Restart
  • # Command-line alternative using netdom.exe
  • netdom join Server01 /Domain:contoso.com /OU:"OU=AppServers,DC=contoso,DC=com" `
  • /UserD:CONTOSO\AdminUser /PasswordD:* /Reboot:30

Important

DNS Configuration Is Critical: More than 80% of domain join failures stem from incorrect DNS configuration. The joining server's network adapter must point to domain controllers running Active Directory-Integrated DNS . Pointing the adapter to a public DNS resolver (such as 8.8.8.8 or Azure default DNS 168.63.129.16 ) will cause domain join failure with error 0x54B ( ERROR_NO_SUCH_DOMAIN ).

2. Offline Domain Join (ODJ) Using djoin.exe

Offline Domain Join (ODJ) allows an administrator to provision a computer account in Active Directory and inject the domain join metadata into a client operating system without requiring network connectivity between the target machine and a domain controller during OS deployment. +-----------------------------------------------------------------------------------+

  • | OFFLINE DOMAIN JOIN (ODJ) WORKFLOW |
  • | |
  • | [PROVISIONING PHASE (Online DC or Domain Machine)] |
  • | - Run: djoin.exe /provision /domain contoso.com /machine VM-EDGE01 |
  • | /savefile C:\ODJ\provision.txt |
  • | - Creates computer account 'VM-EDGE01$' in AD DS. |
  • | - Outputs base64-encoded metadata blob (machine password, domain SID, DCs). |
  • | | |
  • | | Securely transfer provision.txt (USB / Azure Script / Sysprep) |
  • | v |
  • | [REQUEST PHASE (Target Machine - No DC Network Access Needed)] |
  • | - Run: djoin.exe /requestODJ /loadfile C:\ODJ\provision.txt |
  • | /windowspath %SystemRoot% /localos |
  • | - Injects machine account credentials into local LSA database. |
  • | - Target machine boots directly as a domain-joined system! |
  • +-----------------------------------------------------------------------------------+
  • Advanced ODJ Scenarios: DirectAccess & Unattended Installs

DirectAccess / Always On VPN ODJ: ODJ can inject DirectAccess connectivity policies into remote laptops before shipping to users:

djoin.exe /provision /domain contoso.com /machine RemoteLaptop01 /policynames DirectAccessClientPolicy /savefile C:\ODJ\blob.txt

Unattended Windows Setup ( unattend.xml ): The provisioning blob can be pasted directly into the Microsoft-Windows-UnattendedJoin component of unattend.xml under <Identification><Provisioning><AccountData>Base64Blob</AccountData></Provisioning></Identification> .

3. Joining Azure IaaS VMs to AD DS

When provisioning Windows Server virtual machines in Azure IaaS, domain join is automated using the Azure VM Domain Join Extension ( JsonADDomainExtension ). +-----------------------------------------------------------------------------------+

  • | AZURE IAAS VM DOMAIN JOIN ARCHITECTURE |
  • | |
  • | [AZURE VIRTUAL NETWORK (VNet)] |
  • | - VNet DNS Configuration: CUSTOM DNS pointing to DC IPs (e.g., 10.0.1.4, 10.0.1.5)|
  • | | |
  • | v |
  • | [AZURE IAAS VM: WebServer-VM] |
  • | - Extension: Microsoft.Compute/virtualMachines/extensions/JsonADDomainExtension |
  • | - Parameters: |
  • | * Name: contoso.com |
  • | * OUPath: OU=AzureVMs,DC=contoso,DC=com |
  • | * User: domainjoin@contoso.com |
  • | * Password: (Protected KeyVault Secret) |
  • | * Options: 3 (0x00000001 Join + 0x00000002 Perform Unsecure/Restart) |
  • +-----------------------------------------------------------------------------------+
  • ARM Template Snippet for JsonADDomainExtension {
  • "type": "Microsoft.Compute/virtualMachines/extensions",
  • "apiVersion": "2024-03-01",
  • "name": "[concat(parameters('vmName'), '/JsonADDomainExtension')]",
  • "location": "[parameters('location')]",
  • "properties": {
  • "publisher": "Microsoft.Compute",
  • "type": "JsonADDomainExtension",
  • "typeHandlerVersion": "1.3",
  • "autoUpgradeMinorVersion": true,
  • "settings": {
  • "Name": "contoso.com",
  • "OUPath": "OU=CloudServers,DC=contoso,DC=com",
  • "User": "contoso.com\\adminjoin",
  • "Restart": "true",
  • "Options": "3"
  • },
  • "protectedSettings": {
  • "Password": "[parameters('adminPassword')]"
  • }
  • }
  • }
  • 4. Joining Windows Server to Microsoft Entra Domain Services

Microsoft Entra Domain Services provides managed domain services (such as domain join, group policy, LDAP, and Kerberos/NTLM authentication) in Azure without requiring administrators to deploy or patch domain controllers.

Key Architectural Rules for Entra Domain Services Join:

Virtual Network Peering / DNS: The VM's virtual network must have its DNS servers configured with the two private IP addresses assigned to the Microsoft Entra Domain Services managed domain.

Administrative Role: To join a server, the administrator account must belong to the AAD DC Administrators group. Standard Global Administrators cannot join machines unless they are members of this specific group.

Target OU: Joined servers land in the built-in AADDC Computers container. Managed domains use a flat OU structure — custom OUs are created at the domain root , not nested beneath AADDC Computers , and custom GPOs are linked to those custom OUs.

5. Joining Windows Server to Microsoft Entra ID

Modern cloud-native and hybrid servers running Windows Server 2022 or Windows Server 2025 can be joined directly to Microsoft Entra ID :

Microsoft Entra ID Join via Azure VM Extension: In Azure, deploying the AADLoginForWindows VM extension enables Windows Server virtual machines to authenticate users using Microsoft Entra credentials.

Azure Arc Integration: On-premises Windows Servers onboarded to Azure Arc can leverage Microsoft Entra authentication and Azure Role-Based Access Control (RBAC) roles:

Virtual Machine Administrator Login: Grants local Administrator privileges on the server.

Virtual Machine User Login: Grants local standard User privileges.

6. Troubleshooting Domain Join Failures & Secure Channel Repair +-----------------------------------------------------------------------------------+

  • | DOMAIN JOIN & SECURE CHANNEL TROUBLESHOOTING |
  • | |
  • | 1. Netsetup.log Analysis |
  • | - Location: %windir%\debug\Netsetup.log |
  • | - Error 0x5: Access is denied (insufficient OU / join permissions) |
  • | - Error 0x54B: Domain controller not found (DNS resolution failure) |
  • | - Error 0x520: Machine account name collision in AD DS |
  • | |
  • | 2. Secure Channel Broken (Hypervisor Snapshot Rollback / Password Mismatch) |
  • | - Symptoms: 'The trust relationship between this workstation and the |
  • | primary domain failed.' |
  • | - Diagnosis: Test-ComputerSecureChannel (Returns False) |
  • | - Repair: Test-ComputerSecureChannel -Repair -Credential (Get-Credential) |
  • | - Manual Reset: Reset-ComputerMachinePassword -Credential (Get-Credential) |
  • +-----------------------------------------------------------------------------------+
  • Diagnosing and Repairing Secure Channels

When a virtual machine is rolled back to a hypervisor checkpoint/snapshot, its local machine account password reverts to an older version. Because domain controllers automatically rotate machine account passwords every 30 days, the password stored in Active Directory no longer matches the local LSA secret, breaking the secure channel. # Step 1: Verify the health of the secure channel

  • Test-ComputerSecureChannel -Verbose
  • # Returns: False
  • # Step 2: Repair the secure channel using domain administrative credentials
  • Test-ComputerSecureChannel -Repair -Credential (Get-Credential)
  • # Successfully resets machine password with the DC without rebooting
  • # Step 3: Alternative manual password reset cmdlet
  • Reset-ComputerMachinePassword -Credential (Get-Credential) -Server "DC01.contoso.com"

Loading diagram... Windows Server Domain Join Methods in Hybrid Environments