Study guide

8.4 Windows Server Container Hosts, Isolation Models & Images

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.4 Windows Server Container Hosts, Isolation Models & Images

Key Takeaways Explain This Topic AI

Process isolation shares the host kernel for maximum density but requires the container base image build to match the host OS build exactly.

Hyper-V isolation gives each container its own lightweight utility VM kernel, which is what allows a mismatched image build to run and provides a hostile multi-tenancy boundary.

A Windows Server container host needs the Containers feature plus a runtime; Hyper-V is additionally required when Hyper-V-isolated containers are used.

The modern Windows container stack is built on containerd as the CRI runtime alongside the Host Compute Service and the Host Network Service.

In a Windows Dockerfile the '# escape=`' directive switches the escape character to a backtick so that backslashes in Windows paths are not misread.

Last updated: August 2026

Windows Server Container Hosts, Isolation Models & Images

Containerization packages applications and their runtime dependencies into lightweight, portable, and immutable execution units. In Windows Server environments, containerization enables legacy .NET Framework applications, modern .NET cloud-native microservices, and enterprise web workloads to achieve high density, automated CI/CD lifecycle pipelines, and instant scaling.

This section covers preparing Windows Server as a container host and the isolation models and base images that decision depends on. Running and lifecycle-managing container instances and Linux containers via WSL are covered in section 8.5; container networking and Azure Kubernetes Service (AKS) enabled by Azure Arc are covered in section 8.6; building, tagging, and distributing images through a registry is covered in section 8.7.

1. Windows Server Container Isolation Models

Windows Server provides two distinct container isolation technologies to balance density against multi-tenant security boundaries: +-----------------------------------------------------------------------------------------+

  • | WINDOWS SERVER CONTAINER ISOLATION MODELS |
  • | |
  • | [PROCESS ISOLATION] [HYPER-V ISOLATION] |
  • | +-------------------+ +-------------------+ +-------------------+ +-------------------+|
  • | | Container App A | | Container App B | | Container App A | | Container App B ||
  • | | User Mode (DLLs) | | User Mode (DLLs) | | User Mode (DLLs) | | User Mode (DLLs) ||
  • | +-------------------+ +-------------------+ +-------------------+ +-------------------+|
  • | | Shared Host Kernel Engine & Subsystems | | Guest Kernel (VM) | | Guest Kernel (VM) ||
  • | | (Namespaces, Job Objects, File System) | +-------------------+ +-------------------+|
  • | +------------------------------------------+ | Lightweight Hyper-V Utility Partition ||
  • | | Windows Server Physical / Virtual Host | +------------------------------------------+|
  • | | Operating System Kernel | | Windows Server Host Kernel / Hyper-V ||
  • | +------------------------------------------+ +------------------------------------------+|
  • +-----------------------------------------------------------------------------------------+

Detailed Comparison: +-----------------------------------------------------------------------------------------+

  • | PROCESS ISOLATION VS HYPER-V ISOLATION |
  • | |
  • | DIMENSION PROCESS ISOLATION HYPER-V ISOLATION |
  • | --------------------+------------------------------+----------------------------------|
  • | Kernel Architecture | Shared Host Kernel | Dedicated Lightweight Hypervisor |
  • | | (Namespace & Job Objects) | Utility VM Kernel per container |
  • | OS Version Match | STRICT requirement: Host OS | FLEXIBLE: Allows running mismatched|
  • | | build must match image build | container OS builds on host kernel|
  • | Security Boundary | Trust boundary: Suitable for | Hostile multi-tenancy boundary: |
  • | | single-tenant enterprise apps| Strong hardware-level isolation |
  • | Startup Time & Perf | Milliseconds; highest density| Seconds; slight memory overhead |
  • | | and raw execution speed | per utility VM partition |
  • | Docker CLI Flag | --isolation=process | --isolation=hyperv |
  • +-----------------------------------------------------------------------------------------+

Important

Host OS Build Matching in Process Isolation: Under Process Isolation, the host operating system kernel and the container base image build must match exactly (e.g., a Windows Server 2022 build 20348 container image running on a Windows Server 2022 build 20348 host). Running a Windows Server 2019 container image on a Windows Server 2022 host requires Hyper-V Isolation .

Loading diagram... Process Isolation vs Hyper-V Isolation Architecture

2. Windows Base Container Images & Dockerfile Authoring

Microsoft maintains official Windows base container images in the Microsoft Container Registry ( mcr.microsoft.com ): +-----------------------------------------------------------------------------------------+

  • | WINDOWS BASE CONTAINER IMAGES HIERARCHY |
  • | |
  • | IMAGE REPOSITORY APPROX. SIZE TARGET WORKLOADS & RUNTIMES |
  • | ----------------------------+--------------+------------------------------------------|
  • | mcr.microsoft.com/windows/ | ~100 - 300 MB| Cloud-native .NET 6/8/9, Node.js, Go, |
  • | nanoserver | (Compressed) | Python. 64-bit only; no GUI, no WOW64. |
  • | ----------------------------+--------------+------------------------------------------|
  • | mcr.microsoft.com/windows/ | ~1.5 - 2 GB | Full .NET Framework (3.5/4.8), IIS, WCF, |
  • | servercore | (Compressed) | PowerShell 5.1, COM+, Windows Services. |
  • | ----------------------------+--------------+------------------------------------------|
  • | mcr.microsoft.com/windows/ | ~3.1 GB | Full Windows Server API set, GPU accel., |
  • | server | | no IIS conn. limits. Needs a WS2025 host.|
  • | ----------------------------+--------------+------------------------------------------|
  • | mcr.microsoft.com/windows | ~3.4 GB | Full Windows client API surface; DirectX |
  • | | | and graphics libs. Not on WS2025. |
  • +-----------------------------------------------------------------------------------------+

Note

Microsoft sizes the windows/server image at roughly 3.1 GB and the windows image at roughly 3.4 GB — the Windows Server image is the smaller of the two, inherits Server Core's reliability improvements, adds GPU acceleration support and removes IIS connection limits. The windows image isn't available for Windows Server 2025. Image tagging, registry distribution and cleanup are covered in section 8.6.

  • Preparing Windows Server as a Container Host # Install the Containers and Hyper-V Windows features
  • Install-WindowsFeature -Name Containers, Hyper-V -IncludeManagementTools
  • # Install containerd runtime via Microsoft PowerShell script
  • Invoke-WebRequest -UseBasicParsing "https://aka.ms/install-containerd.ps1" -OutFile "install-containerd.ps1"
  • .\install-containerd.ps1
  • # Verify containerd service status
  • Get-Service containerd
  • Multi-Stage Dockerfile Authoring for Windows # escape=`
  • # Multi-stage build: Compile on Server Core SDK, deploy on minimal Nano Server
  • FROM mcr.microsoft.com/dotnet/sdk:8.0-windowsservercore-ltsc2022 AS build-env
  • WORKDIR /app
  • # Copy project files and restore dependencies
  • COPY *.csproj ./
  • RUN dotnet restore
  • # Copy source files and build release binaries
  • COPY . ./
  • RUN dotnet publish -c Release -o /app/out
  • # Runtime stage: Lightweight Nano Server
  • FROM mcr.microsoft.com/windows/nanoserver:ltsc2022
  • WORKDIR /app
  • COPY --from=build-env /app/out ./
  • # Expose web service port and configure entrypoint
  • EXPOSE 8080
  • ENV ASPNETCORE_URLS=http://+:8080
  • ENTRYPOINT ["dotnet", "WebApiApp.dll"]

Tip

Dockerfile Escape Directive ( # escape=` ): In Windows Dockerfiles, the standard backslash \ character is used as the file system directory separator. Adding # escape=` at the very first line configures the backtick ` as the escape character, preventing conflicts with Windows file paths.