The “free” Hyper-V myth and the turn to Azure Local
Hyper-V is a Windows Server role, not a separately priced product. In production that means Windows Server on every cluster host — usually Datacenter, because Standard includes rights for only two Windows machines and Storage Spaces Direct requires Datacenter. Microsoft steers new hyperconverged deployments toward Azure Local (formerly Azure Stack HCI): a fee for every physical core, billed through an Azure subscription.
Hyper-V host
subscription model
support
What you need to know before you compare TCO
- Hyper-V is not a cheap virtualisation layer “on top of Linux” — the host is Windows Server, licensed by physical cores (minimum 16 per server and 8 per processor).
- Standard: two Windows instances per full host-licence set; further pairs mean stacking. Datacenter: unlimited Windows machines on the licensed host.
- Azure Local L1 (hyperconverged, no external SAN) is a monthly host fee per physical core — public partner meters cluster around $10 / core / month. The first 60 days after registration carry no host fee.
- Optional Windows Server subscription for guests on Azure Local: $23.30 / physical core / month (Microsoft’s price list). It does not replace RDS CALs; AKS on Azure Local from the 2402 release is included in the host fee.
- Azure Hybrid Benefit can waive the L1 host fee and the Windows subscription — only with Windows Server Datacenter plus active Software Assurance (Enterprise Agreement or CSP), only L1 with cloud-connected management and no external storage. L2 and L3 do not get that waiver.
- Proxmox VE (AGPLv3) charges nothing for the hypervisor itself. The Standard subscription is €550 / socket / year and is optional. Windows guests still need Microsoft licences — details in Windows Server licensing on Proxmox.
Honest mapping: in an all-Windows estate on the same hardware, a Datacenter licence on the Hyper-V host also covers unlimited Windows guests. On Proxmox those same guests still need Datacenter or Standard on the host cores. The real TCO gap appears with Linux and containers, with Azure Local without Hybrid Benefit, and with the option to pin Windows to only some nodes.
TCO analysis — Hyper-V vs Azure Local vs Proxmox
Below is a 3-year platform cost for an HA cluster with quorum: 5 hypervisors, each 1 socket × 128 cores (640 physical cores). Classic Hyper-V: Windows Server 2025 Datacenter on all five hosts (list price $6,771 per 16 cores) plus Software Assurance at about 25% per year. Azure Local L1: about $10 / core / month for the host — excluding Windows guest licences. Proxmox VE: Standard subscription 5 × €550.
Note: This table excludes the migration project and CALs. Windows guest licences you pay on any platform are described separately below. Azure Local L1 is an approximate public-meter rate — confirm the live meter in the Azure pricing calculator.
| Cost component | Hyper-V (Datacenter) | Azure Local L1 | Proxmox VE |
|---|---|---|---|
| Licence / platform fee (year 1) | ~€252,000 (perpetual) | ~€71,400 (subscription) | €0 (open source) |
| Support / SA / host fee (year 1) | ~€63,000 (SA ~25%) | included in the L1 fee | €2,750 (5 sockets) |
| Platform × 3 years | ~€441,000 | ~€214,000 | €8,250 |
| Team training (one-off) | €0 (team already knows Hyper-V) | €0 (same stack) | ~€4,000 |
| 3-year TCO (excl. migration) | ~€441,000 | ~€214,000 | ~€12,250 |
Cost proportion visualisation (3 years, excl. migration, base = Hyper-V Datacenter)
Windows guests — when Hyper-V “includes” what Proxmox does not hide
Datacenter on a Hyper-V host covers unlimited Windows machines on that host. On Proxmox you pay for Windows separately, but you do not have to licence nodes on which Windows never runs. In a mixed cluster (Active Directory, files, SQL plus Linux and LXC) a strict node-affinity rule lets you keep Datacenter on two nodes instead of five.
| Windows guest scenario (5 × 128 cores) | 3-year cost (licence + SA) |
|---|---|
| Datacenter on all 5 hosts (typical Hyper-V / HA without pinning) | ~€441,000 |
| Datacenter on 2 hosts only, with strict Windows pinning | ~€176,000 |
| Azure Local: Windows subscription $23.30 / core / month on 640 cores, 3 years | ~€499,000 (on top of the L1 fee) |
Pinning Windows to two nodes saves about €265,000 in Datacenter licences over 3 years versus licensing the whole cluster. Hyper-V in a mixed cluster cannot do that: the Hyper-V role needs Windows Server on every host, even when the guest is Linux.
Microsoft contractual and licensing risk
Beyond the price list, choosing Hyper-V or Azure Local is a choice of purchasing model, audit exposure and the direction Microsoft is taking on-prem.
📋 Windows on every host
A Hyper-V cluster has no “bare” hypervisor. Linux, containers and open-source tooling still sit on licensed Windows Server. You pay the host-core tax even where the guest is not Windows.
☁️ Azure Local pressure
Microsoft steers new hyperconverged work to Azure Local: per-core fee, Azure registration, 60-day trial. Without Hybrid Benefit that is standing OPEX. L2 (external SAN / disaggregated) costs more than L1; L3 (disconnected control plane) is a custom quote.
📦 Bundling and Hybrid Benefit
Hybrid Benefit waives L1 only with Datacenter + SA and only without external storage. Moving to a SAN or disconnected mode removes the waiver. The terms live in the Product Terms, not on a partner slide.
⚖️ Audits and the 90-day rule
A physical-core licence stays with the host. Without Software Assurance in the per-VM model, moving licences between servers is limited (once every 90 days), which clashes with HA. CALs and RDS CALs are counted separately — on Proxmox too, if the guest is Windows.
🔧 Hypervisor support
Hyper-V is first-party. Proxmox VE is not on the SVVP list: Microsoft may require a Windows defect to be reproduced on Hyper-V or on bare metal. The Windows licence on Proxmox remains valid — that is a support-ticket issue, not a legality issue. Details: Windows Server on Proxmox.
🏢 On-prem roadmap
Classic Hyper-V on Windows Server remains, but Microsoft’s HCI, AKS and Arc investment runs through Azure Local. A Microsoft-first organisation should assume a rising share of subscription, not a one-off perpetual licence.
Technical platform comparison
Proxmox VE is a Debian- and KVM-based platform developed since 2008. Hyper-V is a type-1 hypervisor built into Windows Server. Below is a comparison from a typical IT department’s point of view — without either vendor’s marketing.
| Feature | Hyper-V / Azure Local | Proxmox VE | Advantage |
|---|---|---|---|
| Hypervisor | Hyper-V (Windows Server role) | KVM (Linux kernel) | PVE |
| Live migration | Live Migration | Proxmox Live Migration | Equal |
| HA / failover | Failover Clustering | Proxmox HA + Corosync | Equal |
| Shared storage | Storage Spaces Direct (Datacenter); CSV | Ceph or ZFS on a dedicated server | PVE (no Datacenter) |
| Containers | Windows containers / AKS on Azure Local | LXC built in | PVE (Linux) |
| Built-in backup | Windows Server Backup; Veeam separate | vzdump (built in); PBS separate | PVE |
| Panel / automation | Windows Admin Center, SCVMM, PowerShell, Arc | GUI, REST API, Terraform (community) | Equal |
| GPU passthrough | DDA / GPU-P (GPU-P + live migration from WS2025) | PCIe passthrough (native) | PVE |
| Windows guest — Microsoft support | First-party / SVVP | Works; no SVVP listing | Hyper-V |
| Virtualisation-layer price | Datacenter on the host or ~$10/core/month (L1) | €550/socket/year (support opt.) | PVE |
Proxmox VE covers typical mid-market and enterprise use cases outside Microsoft-only niches (Shielded VMs, Host Guardian Service, a strict SVVP matrix). For shared storage we recommend a dedicated ZFS server (TrueNAS/OpenZFS) with RoCE v2 networking — no Datacenter requirement, with live migration without stopping VMs.
When Proxmox is NOT the right choice
An honest analysis needs the scenarios where keeping Hyper-V or Azure Local can be rational.
- All-Windows stack, Datacenter already paid: if every guest is Windows, perpetual Datacenter licences with SA are in place, and Microsoft is not pushing you onto Azure Local — the incremental hypervisor cost is small. Proxmox savings then are mainly Linux/LXC, backup, and avoiding the L1 fee on an HCI refresh.
- Hybrid Benefit on Azure Local L1: Datacenter + SA under an EA/CSP, hyperconverged, no external SAN, cloud-connected management — Microsoft waives the L1 host fee and the Windows subscription. That is a real concession, not a slide. L2/L3 do not get it.
- First-party hypervisor requirement: some support contracts and application vendor matrices require a Windows incident to be reproduced on Hyper-V or on a server without virtualisation. If your ticket cycle regularly reaches Microsoft at the hypervisor layer, leaving Hyper-V for those VMs is cheaper than an SVVP argument.
- Shielded VMs / Host Guardian Service: guarded-machine isolation is a Microsoft-stack feature. Proxmox does not replace it 1:1.
- A fresh S2D cluster / deep SCVMM: if you have just built Storage Spaces Direct and System Center orchestration, sunk cost and team skills may outweigh licence savings for the remainder of the depreciation period.
Even then an audit is worth doing. Often the Windows that must stay on Hyper-V is a handful of VMs, and the rest — Linux, file services, test, containers — moves to Proxmox without an SVVP dispute. For the VMware comparison see VMware vs Proxmox — TCO analysis.
Migration ROI — financial model
The model below compares the annual Azure Local L1 fee (the path Microsoft steers new HCI toward) with Proxmox VE Standard on the same cluster: 5 sockets, 640 cores, about $10 / core / month vs 5 × €550 of support. Team training is a one-off €4,000. ROI (3 years) = net savings ÷ (Proxmox support 3× + training) × 100% ≈ €202k ÷ €12.25k ≈ 1,650%.
Note: the model excludes the migration project and Windows guest licences. If instead of Azure Local you stay on already-purchased perpetual Datacenter, year 1 is loaded with the licence buy (~€252,000) and years 2–3 are mostly SA — payback versus Proxmox still falls in year 1, but the figure depends on whether Datacenter is needed for Windows guests anyway.
savings vs L1
after 3 years
3-year period
Recommendation and next steps
For organisations with a mixed OS estate, with an Azure Local plan and no Hybrid Benefit, or with a large Linux and container footprint, Hyper-V → Proxmox VE is financially justified. The question is “which machines and when”, not “whether Microsoft’s hypervisor is free” — it is not.
Recommended decision path
- Step 1 — Environment audit (free): Hyper-V VM inventory, Windows vs Linux share, S2D, SCVMM, Azure Arc. Takes 2–5 business days.
- Step 2 — TCO analysis: split platform cost (Datacenter / Azure Local) from Windows guest licences. Scenario with Windows pinning vs licensing the whole cluster.
- Step 3 — Proof of Concept: convert 2–5 test VMs (Hyper-V export / virt-v2v) onto an isolated Proxmox cluster. Application and performance checks.
- Step 4 — Schedule: Linux and non-critical environments first; Windows with an SVVP requirement stays or goes last with a rollback plan.
- Step 5 — Wave migration: move in batches, with monitoring and the option to return to Hyper-V until stabilisation.
- Step 6 — Decommission Hyper-V hosts: remove the role, release Datacenter where Windows no longer runs, or reassign licences to Proxmox nodes that host Windows guests.
The best moment is an SA renewal, Windows Server 2016 end of support (January 2027), or an Azure Local decision. That leaves time for a calm VHDX conversion and for negotiating with Microsoft from a “we have a plan B” position.
Calculate Hyper-V vs Proxmox TCO
Book a free consultation — an engineer will split host cost, Azure Local and Windows guests in your cluster and say which machines are worth moving first.
⚡ Free evaluation → Windows Server licensing