Hyper-V on Azure Complete Guide: Nested Virtualization, AVS, Azure Migrate, and Windows Server 2025

Hyper-V on Azure runs Hyper-V (Microsoft's virtualization technology) on top of an Azure VM using Nested Virtualization. Guest VMs run inside the Azure VM (the Parent). Typical use cases: 1) Hyper-V test and training environments (real Hyper-V lab setups), 2) isolated execution of legacy Windows apps, 3) AKS nested container environments, 4) developer virtualization validation via Visual Studio Subscription, 5) Hyper-V Failover Cluster behavior testing, 6) Windows Server 2025 new feature validation. Available on Nested Virtualization-capable VM sizes (Dv4/Dv5, Ev4/Ev5, Fv2, parts of the M series). Microsoft does not recommend Nested Virtualization for production workloads — it is positioned for validation, training, and special-purpose scenarios.

Key limitations: 1) VM size restrictions (only Dv4/Dv5, Ev4/Ev5, Fv2, parts of the M series — B series and older v2/v3 series are unsupported), 2) performance degradation (Guest VMs are slower than the Parent VM, roughly 20-30% overhead), 3) Live Migration is not supported (Azure automatic maintenance may move the Parent VM and restart Guest VMs), 4) Azure Backup cannot back up Guest VMs (only Parent VM-level backup), 5) reduced accuracy of performance counters, 6) network performance degradation (nested NIC latency), 7) GPU Passthrough not supported, 8) Azure service integration is difficult (Guest VMs are not Azure VMs, so features like Managed Identity are unavailable). It is unsuitable for production and should be limited to validation and training scenarios.

Azure VMware Solution (AVS) is a Microsoft-managed dedicated VMware vSphere environment inside Azure — fundamentally different from Hyper-V on Azure. AVS: 1) runs VMware vSphere, vCenter, NSX-T, and vSAN on Azure for production workloads, 2) enables complete lift-and-shift of existing VMware workloads, 3) runs on dedicated bare-metal hosts (AV36, AV52, AV64 series), 4) supports zero-downtime migration from on-premises to AVS via VMware HCX, 5) is production-supported (officially by Microsoft and VMware), 6) is extremely expensive (millions to tens of millions of yen per month, minimum 3-host configuration), 7) includes VMware licensing in the price. Use Hyper-V on Azure (Nested) for training/validation, AVS for production VMware, and direct Azure VM migration for cloud-native modernization — they serve distinct purposes.

Standard deployment procedure: 1) Select a Nested Virtualization-capable VM size (e.g., Standard_D8s_v5 = 8 vCPU, 32 GB RAM), 2) Choose Windows Server 2022/2025 (versions that can install the Hyper-V role), 3) After deployment, add the Hyper-V role via Server Manager or PowerShell: Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart, 4) After reboot, create a Virtual Switch in Hyper-V Manager (Internal/External/Private), 5) Create a Guest VM (via Hyper-V Manager or the New-VM cmdlet), 6) Install an OS on the Guest VM (ISO upload or Sysprep image), 7) Configure Guest VM networking. Linux (Ubuntu Server) also supports KVM/Nested Virtualization, but Microsoft primarily recommends Windows Server + Hyper-V. Premium SSD is recommended for the Parent VM disk (it greatly impacts Guest VM performance), and at least 32 GB of memory is recommended (assuming multiple Guest VMs).

Standard pattern for migrating on-prem Hyper-V VMs to Azure VM: 1) Use Azure Migrate Discovery to scan Hyper-V hosts and obtain a VM inventory plus right-sizing recommendations, 2) Use Azure Migrate Replication to transfer VHD/VHDX files to an Azure Storage Account (initial replication takes hours to days), 3) Continuously sync via Delta Replication (replicate on-prem VMs while they remain in production), 4) Verify boot in Azure via Test Migration, 5) Execute Cutover to switch production (stop on-prem VM, start Azure VM), 6) Switch over DNS and access endpoints. Typical timeline: 3-6 months for a 100-VM migration project. Convert VHDs to either Generation 1 (BIOS) or Generation 2 (UEFI) for Azure VM; Linux VMs need Cloud-init support, and Windows VMs should use Sysprep. Azure Migrate is free — only the Replication Storage Account incurs cost — and it is the de facto standard tool for Hyper-V to Azure migration.

New Hyper-V features in Windows Server 2025: 1) GPU Partitioning (GPU-P) GA (share a physical GPU across Hyper-V Guest VMs for ML workloads), 2) Discrete Device Assignment (DDA) improvements (enhanced GPU/FPGA passthrough), 3) Storage Pool with NVMe over Fabric support (improved storage performance), 4) Stronger AMD CPU support for Nested Virtualization (previously Intel-focused), 5) Improved hot-add/hot-remove of memory and vCPU, 6) Hyper-V Replica improvements (Multi-target Replica replicates one VM to multiple DR sites simultaneously), 7) Tighter integration with Azure Local (successor to Azure Stack HCI), 8) Runtime protection via Microsoft Defender for Hyper-V Hosts, 9) IaC-style configuration via PowerShell DSC for Hyper-V. AZ-800/AZ-801 exams increasingly cover these Windows Server 2025 features — study the latest version.

AZ-800 (Windows Server Hybrid Administrator) covers Hyper-V deeply in Domain 3 (Manage virtual machines and containers, 15-20%) — a core topic for that area. AZ-801 (Configuring Windows Server Hybrid Advanced Services) covers advanced features like Hyper-V Failover Cluster and Hyper-V Replica. AZ-140 (AVD Specialty) covers AVD host validation using Nested Virtualization (Hyper-V on Azure VM). AZ-104 (Administrator) covers Azure VM fundamentals, and AZ-305 (Solutions Architect Expert) covers VMware vs Hyper-V vs Azure VM selection. For infrastructure engineers working with the Microsoft Windows Server ecosystem, Hyper-V is an essential skill.

Hyper-V alternatives and complements: 1) Windows Container (Docker Desktop for Windows Server) — container-level isolation, lightweight, fast startup, ideal for production microservices, 2) Hyper-V Container (Microsoft's container-in-Hyper-V configuration with stronger isolation, ideal for multi-tenant SaaS), 3) WSL2 (Windows Subsystem for Linux 2) — a Linux environment powered by Hyper-V internally, designed for developers running Linux tooling (not recommended for production), 4) Azure Container Apps (Microsoft-managed serverless containers) — the best choice when you only need to run containers, 5) AKS (Azure Kubernetes Service) — production container orchestration. Decision guide: 1) Need full VM isolation → Hyper-V, 2) Containers will do → Container/AKS, 3) Linux dev environment → WSL2, 4) Serverless → Azure Container Apps. The modern best practice is containers first for new projects, with Hyper-V reserved for legacy Windows workloads, legacy apps, and special requirements.