Study guide

9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts

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.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts

Key Takeaways Explain This Topic AI

Flexible orchestration is the current default for Virtual Machine Scale Sets and permits mixed VM sizes, a blend of Spot and Pay-as-You-Go instances, and per-instance data disks.

Uniform orchestration treats instances as identical, fungible clones and is aimed at large stateless fleets rather than individually addressable servers.

Autoscale rules pair metric or schedule triggers with a cool-down period, typically 10 to 30 minutes, during which the engine ignores further triggers to prevent scale flapping.

Rolling upgrades and Automatic OS Image Upgrades replace instances in batches so that a Windows image update never takes the whole scale set offline at once.

Azure Dedicated Hosts give a customer an entire physical server for isolation and licensing control, and let the customer choose the maintenance window.

Last updated: August 2026

  • Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts
  • 1. Virtual Machine Scale Sets (VMSS): Flexible vs Uniform Orchestration

Azure Virtual Machine Scale Sets (VMSS) allow administrators to deploy and manage a group of load-balanced virtual machines. VMSS supports two distinct orchestration modes: +-----------------------------------------------------------------------------+

  • | VMSS UNIFORM VS FLEXIBLE ORCHESTRATION MODES |
  • | |
  • | UNIFORM ORCHESTRATION MODE FLEXIBLE ORCHESTRATION MODE |
  • | - Identical VMs from single model - Heterogeneous VM sizes & OS types |
  • | - Golden image deployment - Mix Spot & Pay-as-You-Go VMs |
  • | - Scalability: Up to 1,000 instances - Individual VM lifecycle management|
  • | - Hidden individual VM objects - Standard VM APIs & ARM templates |
  • | - Best for: Cloud-Native Stateless - Best for: Statefully Managed App |
  • | Web Frontends / Worker Farms Stacks, Hybrid Windows Workloads |
  • +-----------------------------------------------------------------------------+

Detailed Orchestration Comparison:

Uniform Orchestration Mode (Legacy / Cloud-Native):

Uses a centralized VM template model. Every instance in the scale set is identical in size, image, and disk configuration.

Supports scaling up to 1,000 instances with platform images (or 600 with custom images).

Individual VM instances are child resources of the scale set and cannot be managed independently using standard Azure VM management commands.

Flexible Orchestration Mode (Modern Enterprise Standard):

Provides unified management across identical or heterogeneous virtual machines.

Heterogeneous Sizing: Mix different VM series, sizes, and OS versions within the same scale set.

Cost Optimization: Mix Spot VMs (for fault-tolerant batch computing at deep discounts) with Standard Pay-as-You-Go VMs in defined ratios within a single scale set.

High Availability Spreading: Automatically spreads instances across Fault Domains (up to 5 FDs) within a region or across Availability Zones (Zone 1, 2, 3).

Full VM Lifecycle Support: Every VM is a standard first-class Azure VM object. Supports standard Azure Backup, Azure Site Recovery, individual disk attachments, and Azure Arc management.

2. Autoscale Policies: Metric-Based vs Schedule-Based Scaling

Azure Monitor Autoscale dynamically increases (scale out) or decreases (scale in) the number of VMSS instances to match application demand. +-----------------------------------------------------------------------------+

  • | AUTOSCALE DECISION ENGINE & FLAPPING |
  • | |
  • | [METRIC COLLECTION] ---> Azure Monitor Agent collects CPU / Memory / Queue|
  • | | |
  • | v |
  • | [RULE EVALUATION] ---> Is Average CPU > 75% for 10 consecutive minutes? |
  • | | |
  • | v (YES) |
  • | [SCALE-OUT ACTION] ---> Increase instance count by +2 VMs |
  • | | |
  • | v |
  • | [COOL-DOWN TIMER] ---> Block all scaling actions for 20 minutes |
  • | (Prevents Rapid Oscillation / 'Flapping') |
  • +-----------------------------------------------------------------------------+

Autoscale Rule Architecture:

Metric-Based Scaling Rules:

Host Compute Metrics: Default platform metrics like Percentage CPU or Network In/Out collected without guest agents.

Guest OS Metrics: Memory demand (e.g., Available Memory Bytes ), disk queue depth, or custom Windows Performance Counters collected via the Azure Monitor Agent (AMA) .

Application Queue Metrics: Azure Service Bus queue length or Azure Storage Queue message counts (e.g., scale out when queue depth exceeds 500 messages per instance).

Scale-Out vs. Scale-In Asymmetry:

Scale-Out Rule: Aggressive threshold (e.g., scale out by 2 instances when Average CPU > 75% over 5 minutes).

Scale-In Rule: Conservative threshold (e.g., scale in by 1 instance when Average CPU < 25% over 15 minutes).

Why? Prevents premature deallocation of instances during minor traffic lulls.

Cool-Down Periods & Flapping Prevention:

The cool-down period is a mandatory waiting time (typically 10 to 30 minutes) after a scaling action during which the autoscale engine ignores metric triggers.

Flapping: A disastrous condition where a scale-in action reduces capacity, immediately causing remaining VMs to breach high-utilization thresholds, triggering an immediate scale-out action. Cool-down periods allow new VMs to boot, warm up caches, and stabilize telemetry before further scale actions occur.

Schedule-Based Scaling Rules:

Overrides default metric profiles during predictable calendar events.

Example: Scale the base instance count from 2 to 10 instances every Monday through Friday from 08:00 to 18:00 UTC, returning to 2 instances during weekends and off-peak hours.

3. Rolling Upgrades & Automatic OS Image Upgrades for Windows VMSS

Maintaining guest OS patch compliance across hundreds of Windows Server VMSS instances without application downtime requires Rolling Upgrade Policies . +-----------------------------------------------------------------------------+

  • | VMSS ROLLING UPGRADE BATCH EXECUTION |
  • | |
  • | [BATCH 1: 20% Instances] ---> Upgrade OS -> Wait for Health Probe OK ----+||
  • | ||
  • | v|
  • | [BATCH 2: 20% Instances] ---> Upgrade OS -> Wait for Health Probe OK ----+||
  • | ||
  • | v|
  • | [BATCH 3: 20% Instances] ---> Upgrade OS -> Wait for Health Probe OK ----+||
  • | ||
  • | (If Health Probe fails at any batch -> ROLLBACK & HALT UPGRADE) v|
  • +-----------------------------------------------------------------------------+

Upgrade Modes:

Manual: Instances are updated only when explicitly initiated by an administrator via PowerShell or CLI.

Automatic: When a new VMSS model or image is committed, Azure automatically upgrades all instances simultaneously (causes downtime unless orchestrated).

Rolling: Azure updates instances in controlled batches (e.g., 20% max batch size).

Application Health Extension:

Deployed inside the Windows Server guest OS to monitor local application health (e.g., testing http://localhost:80/health ).

Azure verifies the Application Health Extension reports Healthy before moving to the next rolling upgrade batch.

Automatic OS Image Upgrades:

When Microsoft publishes monthly Windows Server security patches to the Azure Marketplace, the scale set automatically rolls out the updated base image batch by batch with zero downtime.

4. Azure Dedicated Hosts

An Azure Dedicated Host provides a physical hardware server in an Azure datacenter that is completely dedicated to running a single customer's virtual machines. +-----------------------------------------------------------------------------+

  • | AZURE DEDICATED HOST ARCHITECTURE |
  • | |
  • | [DEDICATED HOST GROUP (Region: East US, Zone 1, FD: 2)] |
  • | +---------------------------------------------------------------------+ |
  • | | Physical Server (Dedicated Single Tenant) | |
  • | | - Intel Xeon Hardware Isolation (Complies with HIPAA / DoD / PCI) | |
  • | | - Maintenance Control Window (Defer OS hypervisor patching 35 days)| |
  • | | - Azure Hybrid Benefit (License physical cores for unlimited VMs) | |
  • | | | |
  • | | +---------------------------------------------------------------+ | |
  • | | | Guest VMs: [VM-DC01] [VM-SQL01] [VM-APP01] [VM-FINANCE01] | | |
  • | | +---------------------------------------------------------------+ | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+

Key Enterprise Benefits of Dedicated Hosts:

Hardware Isolation: Guarantees no other customer's VMs run on the physical server, satisfying strict regulatory frameworks (PCI-DSS, HIPAA, FedRAMP High).

Maintenance Control: Allows administrators to control and defer platform maintenance updates for up to 35 days, scheduling host patching during planned maintenance windows.

Licensing Optimization with Azure Hybrid Benefit: By licensing all physical processor cores on the Dedicated Host with Windows Server Datacenter edition (with Software Assurance), customers obtain unlimited Windows Server virtualization rights on that host without licensing individual VMs.

  • PowerShell Deployment: VMSS Flexible Mode with Autoscale # Create a Resource Group and Virtual Network
  • $rg = 'RG-ScaleSets'
  • $loc = 'eastus'
  • New-AzResourceGroup -Name $rg -Location $loc
  • # Create a VMSS in Flexible Orchestration Mode across 3 Availability Zones
  • $vmssConfig = New-AzVmssConfig `
  • Location $loc `
  • OrchestrationMode 'Flexible' `
  • PlatformFaultDomainCount 1 `
  • Zone '1','2','3'
  • Set-AzVmssStorageProfile $vmssConfig `
  • OsDiskCreateOption 'FromImage' `
  • OsDiskCaching 'ReadWrite' `
  • ImageReferencePublisher 'MicrosoftWindowsServer' `
  • ImageReferenceOffer 'WindowsServer' `
  • ImageReferenceSku '2022-datacenter-azure-edition' `
  • ImageReferenceVersion 'latest'
  • # Commit VMSS deployment
  • New-AzVmss -ResourceGroupName $rg -VMScaleSetName 'VMSS-AppFlex' -VirtualMachineScaleSet $vmssConfig