Study guide
8.7 Managing Container Images, Tags & Azure Container Registry
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.7 Managing Container Images, Tags & Azure Container Registry
Key Takeaways Explain This Topic AI
Container images are immutable and layered; a tag is mutable and can be repointed, while a digest (sha256) is a fixed content hash and is the only reproducible reference.
Windows base images are pulled from the Microsoft Container Registry at mcr.microsoft.com, which has no catalog of its own and relies on Docker Hub for image discovery.
The windows/server base image is roughly 3.1 GB and smaller than the 3.4 GB windows image, adds GPU acceleration support and no IIS connection limits, and requires Windows Server 2025; the windows image is not available for Windows Server 2025.
Pushing to Azure Container Registry requires tagging with the fully qualified, all-lowercase login server such as myregistry.azurecr.io; an untagged push silently targets Docker Hub instead.
docker rmi and docker image prune only reclaim space on the local host; registry contents must be deleted with az acr repository delete or the Az.ContainerRegistry cmdlets.
Last updated: August 2026
Managing and Distributing Windows Server Container Images
Building an image is only half of the container objective. The AZ-800 blueprint lists "Create Windows Server container images" and "Manage Windows Server container images" as two separate skills, and the second one is where most candidates lose marks. Managing images means knowing where they come from, how they are named and versioned, how you move them between a build host and a private registry, and how you reclaim disk space when a Server Core layer quietly consumes 2 GB on every node. This section covers the image lifecycle after the docker build in section 8.4.
1. Image Anatomy: Layers, Tags and Digests
A container image is an immutable, layered artifact. Each instruction in a Dockerfile adds a read-only layer; a running container adds a thin writable layer on top. Layers are content-addressed and shared, so ten containers built from the same Server Core base consume one copy of that base on disk.
Two different things identify an image, and the exam likes the distinction:
Identifier Example Mutable? Use
Tag mcr.microsoft.com/windows/servercore:ltsc2025 Yes — a tag can be repointed to a new manifest Human-friendly version selection
Digest mcr.microsoft.com/windows/servercore@sha256:9f3c... No — content hash of the manifest Reproducible, pinned deployments
Because tags are mutable, :latest is never a safe production reference. Pin to an explicit OS tag such as ltsc2022 or ltsc2025 , or to a digest.
- Inspect what a host already holds: # List local images with repository, tag, image ID and size
- docker images
- # Show the layer history and the command that created each layer
- docker history mcr.microsoft.com/windows/servercore:ltsc2025
- # Full metadata as JSON, including digest, OS version and layer diff IDs
- docker inspect mcr.microsoft.com/windows/nanoserver:ltsc2025
- 2. Where Windows Base Images Come From
Windows container base images are served from the Microsoft Container Registry (MCR) at mcr.microsoft.com . MCR has no catalog experience of its own — it relies on existing catalogs such as Docker Hub for discovery, which is why you browse tags on Docker Hub but always pull from MCR: docker pull mcr.microsoft.com/windows/servercore:ltsc2025
Microsoft publishes four base images. The sizing and capability differences drive real exam scenarios:
Base image Approx. size What it gives you
windows/nanoserver Smallest footprint .NET Core / modern frameworks only. No PowerShell, no WMI, no servicing stack , 64-bit only
windows/servercore Medium Full .NET Framework, IIS, PowerShell 5.1, COM+, WOW64 — the "lift and shift" target
windows/server ~3.1 GB Full Windows API set, GPU acceleration support , no IIS connection limits. Requires a Windows Server 2025 installation
windows ~3.4 GB Full Windows client API surface, including graphics libraries
Important
The windows/server image is smaller than the windows image (3.1 GB vs 3.4 GB), inherits Server Core's reliability improvements, and is the one that supports GPU acceleration. The windows image isn't available for Windows Server 2025 . Candidates routinely assume "Windows Server" must be the larger of the two — it isn't.
Microsoft also ships insider variants ( windows/servercore/insider , windows/nanoserver/insider ) for hosts running Insider builds. Match insider images to insider hosts only.
The build-matching rule, restated for images
Section 8.4 introduced isolation modes; it matters again when you choose an image tag. Under process isolation the container base image build must match the host OS build exactly — an ltsc2022 image will not start under process isolation on an ltsc2025 host. Hyper-V isolation supplies a matching kernel in a utility VM, which is what allows a down-level image to run. When a scenario says "the image fails to start after we upgraded the hosts," the fix is either re-tagging to the new OS version or switching to --isolation=hyperv .
3. Tagging and Pushing to a Private Registry
Azure Container Registry (ACR) is the private registry for hybrid Windows workloads. The workflow is always the same four moves: authenticate, tag with the fully qualified login server, push, pull. # 1. Authenticate. Azure CLI is the recommended path; it refreshes the Docker credential store.
- az login
- az acr login --name myregistry
- # Azure PowerShell equivalent
- Connect-AzAccount
- Connect-AzContainerRegistry -Name myregistry
# 2. Create an alias of the local image using the fully qualified registry path.
# 'samples' is a namespace that keeps the registry root uncluttered.
docker tag myapp:1.0 myregistry.azurecr.io/samples/myapp:1.0
- # 3. Push the tagged image
- docker push myregistry.azurecr.io/samples/myapp:1.0
- # 4. Pull it on any other host that can authenticate
- docker pull myregistry.azurecr.io/samples/myapp:1.0
Tip
Always use the fully qualified registry name in all lowercase ( myregistry.azurecr.io ) both when logging in and when tagging. docker push myapp:1.0 without the registry prefix targets Docker Hub, not ACR — a very common lab failure.
The registry login server is always <registryname>.azurecr.io . For unattended pipelines you authenticate with a service principal rather than user credentials: docker login myregistry.azurecr.io and supply the service principal appID as the username and its secret as the password.
4. Managing Images in the Registry and Reclaiming Space
Registry-side inventory and cleanup are separate from local cleanup — deleting a local image does nothing to the registry. # Registry inventory
- az acr repository list --name myregistry --output table
- az acr repository show-tags --name myregistry --repository samples/myapp --output table
- # Delete the manifest behind a tag, its unique layers, and every other tag pointing at it
- az acr repository delete --name myregistry --image samples/myapp:1.0
The Azure PowerShell module Az.ContainerRegistry splits this into two cmdlets, and the difference is exam-worthy:
- Cmdlet Scope
- Remove-AzContainerRegistryRepository Removes all images in a namespace, e.g. all of samples/myapp
- Remove-AzContainerRegistryManifest Removes one tag/manifest, e.g. only samples/myapp:1.0
Local host cleanup uses different verbs entirely: # Remove one local image (fails if a container still references it)
docker rmi myregistry.azurecr.io/samples/myapp:1.0
- # Reclaim space from dangling (untagged) layers
- docker image prune
- containerd-only hosts
Modern Windows Server container hosts may run containerd with no Docker CLI present. The image verbs move to ctr and crictl : crictl images # list images known to the CRI runtime
- crictl pull mcr.microsoft.com/windows/nanoserver:ltsc2025
- crictl rmi <image-id> # remove an image
- 5. Exam Traps
- Scenario Correct response
- Push succeeds but the image lands on Docker Hub The tag lacked the myregistry.azurecr.io/ prefix
Image runs on the old host, fails on the rebuilt host Process isolation build mismatch — re-tag or use --isolation=hyperv
"Delete the image" after a docker rmi but it still pulls docker rmi is local only; use az acr repository delete
- Needs GPU acceleration inside a Windows container Use the windows/server base image on Windows Server 2025
- Needs PowerShell inside the container Nano Server has no PowerShell — use Server Core
- Must guarantee the exact same bits deploy everywhere Reference the image by digest , not by a mutable tag