Study guide
9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups
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
9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups
Key Takeaways Explain This Topic AI
An Availability Set spreads VMs across 2 to 3 Fault Domains and up to 20 Update Domains, delivering a 99.95% uptime SLA once two or more VMs are in the set.
Availability Zones place VMs in physically separate datacenters within one region and carry Azure's highest single-region compute SLA at 99.99%.
A region that does not offer Availability Zones leaves the Availability Set as the only rack- and maintenance-fault protection available.
Proximity Placement Groups co-locate resources to cut inter-tier network latency, and are the fix for chatty multi-tier stacks such as IIS calling a SQL Server Always On cluster.
Combining a Proximity Placement Group with Availability Zones is contradictory, because zones are deliberately far apart while a PPG is deliberately close together.
Last updated: August 2026
Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups
Designing resilient enterprise infrastructure in Microsoft Azure requires engineering against both planned platform maintenance (such as hypervisor OS patching) and unplanned hardware failures (such as physical power supply outages, top-of-rack switch failures, or datacenter disasters). Windows Server workloads deployed in Azure IaaS must be architected across availability constructs to meet strict enterprise Service Level Agreements (SLAs). This section covers the three placement constructs — Availability Sets , Availability Zones , and Proximity Placement Groups (PPGs) — and the SLA each one earns. Virtual Machine Scale Sets (VMSS) , autoscale rules, and Azure Dedicated Hosts are covered in section 9.4.
1. High Availability Architecture: Availability Sets vs Availability Zones
Azure provides hierarchical availability tiers depending on whether protection is needed against rack-level hardware failure, hypervisor updates, or entire datacenter facility disruptions. +-----------------------------------------------------------------------------+
- | AZURE HIGH AVAILABILITY ARCHITECTURE HIERARCHY |
- | |
- | [AVAILABILITY SET] [AVAILABILITY ZONES] |
- | - Scope: Single Datacenter - Scope: Entire Azure Region |
- | - Protects: Rack / Power / Host - Protects: Facility / Flooding / Grid |
- | - SLA: 99.95% (2+ VMs) - SLA: 99.99% (2+ VMs across Zones) |
- | |
- | +-------------------------------+ +-----------------------------------+ |
- | | Datacenter A | | Region (e.g., East US) | |
- | | +-----------+ +-----------+ | | +-----------+ +-------+ +-------+ | |
- | | | Rack 1 | | Rack 2 | | | | Zone 1 | | Zone 2| | Zone 3| | |
- | | | FD 0 /UD 0| | FD 1 /UD 1| | | | (DC 1) | | (DC 2)| | (DC 3)| | |
- | | | [VM-APP01]| | [VM-APP02]| | | | [VM-DB01] | |[VM-DB2]| |[VM-DB3]| | |
- | | +-----------+ +-----------+ | | +-----------+ +-------+ +-------+ | |
- | +-------------------------------+ +-----------------------------------+ |
- +-----------------------------------------------------------------------------+
Availability Sets Mechanics:
An Availability Set is a logical grouping of VMs within a single Azure datacenter that isolates VM instances across distinct physical hardware infrastructure:
Fault Domains (FDs):
Definition: Represents a physical rack of servers sharing a common power supply unit (PSU) and top-of-rack (TOR) network switch.
Allocation: Azure regions provide 2 or 3 Fault Domains per Availability Set (FD 0, FD 1, FD 2).
Purpose: Protects against physical hardware failures, cable faults, and power interruptions. VMs in distinct FDs will never fail simultaneously due to a single physical hardware failure.
Managed Disk Alignment: When using Managed Disks, Azure automatically aligns the storage cluster fault domains with the compute fault domains, preventing shared storage hardware failures.
Update Domains (UDs):
Definition: A logical grouping of underlying physical hypervisors that can undergo scheduled platform maintenance or reboot simultaneously.
Allocation: Configurable from 1 to 20 Update Domains (default is 5).
Purpose: When Microsoft patches the underlying host hypervisors, only one Update Domain is rebooted at a time . The platform pauses for a 30-minute recovery window before proceeding to the next UD, ensuring remaining VM instances handle active client traffic.
SLA: Deploying two or more VMs across distinct FDs and UDs in an Availability Set guarantees a 99.95% uptime SLA .
Availability Zones Mechanics:
Availability Zones are physically separate datacenter facilities within an Azure region, each equipped with independent power, cooling, and high-speed fiber networking.
Regional Isolation: Protects workloads against catastrophic datacenter-level disasters (e.g., regional power grid failure, major fire, flooding).
Latency Profile: Inter-zone fiber networks deliver round-trip latency under 2 milliseconds , supporting synchronous database replication (such as SQL Server Always On Availability Groups with synchronous commit).
SLA: Distributing two or more VMs across two or more Availability Zones in the same region provides Azure's highest single-region compute SLA: 99.99% uptime .
Zonal vs. Zone-Redundant Resources:
Zonal Resource: A VM pinned explicitly to a single zone (e.g., Zone 1 ).
Zone-Redundant Resource: An Azure resource (e.g., Standard Load Balancer, Zone-Redundant Gateway, ZRS Managed Disk) whose underlying infrastructure spans all three zones automatically.
- Feature Single VM (Premium Disk) Availability Set Availability Zones
- Scope Single Host Single Datacenter (Racks) Multiple Datacenters (Region)
- Fault Domains None 2 to 3 FDs 3 Availability Zones
- Update Isolation None Up to 20 UDs Independent Zone Maintenance
- Availability SLA 99.9% 99.95% 99.99%
- Network Latency Lowest Sub-millisecond < 2 ms (Inter-zone)
- 2. Proximity Placement Groups (PPGs)
While Availability Zones disperse VMs across different datacenters for disaster isolation, certain tightly coupled multi-tier Windows workloads require the absolute lowest possible physical network latency. +-----------------------------------------------------------------------------+
- | PROXIMITY PLACEMENT GROUP (PPG) TOPOLOGY |
- | |
- | [SAME AZURE DATACENTER / COMPUTE SPINE] |
- | +---------------------------------------------------------------------+ |
- | | Proximity Placement Group: PPG-Production | |
- | | | |
- | | +---------------------------+ +-----------------------------+ | |
- | | | Web/App Tier (IIS) | | Clustered Backend (SQL AG) | | |
- | | | [VM-WEB01] [VM-WEB02] | | [VM-SQL01] [VM-SQL02] | | |
- | | +---------------------------+ +-----------------------------+ | |
- | | \ / | |
- | | ===[Sub-Millisecond RTT]== | |
- | +---------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------+
Architecture: A Proximity Placement Group (PPG) is a logical grouping constraint that forces Azure to provision all assigned compute resources (standalone VMs, Availability Sets, or VMSS) within the same physical datacenter cluster and network spine.
Latency Objective: Reduces network round-trip time (RTT) between application tiers (e.g., IIS web servers calling a backend SQL Server clustered instance) to sub-millisecond levels.
Architectural Trade-offs & Allocation Constraints:
Because PPGs pin VMs to a specific physical hardware cluster, future VM scaling or resizing operations may fail if the specific physical cluster runs out of capacity ( OverconstrainedAllocationRequest ).
Best Practice: When deploying a PPG, deploy all required VMs and scale sets simultaneously during initial rollout rather than incrementally over time.