Study guide

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure

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

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure

Key Takeaways Explain This Topic AI

Windows Admin Center (WAC) employs a lightweight, browser-based client-side architecture that translates user actions into PowerShell remoting and WMI calls over WinRM without deploying heavyweight agents or requiring internet access for core on-premises management.

Gateway Mode installs WAC on Windows Server listening on HTTPS port 443 with a production SSL/TLS certificate to serve as a centralized multi-user administrative portal, whereas Desktop Mode installs on Windows 10/11 listening on port 6516 for local single-user management.

High Availability for WAC gateways is implemented by deploying WAC onto a Windows Server Failover Cluster (active-passive configuration) with a shared cluster storage volume or file share witness and active Kerberos constrained delegation.

Onboarding WAC to Azure registers a Microsoft Entra ID enterprise application, enabling native hybrid integrations such as Azure Arc, Azure Backup, Azure File Sync, Azure Monitor, and Azure Network Adapter directly from the WAC interface.

Azure IaaS VMs can be managed natively from the Azure portal using the Windows Admin Center VM extension, which establishes secure outbound communication over port 443 through the Azure management fabric without requiring public inbound ports.

Last updated: August 2026

Windows Admin Center (WAC) Deployment On-Premises and in Azure

Modern hybrid infrastructure management requires unified, secure, and scalable tooling capable of administering physical servers, virtualization hypervisors, and cloud virtual machines. Windows Admin Center (WAC) is Microsoft's premier management platform for Windows Server. It consolidates fragmented Microsoft Management Consoles (MMCs), Server Manager, Task Manager, Device Manager, and PowerShell scripts into a single, responsive, browser-based management plane.

Unlike traditional enterprise management suites that require complex database backends and invasive software agents, Windows Admin Center leverages existing remote management protocols—primarily PowerShell Remoting and Windows Management Instrumentation (WMI) over WinRM —to deliver agentless, modular server administration.

1. Windows Admin Center Architecture & Evolution

Windows Admin Center separates the presentation layer from the execution layer through an extensible client-gateway architecture. +-----------------------------------------------------------------------------------------+

  • | WINDOWS ADMIN CENTER ARCHITECTURE & DATA FLOW |
  • | |
  • | [Web Browser Client] |
  • | - Chrome, Edge, Firefox |
  • | - HTML5 / Angular UI |
  • | | |
  • | | HTTPS (Port 443 or 6516) - REST API Calls / WebSocket |
  • | v |
  • | +-----------------------------------------------------------------------------------+ |
  • | | WAC GATEWAY SERVICE (Lightweight Node) | |
  • | | - Gateway Web Server (Kestrel / HTTP.sys) | |
  • | | - REST API Engine & Authentication Broker (Kerberos, Smart Card, Entra ID) | |
  • | | - Extension Manager (UI plugins & PowerShell execution pipelines) | |
  • | +-----------------------------------------------------------------------------------+ |
  • | | | |
  • | | WinRM (TCP 5985/5986) | HTTPS / REST API |
  • | | (PowerShell / WMI / CIM) | (Azure REST Endpoints) |
  • | v v |
  • | +-------------------------------------+ +-----------------------------------+ |
  • | | MANAGED TARGET NODES | | AZURE HYBRID SERVICES | |
  • | | - Windows Server 2016/2019/2022/2025| | - Azure Arc for Servers | |
  • | | - Azure Stack HCI Clusters | | - Azure Backup / Azure Monitor | |
  • | | - Azure IaaS Windows / Linux VMs | | - Microsoft Entra ID Authentication| |
  • | +-------------------------------------+ +-----------------------------------+ |
  • +-----------------------------------------------------------------------------------------+

Core Architectural Principles:

Client-Side Rendering: The user interface runs entirely inside the administrator's modern web browser (Edge, Chrome, Firefox). The browser downloads JavaScript, HTML5, and CSS assets from the WAC gateway and issues asynchronous REST API calls to the gateway backend.

Stateless Gateway Processing: The WAC gateway processes incoming REST requests and translates them dynamically into native PowerShell cmdlets or WMI/CIM queries directed at managed target nodes. The gateway does not maintain an operational SQL database; it functions as a lightweight protocol translator and authentication proxy.

Agentless Target Communication: Managed endpoints require no proprietary WAC agents. Communication relies strictly on standard WinRM (TCP 5985 for HTTP or TCP 5986 for HTTPS) and WMI over CIM. Target servers running Windows Server 2016, 2019, 2022, or 2025 have WinRM enabled by default.

PowerShell Visibility & Script Logging: WAC displays the exact underlying PowerShell scripts executed during GUI actions. Administrators can copy these generated cmdlets directly from the interface for inclusion in automated operational pipelines.

2. Deployment Models: Gateway Mode vs. Desktop Mode

Windows Admin Center can be deployed in two primary installation topologies depending on whether the requirement is local single-user management or enterprise multi-user shared infrastructure. +-----------------------------------------------------------------------------------------+

  • | GATEWAY MODE VS DESKTOP MODE ARCHITECTURAL COMPARISON |
  • | |
  • | [DESKTOP MODE] (Single-User) [GATEWAY MODE] (Multi-User Shared) |
  • | +--------------------------+ +----------------------------------+ |
  • | | Windows 10 / 11 Client | | Windows Server (Dedicated/Shared)| |
  • | | - Installs on OS Client | | - Installs on Windows Server | |
  • | | - Port: 6516 (Default) | | - Port: 443 (Default HTTPS) | |
  • | | - Self-signed local cert | | - Trusted CA SSL/TLS Certificate | |
  • | | - Single Administrator | | - Multi-User Concurrent Access | |
  • | | - Access: https://loca...| | - Access: https://wac.contoso.com| |
  • | +--------------------------+ +----------------------------------+ |
  • | | | |
  • | v (WinRM) v (WinRM) |
  • | [Target Servers] [Target Server Fleet] |
  • +-----------------------------------------------------------------------------------------+
  • Detailed Topology Comparison
  • Deployment Property Desktop Mode Gateway Mode (Server Installation)
  • Supported Operating System Windows 10, Windows 11 Windows Server 2016, 2019, 2022, 2025, Azure Stack HCI
  • Default Listening Port TCP 6516 (Configurable) TCP 443 (HTTPS default; configurable to custom ports)

Target Audience Single administrator managing local/remote PCs IT enterprise teams, Help Desk, Cloud Operations

Certificate Requirement Auto-generated self-signed certificate Production CA-signed SSL/TLS certificate (CN matching FQDN)

High Availability Not Supported Supported via Windows Server Failover Clustering

Credential Delegation Direct Kerberos from local desktop Kerberos Constrained Delegation (KCD) or explicit prompt

Azure Arc Integration Limited to local management Full enterprise onboarding and Azure Arc gateway bridge

Important

Exam Trap: Port Assignments: When installing Windows Admin Center on Windows 10 or 11 (Desktop Mode), the default listening port is 6516 . When installing on Windows Server (Gateway Mode), the installer defaults to 443 (or prompts for an alternative port if port 443 is already bound to another service such as IIS). Do not confuse these two default port assignments on the AZ-800 exam.

Gateway Mode Installation Script via PowerShell # Automated silent installation of WAC Gateway Mode on Windows Server

  • $MSIPath = "C:\Install\WindowsAdminCenter.msi"
  • $Thumbprint = "E5B4C2A1890123456789ABCDEF0123456789ABCD"
  • Start-Process msiexec.exe -ArgumentList @(
  • "/i", "`"$MSIPath`"",
  • "/qn",
  • "/L*v", "C:\Install\wac_install.log",
  • "SME_PORT=443",
  • "SSL_CERTIFICATE_OPTION=installed",
  • "SME_THUMBPRINT=$Thumbprint",
  • "GENERATE_SELFSIGNED_CERTIFICATE=0"
  • ) -Wait
  • 3. High Availability for WAC Gateways (Failover Clustering)

In mission-critical enterprise environments, a single WAC gateway represents a single point of failure (SPOF) for centralized management. Windows Admin Center supports high availability (HA) deployment using Windows Server Failover Clustering (WSFC) . +-----------------------------------------------------------------------------------------+

  • | WAC HIGH AVAILABILITY FAILOVER CLUSTER TOPOLOGY |
  • | |
  • | [Client Web Browsers] ---> Virtual Cluster DNS Name / IP: https://wac-cluster.corp.com |
  • | | |
  • | v |
  • | +-----------------------------------------------------------------------------------+ |
  • | | TWO-NODE WINDOWS SERVER FAILOVER CLUSTER | |
  • | | | |
  • | | +-------------------------------+ +-------------------------------+ | |
  • | | | NODE 1 (Active) | | NODE 2 (Passive Standby) | | |
  • | | | - WAC Gateway Service Running | <---> | - WAC Gateway Service Stopped | | |
  • | | | - Bound to Port 443 | | - Ready for Fast Failover | | |
  • | | +-------------------------------+ +-------------------------------+ | |
  • | | \ / | |
  • | | \ / | |
  • | | v v | |
  • | | [Cluster Shared Volume / SMB Witness / Shared Configuration Directory] | |
  • | +-----------------------------------------------------------------------------------+ |
  • | | |
  • | v WinRM (TCP 5985/5986) |
  • | [Managed Production Server Fleet] |
  • +-----------------------------------------------------------------------------------------+

HA Cluster Implementation Requirements:

Active-Passive Gateway Model: WAC HA clustering operates in an active-passive configuration. The active cluster node hosts the WAC service and processes inbound HTTPS connections. If the active node fails, the cluster resource group automatically transfers the service, IP address, and network name to the passive standby node.

Shared State & Extension Repository: Cluster nodes share configuration metadata, connection lists, and installed extensions using a shared storage location (Cluster Shared Volume [CSV] or an enterprise SMB 3.0 file share).

Cluster Installation Command: The WAC MSI installer is executed on each cluster node using the cluster-aware parameter set: # Installing WAC on an existing Failover Cluster Node

  • msiexec /i WindowsAdminCenter.msi /qn /L*v C:\wac_cluster.log `
  • SME_PORT=443 `
  • SSL_CERTIFICATE_OPTION=installed `
  • SME_THUMBPRINT='E5B4C2A1890123456789ABCDEF0123456789ABCD' `
  • CLUSTER_NAME='wac-cluster.corp.contoso.com'

Kerberos Constrained Delegation (KCD): The Active Directory computer accounts of both cluster nodes (and the virtual cluster name) must be configured with Kerberos Constrained Delegation to the WSMAN and HOST Service Principal Names (SPNs) of all managed target servers to allow seamless credential delegation across failovers.

4. WAC Extension Ecosystem & Azure Hybrid Onboarding

Windows Admin Center is built on a modular, pluggable extension model. Extensions deliver domain-specific administrative tools and provide direct hooks into Microsoft Azure hybrid management services. +-----------------------------------------------------------------------------------------+

  • | WAC EXTENSION & HYBRID CLOUD INTEGRATION |
  • | |
  • | +-----------------------------------------------------------------------------------+ |
  • | | WINDOWS ADMIN CENTER EXTENSION ECOSYSTEM | |
  • | | +-------------------+ +-------------------+ +--------------------------------+ | |
  • | | | CORE OS TOOLS | | CLUSTER & FABRIC | | AZURE HYBRID SERVICES | | |
  • | | | - Certificates | | - Hyper-V Manager | | - Azure Arc for Servers | | |
  • | | | - Registry | | - Storage Spaces | | - Azure Backup | | |
  • | | | - File Shares | | Direct (S2D) | | - Azure File Sync | | |
  • | | | - Firewall / Event| | - SDN Infrastructure| - Azure Monitor Metrics | | |
  • | | | Viewer / Updates| | - Storage Migration| - Azure Network Adapter (P2S VPN)| | |
  • | +-----------------------------------------------------------------------------------+ |
  • | | |
  • | (Azure Registration Wizard) |
  • | v |
  • | +-----------------------------------------------------------------------------------+ |
  • | | MICROSOFT ENTRA ID & AZURE SUBSCRIPTION | |
  • | | - Entra ID Enterprise App: 'WindowsAdminCenter-https://wac.contoso.com' | |
  • | | - Delegated Permissions: Azure Resource Manager API / Graph API | |
  • | | - Target Azure Subscription & Resource Group Binding | |
  • | +-----------------------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------------------+

Key Core and Fabric Extensions:

Hyper-V Extension: Enables VM lifecycle operations (create, modify, start, stop, checkpoint, live migrate), virtual switch configuration, and nested virtualization.

Storage Spaces Direct (S2D): Visualizes cluster pools, drives, virtual disks, resilient volumes, IOPS/latency performance telemetry, and health alerts.

Software-Defined Networking (SDN): Manages Virtual Networks, Network Security Groups (NSGs), Software Load Balancers (SLBs), and gateway connections.

Storage Migration Service (SMS): Orchestrates multi-server file server inventory, transfer, and cutover from legacy Windows Server 2003/2008/2012 to modern Windows Server or Azure VMs.

Step-by-Step Azure Registration Workflow:

To enable hybrid capabilities, the WAC gateway must be registered with Microsoft Entra ID:

Navigate to Settings > Azure in the WAC interface.

Click Register with Azure and select the Azure Cloud environment (Azure Global, Azure US Government, or Azure China).

Enter the Microsoft Entra Directory (Tenant) ID .

Sign in with a Global Administrator or Privileged Role Administrator account to grant admin consent. WAC automatically provisions an App Registration (Enterprise Application) in Entra ID named WindowsAdminCenter-https://<WAC-FQDN> .

Once registered, administrators can link on-premises servers to Azure Arc , configure Azure Backup vaults, deploy Azure File Sync agent endpoints, and establish one-click point-to-site VPNs using Azure Network Adapter directly from server management panes.

5. Managing Azure IaaS Virtual Machines via Azure Portal WAC Extension

Microsoft extends Windows Admin Center directly into the Azure control plane. Administrators can manage Windows Server Azure IaaS Virtual Machines directly within the Azure Portal without establishing VPN tunnels, ExpressRoute circuits, or exposing public inbound RDP/WinRM ports.

Windows Admin Center Connectivity Models for Azure IaaS VMs

Management Method Network Path Inbound Public Ports Required Security & Protocol Characteristics

Azure Portal WAC Extension Azure Management Fabric to VM Extension Agent None (0 Inbound Ports) Outbound HTTPS (Port 443) from VM to Azure control plane; authenticated via Microsoft Entra RBAC.

On-Premises WAC Gateway (Direct) Hybrid Site-to-Site VPN / ExpressRoute None (Private IP over VPN) Internal WinRM (TCP 5985/5986) over private hybrid network links; Kerberos authentication.

On-Premises WAC Gateway (Public IP) Direct Internet via Public IP / NSG TCP 5985 / 5986 Inbound Highly Discouraged. Exposes WinRM to internet; requires TLS certs and strict NSG source IP filtering.

Azure Bastion + WAC Desktop Azure Bastion PaaS to Internal Jumpbox None (Port 443 to Bastion) Browser-based RDP session to jumpbox hosting WAC Desktop Mode; jumpbox reaches VMs over VNet.

Mechanics of the Azure Portal WAC VM Extension:

VM Extension Deployment: In the Azure Portal, selecting Windows Admin Center under the VM's Settings menu installs the AdminCenter VM extension ( Microsoft.Azure.Security.AdminCenter agent).

Outbound Reverse Tunneling: The extension initiates an outbound, encrypted reverse WebSocket tunnel over HTTPS (Port 443) to the Azure management endpoint. Target VMs require no public IP addresses and no inbound NSG rules allowing ports 5985, 5986, or 3389.

Identity & Access Enforcement: Portal users must possess the Windows Admin Center Administrator Login Azure RBAC role on the target virtual machine resource (or parent resource group) to successfully authenticate into the embedded WAC session.

6. Access Control, Security Hardening & Role-Based Access Control (RBAC)

Securing the Windows Admin Center gateway and delegated server management involves multiple authorization layers. +-----------------------------------------------------------------------------------------+

  • | WAC MULTI-LAYER ACCESS CONTROL MODEL |
  • | |
  • | [Layer 1: Gateway Authentication] |
  • | - Local Users vs Local Administrators on Gateway OS |
  • | - Microsoft Entra ID Authentication (Enables Conditional Access & MFA) |
  • | - Smart Card / PKI Client Certificate Mapping |
  • | | |
  • | v |
  • | [Layer 2: Target Node Authorization (JEA / PowerShell RBAC)] |
  • | - Full Administrator vs Readers vs Network/Hyper-V Admins |
  • | - Gateway configures Just Enough Administration (JEA) endpoints automatically |
  • | | |
  • | v |
  • | [Layer 3: Credential Delegation] |
  • | - Kerberos Constrained Delegation (KCD) across gateway boundaries |
  • | - Avoids CredSSP security vulnerabilities for multi-hop management |
  • +-----------------------------------------------------------------------------------------+

Gateway Access Roles:

Gateway Users: Can connect to the WAC gateway service and manage target servers for which they have valid administrative credentials, but cannot modify gateway settings, install extensions, or alter gateway security.

Gateway Administrators: Possess full administrative authority over the WAC gateway instance, including extension installation/upgrades, certificate management, Azure hybrid registration, and user access configuration.

Tip

Entra ID Conditional Access Integration: When the WAC gateway is onboarded to Microsoft Entra ID, administrators can enforce Microsoft Entra Conditional Access policies on the WAC Enterprise Application. This enables mandatory Phishing-Resistant Multi-Factor Authentication (FIDO2 / Windows Hello for Business), device compliance checks (Intune-managed devices), and named IP location restrictions for all incoming IT administrative sessions.

Loading diagram... Windows Admin Center Enterprise Hybrid Management Architecture