For estates already anchored in Windows Server, Active Directory and Azure, Azure Local (formerly Azure Stack HCI) is the most natural VMware alternative to weigh. It pairs the Hyper-V hypervisor with Storage Spaces Direct and hooks the whole cluster into Azure through Arc. The calculator below sizes your migration and prices both routes; this guide explains where Microsoft's stack wins and where it doesn't.
| VMs | Hosts | VMware VCF / yr | Azure Local (Hyper-V) / yr | 3-yr saving |
|---|---|---|---|---|
| 50 | 3× | £50,304 | £18,000 | £96,912 |
| 100 | 5× | £83,840 | £30,000 | £161,520 |
| 250 | 10× | £167,680 | £60,000 | £323,040 |
| 500 | 18× | £301,824 | £108,000 | £581,472 |
All figures are indicative estimates for planning only and subject to change; licence prices vary by reseller and deal size, and any monthly finance figure is subject to credit approval — not a quotation.
Hyper-V and Storage Spaces Direct vs the vSphere stack
Azure Local replaces ESXi with Hyper-V and vSAN with Storage Spaces Direct (S2D), delivering hyper-converged compute and storage from the same validated nodes. The building blocks map cleanly onto vSphere concepts — clusters, live migration, resilient mirror or parity volumes — so VMware admins rarely start from zero. The trade-off is maturity of tooling: features that feel turnkey in vCenter can need more deliberate design in S2D, and node counts, fault domains and reserve capacity should be sized carefully rather than assumed. The calculator reflects that in its host maths.
Licensing: per-core Windows Server Datacenter or Azure subscription
This is where Azure Local diverges most sharply from VMware's per-core VCF bundles. You can run Datacenter edition licences you may already own, unlocking unlimited Windows guest virtualisation, or consume Azure Local as a per-core Azure subscription billed through your existing agreement. Organisations with Software Assurance, an Enterprise Agreement or heavy Windows guest counts often find the numbers land very differently from a like-for-like Broadcom renewal. Because the split depends on your exact core count and guest OS mix, the tool prices both models against your inputs rather than quoting a headline rate.
When the Microsoft-native route pays off
Azure Local rewards Microsoft-centric estates. If you already lean on Azure for backup, Site Recovery, monitoring and identity via Entra, running your on-prem hypervisor as an Arc-managed extension of that tenancy removes a whole toolchain rather than adding one. Hybrid and edge scenarios — branch clusters, DR into Azure, consistent policy from cloud to floor — are the natural sweet spot. Estates that are Linux-heavy, multi-cloud or want a hypervisor with no cloud dependency will usually find a cleaner fit elsewhere in this comparison cluster.
FAQs
Is Azure Local the same as Azure Stack HCI?
Yes. Azure Local is Microsoft's current name for the platform previously branded Azure Stack HCI. It's the same Hyper-V plus Storage Spaces Direct architecture, Arc-connected to Azure. The rename broadened the scope to cover a wider range of on-premises and edge hardware, but for a VMware migration the technology and licensing you're evaluating are unchanged.
Do I need an Azure subscription to run Azure Local?
Yes — Azure Local registers with Azure through Arc and is billed either per core as an Azure subscription or via Windows Server Datacenter licences, with an Azure connection still required for management and updates. It's not a fully air-gapped product. If a permanently disconnected on-prem hypervisor is a hard requirement, other VMware alternatives suit better.
Can I reuse my existing VMware servers for Azure Local?
Sometimes, but check carefully. Azure Local expects validated hardware and specific network and storage configurations for Storage Spaces Direct to be supported. Some VMware-era nodes qualify; others don't, particularly around drives and NICs. The calculator sizes a fresh, properly configured cluster, and Servnet can assess whether your current fleet can be repurposed or should be replaced.