Study guide
6.1 Azure Arc-Enabled Servers Architecture & Onboarding
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
6.1 Azure Arc-Enabled Servers Architecture & Onboarding
Key Takeaways Explain This Topic AI
Azure Arc-enabled servers project physical and virtual non-Azure Windows and Linux servers into Azure Resource Manager (ARM) as Microsoft.HybridCompute/machines, granting them first-class Azure identities and governance capabilities.
The Azure Connected Machine Agent operates through three core operating system services: Hybrid Instance Metadata Service (himds) for identity and heartbeats, Guest Configuration Service (gc_service) for policy evaluation, and Extension Manager (extmd) for VM extension lifecycle management.
Network communication requires only outbound HTTPS connectivity over TCP port 443 to Azure management endpoints; no inbound firewall ports, public IP addresses, or incoming network tunnels are necessary.
Enterprise-scale onboarding utilizes an Entra ID Service Principal assigned the least-privilege 'Azure Connected Machine Onboarding' RBAC role, distributed via Active Directory Group Policy startup scripts or Microsoft Configuration Manager.
Local agent configuration, connectivity diagnostics, logs collection, and lifecycle operations are managed using the azcmagent command-line interface (show, check, config, disconnect, and logs).
Last updated: August 2026
Azure Arc-Enabled Servers Architecture & Onboarding
Modern enterprise IT environments rarely reside entirely within a single cloud boundary. Organizations routinely operate heterogeneous fleets of Windows Server and Linux virtual machines running across on-premises hypervisors (VMware vSphere, Microsoft Hyper-V), physical bare-metal hardware, and third-party cloud platforms (AWS, Google Cloud). Azure Arc-enabled servers bridges this architectural divide by projecting non-Azure physical and virtual servers directly into Azure Resource Manager (ARM) as first-class resources under the Microsoft.HybridCompute/machines resource provider namespace.
Once projected into ARM, non-Azure servers gain native Azure capabilities: they can be organized into Subscriptions, Resource Groups, and Management Groups; tagged with corporate metadata; secured with Azure Role-Based Access Control (Azure RBAC); governed through Azure Policy and Azure Machine Configuration; monitored using Azure Monitor; and patched via Azure Update Manager—all without migrating the underlying operating system or storage volumes into the cloud.
1. Azure Arc-Enabled Servers Core Architecture
When a server is onboarded to Azure Arc, the installation of the Azure Connected Machine Agent creates a digital representation of the host within Azure Resource Manager. The physical or virtual machine remains in its existing physical datacenter or host environment while establishing an outbound, cryptographically authenticated control-plane connection to Azure. +-----------------------------------------------------------------------------------------+
- | AZURE ARC-ENABLED SERVERS CONTROL PLANE ARCHITECTURE |
- | |
- | [ON-PREMISES / MULTICLOUD INFRASTRUCTURE] [AZURE RESOURCE MANAGER] |
- | +---------------------------------------+ +----------------------------+ |
- | | Windows Server 2012 R2 - 2025 Host | | Azure Subscription | |
- | | | | - Resource Group | |
- | | +-----------------------------------+ | | - Resource Tags | |
- | | | Azure Connected Machine Agent | | | - Azure RBAC Access | |
- | | | | | +----------------------------+ |
- | | | [himds] Identity & Heartbeats | | ^ |
- | | | [gc_svc] Machine Configuration | | | |
- | | | [extmd] Extension Manager | |=== Outbound HTTPS 443 ====>| |
- | | +-----------------------------------+ | (No Inbound Ports) v |
- | | | +----------------------------+ |
- | | [Guest OS / Workloads / Services] | | Microsoft.HybridCompute | |
- | | - Active Directory / Hyper-V / IIS | | /machines Projection | |
- | +---------------------------------------+ +----------------------------+ |
- +-----------------------------------------------------------------------------------------+
- The Projection Model vs Virtualization Migration
It is critical to distinguish Azure Arc from cloud migration solutions such as Azure Migrate. Azure Arc does not relocate the virtual disk images (VHD/VHDX/VMDK) or modify the hypervisor execution engine. The server continues executing locally. Azure Arc projects only the management metadata and control plane into Azure, allowing centralized governance across hybrid topologies.
2. Connected Machine Agent Architecture & OS Services
The Azure Connected Machine Agent is composed of three primary background operating system services working in concert: +-----------------------------------------------------------------------------------------+
- | AZURE CONNECTED MACHINE AGENT DAEMON STACK |
- | |
- | +-----------------------------------------------------------------------------------+ |
- | | Hybrid Instance Metadata Service (himds / himds.exe) | |
- | | - Manages local IMDS REST endpoint: http://localhost:40342/metadata/... | |
- | | - Generates & rotates Azure Entra ID System-Assigned Managed Identity | |
- | | - Transmits 5-minute health heartbeats to Azure Hybrid Instance Service | |
- | | - Collects host hardware, OS build, FQDN, and network adapter metadata | |
- | +-----------------------------------------------------------------------------------+ |
- | | |
- | +-----------------------------------------------------------------------------------+ |
- | | Guest Configuration Service (gc_service / gc_agent) | |
- | | - Executes in-guest compliance audits and Desired State Configuration (DSC v3) | |
- | | - Evaluates OS-level security baselines assigned by Azure Policy | |
- | | - Reports in-guest compliance JSON telemetry back to ARM | |
- | +-----------------------------------------------------------------------------------+ |
- | | |
- | +-----------------------------------------------------------------------------------+ |
- | | Extension Manager Service (extmd / ext_mgr) | |
- | | - Coordinates lifecycle of Azure VM Extensions (AMA, MDE, Custom Script, KeyVault) | |
- | | - Downloads, installs, configures, health-monitors, and uninstalls extensions | |
- | +-----------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
Detailed Service Functions:
Hybrid Instance Metadata Service ( himds / himds.exe ):
Serves as the identity and heartbeat engine. It exposes a local Instance Metadata Service (IMDS) endpoint accessible only via loopback at http://localhost:40342/metadata/identity/oauth2/token .
Maintains the machine's Microsoft Entra ID System-Assigned Managed Identity . Local applications and extensions can acquire OAuth 2.0 tokens from this local endpoint to authenticate directly to Azure services (e.g., Azure Key Vault, Azure Storage) without embedding credentials in configuration files.
Transmits a health heartbeat to Azure every 5 minutes . If Azure fails to receive a heartbeat for more than 15 minutes, the machine's status in the Azure portal transitions from Connected to Disconnected .
Guest Configuration Service ( gc_service / gc_agent ):
Runs an embedded, sandboxed PowerShell Desired State Configuration (DSC v3) execution engine.
Downloads and executes Machine Configuration policy packages assigned to the machine to audit or enforce OS-level security baselines, registry settings, and user rights assignments.
Extension Manager Service ( extmd / ext_mgr ):
Implements the VM Extension framework on non-Azure servers. It handles requests from ARM to install, configure, upgrade, and delete extension binaries such as the Azure Monitor Agent (AMA), Microsoft Defender for Endpoint (MDE), Azure Key Vault extension, and Custom Script Extension.
3. Onboarding Prerequisites & Network Architecture
To onboard a server to Azure Arc, the host operating system and network routing path must satisfy strict architectural requirements.
Supported Operating Systems
Windows Server: Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025 (Standard, Datacenter, and Server Core editions).
Linux: Red Hat Enterprise Linux (RHEL) 7/8/9, CentOS 7, Oracle Linux 7/8/9, SUSE Linux Enterprise Server (SLES) 12/15, Ubuntu 18.04/20.04/22.04/24.04 LTS, Debian 10/11/12, Rocky Linux, and AlmaLinux.
Local Privileges: Requires administrative elevation ( BUILTIN\Administrators on Windows; root on Linux).
Network Connectivity & Security Baseline
The Azure Connected Machine Agent communicates exclusively outbound over standard HTTPS ( TCP Port 443 ). It does not require any inbound ports to be opened on perimeter firewalls or local host firewalls, nor does it require a public IP address. +-----------------------------------------------------------------------------------------+
- | AZURE ARC MANDATORY OUTBOUND HTTPS ENDPOINTS |
- | |
- | ENDPOINT URL PATTERN PURPOSE |
- | ------------------------------------+-------------------------------------------------|
- | management.azure.com | Azure Resource Manager control plane operations |
- | login.microsoftonline.com | Entra ID authentication and token issuance |
- | pas.windows.net | Hybrid Instance Service token authority |
- | *.his.arc.azure.com | Hybrid Instance Metadata Service heartbeats |
- | guestconfiguration.azure.com | Azure Machine Configuration package downloads |
- | *.servicebus.windows.net | Notification channel and Run Command messaging |
- | *.blob.core.windows.net | VM extension binaries and package storage |
- +-----------------------------------------------------------------------------------------+
- Proxy and SSL Inspection Rules
If the on-premises environment routes outbound traffic through an enterprise HTTP/HTTPS proxy server, the agent must be configured with proxy connection parameters. The agent supports both unauthenticated proxies and proxies using integrated Windows authentication. # Configure proxy settings directly via the azcmagent CLI
azcmagent config set proxy.url "http://proxy.contoso.com:8080"
- # Configure proxy bypass for internal local endpoints
- azcmagent config set proxy.nonproxy "localhost,127.0.0.1,*.internal.contoso.com"
# Alternative: Configure system-wide environment variable
[System.Environment]::SetEnvironmentVariable('https_proxy', 'http://proxy.contoso.com:8080', [System.EnvironmentVariableTarget]::Machine)
Caution
SSL/TLS Inspection & Certificate Termination: Azure Arc agent communication utilizes mutual Transport Layer Security (mTLS) with pinned Microsoft certificates. If an enterprise perimeter proxy performs SSL Decryption / TLS Inspection (Man-in-the-Middle) , the agent will reject the intercepted proxy certificate, terminating connection attempts. Administrators must create an SSL inspection bypass rule for all Azure Arc domain endpoints.
Azure Arc Private Link Scope (AMPLS)
For high-security environments where servers must not route traffic across the public Internet, organizations can deploy an Azure Arc Private Link Scope (AMPLS) . This architecture routes all agent heartbeats, extension downloads, and metadata over an Azure ExpressRoute or Site-to-Site VPN directly into private endpoints hosted within an Azure Virtual Network (VNet).
4. Enterprise Onboarding Methods: Interactive vs Service Principal at Scale
Microsoft provides multiple onboarding workflows designed for different deployment scales. +-----------------------------------------------------------------------------------------+
- | ONBOARDING METHODOLOGY SELECTION |
- | |
- | CRITERIA INTERACTIVE SCRIPT SERVICE PRINCIPAL AT SCALE |
- | --------------------+-----------------------------+-----------------------------------|
- | Target Scale | 1 to 5 machines (PoC / Dev) | Hundreds to Thousands of servers |
- | Authentication | Interactive browser / code | Entra ID App (Secret or Cert) |
- | User Interaction | Required (MFA / Browser) | Zero interaction (Fully automated)|
- | Deployment Vehicle | Manual PowerShell execution | Group Policy, MECM, Ansible, WAC |
- | Required RBAC Role | Azure Connected Machine | Azure Connected Machine |
- | | Onboarding (or Contributor) | Onboarding |
- +-----------------------------------------------------------------------------------------+
- Method 1: Interactive Onboarding (Single-Server Evaluation)
In the Azure Portal, navigating to Azure Arc > Servers > Add allows generating a PowerShell script for a single server. Executing the script downloads AzureConnectedMachineAgent.msi , installs the binaries, and initiates an interactive authentication challenge prompting the administrator to authenticate via https://microsoft.com/devicelogin using their Entra ID administrative credentials.
Method 2: Automated Onboarding at Scale via Entra ID Service Principal
For production deployments across hundreds of physical or virtual servers, administrators generate an onboarding script backed by a Microsoft Entra ID Service Principal .
Step 1: Assign the Least-Privilege RBAC Role
The Service Principal requires only the Azure Connected Machine Onboarding built-in role scoped to the target Resource Group or Subscription.
Important
Least-Privilege Principle ( Azure Connected Machine Onboarding ): The Azure Connected Machine Onboarding role permits the Service Principal to register and onboard Microsoft.HybridCompute/machines resources into Azure. It does not permit reading data, deleting servers, modifying Azure policies, or assigning roles, preventing privilege escalation if the onboarding secret is intercepted.
Step 2: Execute Unattended Onboarding Script # Download and install the Azure Connected Machine Agent MSI silently
- $AgentDownloadUrl = "https://aka.ms/AzureConnectedMachineAgent"
- $InstallerPath = "$env:TEMP\AzureConnectedMachineAgent.msi"
- Invoke-WebRequest -Uri $AgentDownloadUrl -OutFile $InstallerPath -UseBasicParsing
Start-Process -FilePath "msiexec.exe" -ArgumentList "/i `"$InstallerPath`" /qn /l*v `"$env:TEMP\ArcAgentInstall.log`"" -Wait
- # Connect the agent to Azure using the Service Principal
- $TenantId = "72f988bf-86f1-41af-91ab-2d7cd011db47"
- $SubscriptionId = "a1b2c3d4-e5f6-7a8b-9c0d-1e2f3a4b5c6d"
- $ResourceGroup = "rg-hybrid-infrastructure"
- $Location = "eastus"
- $AppId = "d9e8f7a6-b5c4-3d2e-1f0a-9b8c7d6e5f4a"
- $AppSecret = "Secr3t~Value~P@ssw0rd2026!"
- & "$env:ProgramFiles\AzureConnectedMachineAgent\azcmagent.exe" connect `
- -service-principal-id $AppId `
- -service-principal-secret $AppSecret `
- -tenant-id $TenantId `
- -subscription-id $SubscriptionId `
- -resource-group $ResourceGroup `
- -location $Location `
- -tags "Datacenter=Chicago,Environment=Production,Workload=ActiveDirectory" `
- -correlation-id (New-Guid).ToString()
- Method 3: Active Directory Group Policy (GPO) Distribution
To onboard entire Active Directory Organizational Units (OUs) without touching individual machines:
Create a network share containing AzureConnectedMachineAgent.msi and a locked-down PowerShell script containing the azcmagent connect command.
Create an Active Directory Group Policy Object (GPO) linked to the target OU.
Configure a Startup Script under Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown) > Startup or deploy a Scheduled Task running under the NT AUTHORITY\SYSTEM context.
When domain-joined servers reboot, the agent installs silently, authenticates via the Service Principal, applies tags, and registers the server in ARM.
5. Agent Administration & CLI Reference ( azcmagent )
The azcmagent command-line utility provides complete lifecycle and diagnostic capabilities for the Connected Machine Agent.
Core azcmagent CLI Commands
Command Primary Function Exam & Operational Use Case
azcmagent show Displays agent status, connection state, Azure resource ID, tenant ID, and proxy settings Verifying successful onboarding and checking whether the host is Connected or Disconnected
azcmagent check Validates end-to-end network reachability to all mandatory Azure endpoints and tests proxy authentication Troubleshooting firewall blocks, DNS resolution failures, and proxy routing rules
azcmagent config get/set Queries or modifies local agent configuration properties (e.g. proxy.url , proxy.nonproxy ) Configuring proxy URLs or adjusting local agent parameters post-installation
azcmagent disconnect Removes the server registration from Azure Arc and revokes the local managed identity certificate Gracefully unlinking a decommissioned server before removing local agent binaries
azcmagent logs Collects all local diagnostic logs into a consolidated .zip archive Capturing error logs ( himds.log , gc_agent.log ) for Microsoft Support escalations
Diagnostic Workflow: Troubleshooting a Disconnected Agent # Step 1: Inspect local agent state and connection status
azcmagent show
# Sample Output:
- # Resource Name : SRV-APP-01
- # Resource Group : rg-hybrid-infrastructure
- # Subscription ID : a1b2c3d4-e5f6-7a8b-9c0d-1e2f3a4b5c6d
- # Tenant ID : 72f988bf-86f1-41af-91ab-2d7cd011db47
- # VM ID : 12345678-abcd-1234-abcd-1234567890ab
- # Agent Status : Disconnected
- # Agent Version : 1.42.02891.1345
- # HTTPS Proxy : http://proxy.contoso.com:8080
- # Step 2: Execute network connectivity and endpoint validation check
- azcmagent check
- # Step 3: If connectivity succeeds but agent remains disconnected, gather logs
- azcmagent logs
- # Generated: C:\ProgramData\AzureConnectedMachineAgent\Log\azcmagent_logs_20260822_143000.zip
Tip
Exam Trap: Disconnecting vs Deleting in Azure: Running azcmagent disconnect from the local guest server removes the local connection certificate and sets the status to disconnected. However, it does not delete the Microsoft.HybridCompute/machines resource representation in Azure ARM. To cleanly purge the server, an administrator must both execute azcmagent disconnect locally and delete the resource object in the Azure Portal, Azure CLI ( az resource delete ), or Azure PowerShell ( Remove-AzConnectedMachine ).