Study guide

9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers

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.1 Azure VM Sizing, Series Selection & Managed Disk Tiers

Key Takeaways Explain This Topic AI

Azure VM series map to workload shape: D-series for general-purpose Windows Server, E-series for memory-bound workloads such as SQL Server, F-series for compute-bound processing, and L-series for storage throughput.

Premium SSD v1 derives IOPS and throughput from the provisioned capacity tier (P10 through P80), so buying performance means buying size.

Premium SSD v2 and Ultra Disk decouple capacity from performance, letting IOPS and throughput be provisioned and changed independently without resizing the disk.

Ultra Disk is the only tier that supports live adjustment of IOPS and throughput while the VM is running, which suits workloads with scheduled performance peaks.

Standard HDD and Standard SSD are transaction-billed and have no uptime SLA suitable for production databases; Premium and Ultra tiers carry the 99.999% managed-disk availability design target.

Last updated: August 2026

Azure VM Sizing, Storage & Managed Disk Management

Administering Windows Server workloads in Microsoft Azure Infrastructure as a Service (IaaS) requires aligning workload compute and storage demands with Azure virtual machine architectures. Enterprise applications—such as Active Directory Domain Services (AD DS), Microsoft SQL Server, Internet Information Services (IIS), and enterprise file services—exhibit distinct CPU, memory, and disk input/output (I/O) profiles. Selecting the incorrect VM series, managed disk tier, or host caching strategy leads to severe performance bottlenecks, unnecessary licensing expenditure, or catastrophic database corruption.

1. Azure Virtual Machine Sizing & Series Selection for Windows Server

Azure organizes virtual machine sizes into families and series optimized for specific computational, memory, and storage profiles. The presence of the lowercase letter s in a VM size name (e.g., Standard_D4s_v5 vs. Standard_D4_v5 ) indicates support for Premium Storage (Premium SSD and Ultra Disk). +-----------------------------------------------------------------------------+

  • | AZURE VM SERIES WORKLOAD TAXONOMY |
  • | |
  • | [D-SERIES: General Purpose] [F-SERIES: Compute Optimized] |
  • | - Ratio: 1 vCPU : 4 GiB RAM - Ratio: 1 vCPU : 2 GiB RAM |
  • | - Use: Domain Controllers, - Use: Batch Processing, Web Servers, |
  • | File Servers, App Tiers CPU-Bound Analytics |
  • | - Examples: Dsv5, Dadsv5 - Examples: Fsv2 |
  • | |
  • | [E/M-SERIES: Memory Optimized] [L-SERIES: Storage Optimized] |
  • | - Ratio: 1 vCPU : 8 GiB RAM - High-Throughput Direct Local NVMe |
  • | - Use: SQL Server OLTP, In- - Use: NoSQL (Cassandra, MongoDB), |
  • | Memory Caches, Large ERP Data Warehousing, High-Write Logs |
  • | - Examples: Esv5, Edsv5, M-series- Examples: Lsv2, Lsv3 |
  • +-----------------------------------------------------------------------------+

Primary VM Families for Windows Server Workloads:

General Purpose (D-Series - Dsv5, Dadsv5):

Architecture: Features a balanced 1:4 vCPU-to-memory ratio running on 3rd Generation Intel Xeon Platinum or AMD EPYC processors.

Workload Alignment: Ideal for Active Directory domain controllers, enterprise file servers, small-to-medium relational databases, and general application hosting.

Note: Sizes with an a designate AMD processors; sizes with a d include a local temporary SSD.

Compute-Optimized (F-Series - Fsv2):

Architecture: Features a 1:2 vCPU-to-memory ratio powered by Intel Xeon Platinum 8168 processors with high Turbo clock speeds.

Workload Alignment: Designed for compute-heavy batch processing, web server farms with high request volume but low memory footprint, video encoding, and analytics nodes.

Memory-Optimized (E-Series - Esv5, Edsv5 & M-Series):

Architecture: Features a 1:8 vCPU-to-memory ratio. The M-series scales up to 128 vCPUs and 4.0 TiB of RAM (or Mv2 up to 12 TiB of RAM).

Workload Alignment: Mandatory for memory-intensive enterprise database workloads, including Microsoft SQL Server OLTP, SAP HANA, and large in-memory cache architectures.

Storage-Optimized (L-Series - Lsv2, Lsv3):

Architecture: Provides high-throughput, low-latency direct-mapped local NVMe solid-state storage directly attached to the host hypervisor.

Workload Alignment: Tailored for big data engines, distributed NoSQL databases (e.g., Apache Cassandra, MongoDB), and data warehousing solutions requiring extreme local disk throughput.

Constrained vCPU Sizes for Database Licensing:

Sizing models such as Standard_E4-2s_v5 or Standard_E8-4s_v5 constrain the active vCPU count to 2 or 4 while preserving the full memory (32 GiB / 64 GiB), network bandwidth, and storage I/O limits of the parent 4-vCPU or 8-vCPU chassis.

Cost Benefit: SQL Server core-based licensing costs are reduced significantly while maintaining the extensive RAM and storage throughput required for database operations.

2. Azure Managed Disks: Performance Tiers & Characteristics

Azure Managed Disks are block-level storage volumes managed by Microsoft that abstract underlying physical storage accounts. They provide 99.999% (five nines) availability, automatic local redundancy (LRS or ZRS), and automated alignment with VM Fault Domains. +-----------------------------------------------------------------------------+

  • | AZURE MANAGED DISK TIERS COMPARISON |
  • | |
  • | TIER MAX IOPS MAX THROUGHPUT TYPICAL LATENCY BEST FOR |
  • | ---------------+-----------+----------------+----------------+------------|
  • | Standard HDD | 2,000 | 500 MB/s | High (>10ms) | Backup/Dev |
  • | Standard SSD | 6,000 | 750 MB/s | Single-digit ms| Web/Light |
  • | Premium SSD v1 | 20,000 | 900 MB/s | Low single-ms | SQL/AD Prod|
  • | Premium SSD v2 | 80,000 | 2,000 MB/s | Sub-millisecond| IOPS Tuning|
  • | Ultra Disk | 400,000 | 10,000 MB/s | Sub-millisecond| Extreme DB |
  • +-----------------------------------------------------------------------------+

Detailed Disk Tier Characteristics:

Standard HDD: Backed by magnetic spinning platters. Suited exclusively for non-critical dev/test environments, infrequently accessed backup repositories, and archival workloads where cost is the primary driver.

Standard SSD: Backed by solid-state drives. Delivers consistent entry-level performance for web frontends, lightweight application servers, and non-critical production workloads with moderate I/O demands.

Premium SSD (v1): Fixed-tier architecture (P1 through P80). Performance scales strictly with provisioned disk capacity (e.g., P30 provides 1,024 GiB capacity, 5,000 IOPS, and 200 MB/s throughput). Recommended for standard production Windows Server workloads, Active Directory databases, and production SQL Server instances.

Premium SSD v2: Advanced block storage enabling independent, granular provisioning of Disk Size (1 GiB–64 TiB) , IOPS (up to 80,000) , and Throughput (up to 2,000 MB/s) without paying for unwanted capacity. IOPS scale at 500 per GiB above a free 3,000 IOPS baseline, and throughput scales at 0.25 MB/s per provisioned IOPS above a free 125 MB/s baseline. Delivers consistent sub-millisecond latency. Does not support host caching; host caching must be set to None .

Ultra Disk: The highest-performance Azure block storage. Scales to a maximum of 400,000 IOPS and 10,000 MB/s throughput per disk with sub-millisecond latency, sized from 4 GiB to 64 TiB. IOPS scale at 1,000 per GiB and throughput at 0.25 MB/s per provisioned IOPS. Ultra Disks allow administrators to dynamically adjust IOPS and throughput on the fly without detaching the disk or restarting the virtual machine.

Constraints: Ultra Disks cannot be used as OS disks, do not support host caching, availability sets, or zone-redundant storage, and require the VM to be provisioned with Ultra Disk compatibility enabled. Performance can be changed at most four times in any 24-hour window.