Study guide
8.6 Windows Container Networking & AKS Enabled by Azure Arc
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
8.6 Windows Container Networking & AKS Enabled by Azure Arc
Key Takeaways Explain This Topic AI
Windows container networking is implemented by the Host Network Service (HNS), which also provides IP address management for the nat and l2bridge drivers.
The default nat driver attaches containers to an internal Hyper-V switch and requires published ports, and NAT networks created on Windows Server 2019 and above are not persisted across a reboot.
The transparent driver gives containers a real physical-network address from DHCP or a static subnet, but requires MAC address spoofing when the host is a VM and is therefore not supported on Azure VMs.
l2bridge rewrites container traffic to the host MAC address on ingress and egress, while the otherwise identical l2tunnel driver is Azure-only and hair-pins traffic to the virtualization host so SDN policy such as Network Security Groups applies.
In a mixed AKS Hybrid cluster, Windows workloads must be pinned to nodes labelled kubernetes.io/os: windows with nodeSelector, plus tolerations when the Windows node pool is tainted, or they are scheduled onto Linux nodes and fail to start.
Last updated: August 2026
Windows Container Networking & AKS Enabled by Azure Arc
A container that cannot be reached is not much use. Section 8.5 covered running and constraining instances; this section covers connecting them — first on a single host through the Host Network Service (HNS) , then across many hosts through AKS enabled by Azure Arc .
1. Windows Container Networking Modes
Windows container networking is implemented by the Host Network Service (HNS) :
Network mode IP assignment Routing Primary use case
nat (default) Internal WinNAT private subnet Host port forwarding required ( -p 8080:80 ) Single-host development and standalone hosts
transparent Physical subnet IP from DHCP or static Directly addressable, no NAT Workloads that must hold a real corporate IP
overlay Overlay subnet via an SDN controller VXLAN encapsulation across hosts Multi-host Docker Swarm and Kubernetes
l2bridge Physical subnet IP via a host bridge Layer-2 packet rewrite on the same subnet Kubernetes clusters using Azure CNI or SDN # List the container networks HNS currently owns
Get-HnsNetwork | Select-Object Name, Type, @{n='Subnet';e={$_.Subnets.AddressPrefix}}
- # Create a transparent network bound to the physical corporate subnet
- docker network create -d transparent `
- o com.docker.network.windowsshim.interface="Ethernet0" `
- -subnet=192.168.10.0/24 --gateway=192.168.10.1 CorpTransparent
A container that must receive an address directly from the corporate DHCP server needs the transparent driver. NAT will not do it: NAT allocates from an internal WinNAT subnet and requires published ports.
Driver Mechanics the Exam Tests
nat attaches containers to an internal Hyper-V switch. HNS performs IPAM from the internal NAT prefix, and you customise the default subnet with the fixed-cidr setting in the Docker daemon configuration file. Only one NAT internal prefix exists, so cross-subnet container-to-container traffic is not supported. NAT networks created on Windows Server 2019 and above are not persisted across a reboot.
transparent attaches containers to an external Hyper-V switch, so they take a real address from the physical network either statically or from an external DHCP server. Two hard limits: when the container host is itself a VM, MAC address spoofing must be enabled , and for that reason transparent networking is not supported on Azure VMs . Transparent networks also have no service discovery .
overlay uses VXLAN encapsulation so containers on different hosts share a subnet, which is what Docker Swarm and Kubernetes need. On Windows Server 2019 and above, Swarm overlay networks use VFP NAT rules for outbound traffic, so ICMP tools such as ping and Test-NetConnection must be run with their TCP/UDP options when debugging.
l2bridge also uses an external switch, but rewrites the container MAC address to the host's MAC on ingress and egress. In a datacenter this spares physical switches from learning the MAC address of every short-lived container.
l2tunnel is created identically to l2bridge but should only be used in a Microsoft cloud stack (Azure) . All container traffic is hair-pinned to the virtualization host so SDN policy — including Azure Network Security Groups for containers — can be applied.
- 2. Troubleshooting Container Networking # Inspect what HNS believes exists
- Get-HnsNetwork | Select-Object Name, Type, Id
- Get-HnsEndpoint | Select-Object Id, VirtualNetworkName, IPAddress, MacAddress
- # Confirm the published port mapping actually landed on the host
- docker port web01
- Get-NetNatStaticMapping
- # Last resort: restarting HNS tears down and rebuilds container networking
- Restart-Service hns
A useful diagnostic order is to confirm the network exists in Get-HnsNetwork , confirm the container has an endpoint with a sane IP in Get-HnsEndpoint , and only then look at the port mapping. A container that has an endpoint and an IP but is unreachable from outside the host on a nat network almost always means the port was never published with -p .
3. Azure Kubernetes Service Enabled by Azure Arc (AKS Hybrid)
Once a workload outgrows one host, AKS enabled by Azure Arc brings a managed Kubernetes control-plane experience to on-premises Windows Server and Azure Local infrastructure, governed from the Azure portal alongside cloud clusters.
Scheduling in a mixed Windows and Linux cluster is the exam-relevant detail. Kubernetes nodes are automatically labelled with kubernetes.io/os , and a Windows workload must be pinned to Windows nodes or it will be scheduled onto a Linux node and fail to start: apiVersion: apps/v1
kind: Deployment
metadata:
name: iis-frontend
spec:
replicas: 3
selector:
matchLabels:
app: iis-frontend
template:
metadata:
labels:
app: iis-frontend
spec:
nodeSelector:
kubernetes.io/os: windows # pin to Windows Server worker nodes
containers:
- name: iis
- image: mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2022
resources:
limits:
- cpu: "1"
- memory: 2Gi
Where a cluster taints its Linux nodes, the Windows deployment also needs a matching tolerations block. The reverse is equally true: Linux workloads must be kept off Windows nodes, which is normally handled by tainting the Windows node pool.
Operating an Arc-Enabled Cluster
Because the cluster is projected into Azure Resource Manager as an Arc resource, it inherits the same governance surface as a cloud cluster:
- Capability What it gives you on-premises
- Azure Policy for Kubernetes Audits and enforces cluster configuration through Gatekeeper admission control
Azure Monitor container insights Node and pod telemetry from on-premises clusters in the same workspace as cloud clusters
- Microsoft Defender for Containers Threat detection for the on-premises cluster
- GitOps (Flux) Declarative, repository-driven configuration applied to the cluster
- Microsoft Entra RBAC Cluster access governed by directory identity rather than local kubeconfig files
Exam trap: mixing operating systems in one cluster is the recurring scenario. Windows nodes are labelled kubernetes.io/os: windows , and a Windows container scheduled onto a Linux node fails to start. Pin Windows workloads with nodeSelector , add tolerations when the Windows node pool is tainted, and remember that troubleshooting a container on those worker nodes uses crictl , not docker , because Kubernetes nodes run containerd.