Azure Stack HCI (Azure Local) vs Hyper-V: What Is the Difference and Which Should You Choose?
Microsoft.AzureStackHCI. This guide uses “Azure Local” for the current product and notes “Azure Stack HCI” where older material applies. Licensing, pricing and supported configurations change quickly, so confirm figures on Microsoft’s pages before you buy.
Both products run virtual machines on the Hyper-V hypervisor, which is exactly why they get confused. The decision between them is less about the hypervisor and more about the operating model around it.
Windows Server with the Hyper-V role is a general-purpose operating system you license, install on certified hardware and manage on your own terms. Azure Local is a purpose-built, cloud-connected hyperconverged platform that is billed through Azure, runs on validated hardware and is managed primarily through Azure Arc. This guide explains the relationship, then compares licensing, clustering, storage, networking, high availability and Azure integration in practical terms, and finishes with a decision guide for common scenarios.
⚡ Quick Summary
- Relationship: Azure Local and Windows Server Hyper-V share the same core virtualization technology: Hyper-V, Windows Server Failover Clustering and Storage Spaces Direct. They differ in packaging, billing, hardware rules and how they are managed.
- Azure Local: a purpose-built host OS sold as an Azure service, billed per physical core, run on validated hardware, always cloud-connected (or on a local control plane with disconnected operations), and managed through Azure Arc.
- Windows Server Hyper-V: a role in a general-purpose OS, licensed with traditional or pay-as-you-go licensing, run on any certified hardware, optionally connected to Azure.
- Choose Azure Local when you want a standardized HCI platform with Azure-native management, built-in AKS or AVD, and consistent updates across many sites.
- Choose Windows Server Hyper-V when you need hardware freedom, host-level roles, flexible storage, long servicing cycles or no cloud dependency.
- The big picture: how the two relate
- What each product is and where it runs
- Licensing and billing
- Clustering and high availability
- Storage
- Networking
- Azure integration: Arc, Monitor, Backup, Site Recovery
- Management and lifecycle
- Which workloads and scenarios suit each
- Where they overlap
- Decision guide
- FAQ
- Sources
The big picture: how the two relate
The comparison is often framed as “Azure Stack HCI versus Hyper-V”, but those names are not parallel. Hyper-V is a hypervisor. Windows Server is an operating system that can host it. Azure Local is a different operating system and service that also uses Hyper-V. The fair comparison is Azure Local against Windows Server running Hyper-V, usually with failover clustering and optionally Storage Spaces Direct.
Windows Server 2025 + Hyper-V
Azure Local
Simplified view. Details vary by deployment type and release.
What each product is and where it runs
| Attribute | Azure Local | Windows Server (Hyper-V) |
|---|---|---|
| What it is | Cloud-connected hyperconverged infrastructure platform and host OS | Multi-purpose OS that can host Hyper-V VMs, run roles directly, or act as a guest |
| Where it runs | Customer-owned datacenter or edge sites, on validated hardware (Azure Local Catalog lists more than 200 pre-validated solutions) | On-premises, in the cloud or at the edge, on any hardware with the “Certified for Windows Server” logo |
| Cloud connection | Required, at least once every 30 days (connected deployments) | Optional (needed for Azure Arc or Pay-as-You-Go licensing) |
| Hosts roles directly | No. Run workloads in VMs or containers | Yes |
| Used as a guest OS | Evaluation only | Yes |
| Support | Covered under Azure support | Covered by Windows Server support agreements |
| Lifecycle | Always up to date, with up to six months to install updates | LTSC: 5 years mainstream plus 5 years extended. Annual Channel: 18 months plus 6 months |
| How you get it | Download from the Azure portal, or buy preinstalled on integrated systems | Volume Licensing Service Center or Evaluation Center |
Licensing and billing
This is the area where the two products differ most, and the one where the details have changed over time. Azure Local was announced under per-core subscription pricing, and Microsoft has since restructured it into deployment tiers.
Azure Local
- Host service fee: billed per physical core through your Azure subscription. You are billed daily for all physical cores while the system is registered, and hyperthreading is not counted.
- Free trial: the first 60 days after registration.
- Deployment tiers: Microsoft’s pricing page now separates L1 (hyperconverged, no external storage), L2 (multi-rack, disaggregated, or hyperconverged with external storage) and L3 (disconnected operations with a locally hosted control plane, priced through your account representative).
- Reported list prices: secondary sources report about $10 per core per month for L1 and about $20.10 for L2. Microsoft’s page loads prices through a region selector, so confirm current figures in the Azure pricing calculator.
- Guest licensing is separate. The host fee does not include Windows Server or paid Linux guest rights. You can use Azure Hybrid Benefit or buy the Windows Server subscription add-on, listed at $23.30 per physical core per month, which gives unlimited Windows Server guest rights.
- Azure Hybrid Benefit: if you hold Windows Server Datacenter with active Software Assurance, you can exchange core licenses to waive both the L1 host fee and the Windows Server subscription. Microsoft states it is available only for L1, not for L2 or L3.
- OEM license: a prepaid, per-core license preinstalled on Premier Solutions, Integrated Systems and Validated Nodes. It does not renew, is tied to the original hardware and includes Windows Server Datacenter 2025 guest rights, but not next-version rights. If you attach external storage, Microsoft says the monthly service fee applies.
- Included: AKS enabled by Azure Arc is included with Azure Local from the 2402 release, and Extended Security Updates for Windows Server are included.
Windows Server with Hyper-V
- Host licensing: traditional per-core licenses (with Software Assurance as an option), or Windows Server Pay-as-You-Go through Azure Arc.
- Guests: Standard Edition includes rights for two VMs per licensed set. Datacenter Edition includes unlimited VMs.
- CALs: client access licenses are required for each user or device. Pay-as-You-Go includes CALs for standard functionality, but not RDS CALs.
- Azure benefits are optional. Arc-enabled management adds Azure Update Manager, and Azure Hybrid Benefit makes it free for Windows Server 2025.
Side by side
| Cost element | Azure Local | Windows Server Hyper-V |
|---|---|---|
| Model | Operating expense subscription, billed through Azure | Capital expense licenses, or Pay-as-You-Go |
| Host | Per physical core per month (tier-dependent), waivable for L1 with Datacenter + SA | Per core license (Standard or Datacenter) |
| Windows Server guests | Windows Server subscription, Azure Hybrid Benefit, or bring your own license | Standard: 2 VMs. Datacenter: unlimited |
| CALs | Not licensed for direct client connections to the host. Needed for guests as usual | Required |
| Hardware | Bought separately from validated catalog, or as integrated system | Any certified hardware |
| Extended Security Updates | Included | Purchased separately |
A worked example (illustrative list-price arithmetic)
Take a two-node branch cluster with 16 physical cores per node, so 32 cores, running Windows Server VMs, with no Software Assurance. Using the reported L1 host price and the listed Windows Server subscription price, the arithmetic looks like this:
| Item | Calculation | Per month |
|---|---|---|
| Azure Local host fee (L1, reported) | 32 cores × $10 | $320 |
| Windows Server subscription | 32 cores × $23.30 | $745.60 |
| Total | $1,065.60 (about $12,800 per year) |
With Windows Server Datacenter and active Software Assurance on those cores, Azure Hybrid Benefit would waive both lines for L1. Compare the result against the licensing, Software Assurance and support cost of an equivalent Windows Server Datacenter design over your planned hardware life. Enterprise agreement discounts change the picture considerably, so treat this as a method, not a quote.
Clustering and high availability
Both products use Windows Server Failover Clustering, Hyper-V live migration and the same restart-on-failure model. The differences are in the supported topologies and how much is prescribed.
| Topic | Azure Local | Windows Server Hyper-V |
|---|---|---|
| Cluster sizes | Hyperconverged: 1 to 16 machines. Disaggregated (SAN): 1 to 64 machines | Failover clusters of up to 64 nodes; single hosts also common |
| Single machine | Supported | Standalone host, not a cluster |
| Two-machine clusters | Supported. Connected two-machine clusters require a cloud witness created during deployment | Supported with the witness type you choose (disk, file share or cloud) |
| Rack or room resilience | Rack aware clustering, generally available since release 2601, spreads one cluster across two local availability zones. Requires a cloud witness | Stretched or campus designs built with Storage Replica or storage-vendor replication. Check Microsoft’s current guidance for Windows Server 2025 campus designs |
| VM-level replication | Hyper-V Replica (to another Azure Local cluster) and Azure Site Recovery (to Azure) | Hyper-V Replica and Azure Site Recovery |
| Fully disconnected | Disconnected operations (L3) with a local control plane, generally available since release 2602 | Windows Server runs offline natively |
| Cluster design freedom | Prescriptive: validated hardware, Azure-orchestrated deployment | Flexible: you design hosts, networks, witness and storage |
Storage
Azure Local
Azure Local’s default storage design is Storage Spaces Direct (S2D), pooling local drives across machines. Two newer options changed the picture in 2026:
- External SAN storage. Microsoft’s What’s New lists SAN support as generally available, including Fibre Channel and iSCSI, for hyperconverged deployments with external storage and for disaggregated deployments. Reports place Fibre Channel GA at release 2604 and iSCSI GA at 2607, so verify against your release.
- Disaggregated deployments separate compute from SAN storage and scale from 1 to 64 machines.
Rack aware clusters, by contrast, do not support external SAN storage in the generally available design (a SAN variant is listed as preview).
Windows Server Hyper-V
Windows Server gives you the widest range of choices: Storage Spaces Direct (Datacenter edition), shared SAN storage with Cluster Shared Volumes over Fibre Channel, iSCSI or SAS, SMB 3 file shares including Scale-Out File Server, and local disks on standalone hosts.
| Storage feature | Azure Local | Windows Server 2025 |
|---|---|---|
| Storage Spaces Direct | Yes (default) | Yes (Datacenter edition) |
| S2D thin provisioning | Yes | Yes |
| ReFS deduplication | Yes | Yes |
| External SAN | Yes, in supported deployment types (GA, check release) | Yes, long-standing |
| SMB / file-share-backed VMs | Not a standard path | Yes |
| Mixed storage designs | Constrained by deployment type | Free choice |
Networking
Under the hood both use the Hyper-V virtual switch, Switch Embedded Teaming and RDMA for storage traffic. The practical difference is how opinionated the deployment is.
| Topic | Azure Local | Windows Server Hyper-V |
|---|---|---|
| Host network configuration | Intent-based with Network ATC as part of the deployment workflow | Manual design, or Network ATC (available in Windows Server 2025) |
| Reference designs | Documented network patterns, including switched and switchless storage topologies and multi-rack patterns for disaggregated deployments | Your own design, validated against vendor guidance |
| Software-Defined Networking | Supported | Supported |
| Storage network | RDMA-based design is prescribed for S2D clusters. Dedicated storage fabric for SAN designs | RDMA optional but recommended for S2D |
| Cross-site requirements | Rack aware needs a dedicated storage network and validated latency between zones | Defined by your replication or stretch design |
Azure integration: Arc, Monitor, Backup and Site Recovery
Both products can connect to Azure, but Azure Local is built around it while Windows Server treats it as an add-on.
| Azure service | Azure Local | Windows Server Hyper-V |
|---|---|---|
| Azure Arc | Registration is part of deployment. The cluster is an Azure resource, and VMs are managed through Azure Local VMs enabled by Arc, with Azure portal, CLI and ARM templates | Install the Azure Connected Machine agent on each host. Hosts become Arc-enabled servers, with extensions, policy and Defender for Cloud. Hyper-V VMs are not Arc VMs by default |
| Azure Monitor | Monitoring, insights, logs, alerts and workbooks, with multi-cluster monitoring in the portal and native alerts | Supported through the Arc agent and Azure Monitor. Alerts are configured through Windows Admin Center |
| Azure Backup | Microsoft Azure Backup Server (MABS) protects Azure Local VMs at host level or guest level, plus host system state | MABS protects Hyper-V VMs too. Check the MABS protection matrix for supported Windows Server host versions |
| Azure Site Recovery | Hyper-V Replica between Azure Local clusters is supported. Azure Site Recovery integration with Azure Local to Azure is listed as preview | Hyper-V to Azure is supported through the Site Recovery provider and MARS agent. Windows Server 2025 hosts are in the support matrix |
| Azure Update Manager | Included | Free for Windows Server 2025 with Azure Hybrid Benefit |
| Host hotpatching | Not available | Windows Server 2025 via Azure Arc |
| AKS and AVD | AKS built in. Azure Virtual Desktop supported on-premises | AKS on Windows Server is being retired in stages between March 2026 and March 2028, so plan accordingly |
Management and lifecycle
| Topic | Azure Local | Windows Server Hyper-V |
|---|---|---|
| Preferred host management | Azure portal | Windows Admin Center |
| Preferred VM management | Azure portal through Azure Arc | Windows Admin Center, Hyper-V Manager, PowerShell, or Arc |
| On-premises tools | Windows Admin Center, PowerShell | Windows Admin Center, PowerShell, Server Manager |
| System Center | Supported (sold separately) | Supported (sold separately) |
| Driver and firmware updates | Integrated on Integrated Systems and Premier Solutions | Your own process or vendor tooling |
| Update cadence | Regular releases. Plan to stay within six months | Monthly patching on a long-term servicing branch |
| Restarts | Kernel-only restarts, up to 10x faster restarts per Microsoft | Standard restarts. Hotpatching available through Arc |
| Desktop experience | No | Yes |
Which workloads and scenarios suit each
| Scenario | Better fit | Why |
|---|---|---|
| Many branch or edge sites with 1 to 4 machines | Azure Local | Single or two-machine clusters, central Azure management and consistent updates |
| Core datacenter virtualization with existing SAN and mixed hardware | Windows Server Hyper-V (or Azure Local with SAN if hardware is on the catalog) | Hardware and storage freedom. Azure Local SAN designs sit in a higher pricing tier |
| Host also runs file, DNS, DHCP or other roles | Windows Server | Azure Local does not host roles directly |
| On-premises Azure Virtual Desktop or built-in Kubernetes | Azure Local | AKS is included. AKS on Windows Server is being retired |
| Sovereign or air-gapped environments | Windows Server, or Azure Local disconnected operations | Windows Server is simplest offline. Disconnected operations (L3) offers a local Azure control plane at a custom price |
| Sites with unreliable or limited connectivity | Windows Server | Azure Local connected deployments must reach Azure at least every 30 days |
| Dev, test and labs | Windows Server | Easy to run nested and without catalog hardware. Azure Local as a guest is for evaluation only |
| VMware exit | Either, depending on goals | Azure Migrate is the documented method for VMware to Azure Local. System Center VMM and VM conversion are listed for Windows Server |
| Organizations with Datacenter + Software Assurance and Azure Arc plans | Evaluate Azure Local L1 | Azure Hybrid Benefit can waive host and guest subscription fees |
| Strict hardware standardization already in place | Either | Azure Local matches validated-hardware discipline, but Windows Server works with any certified vendor |
Where they overlap
It is easy to overstate the differences. Microsoft’s own comparison shows the technical feature sets overlap heavily:
- Same hypervisor and clustering: Hyper-V, Windows Server Failover Clustering and live migration.
- Shared storage and resilience features: Storage Spaces Direct, thin provisioning, ReFS deduplication and Cluster-Aware OS feature updates.
- Shared security and VM features: Secured-core server, dynamic processor compatibility mode and Hyper-V high availability for GPU workloads with GPU partitioning.
- Shared networking tools: Network ATC and Software-Defined Networking.
- Shared management tools: Windows Admin Center, PowerShell, System Center and third-party tools.
- Shared Azure reach: both support Azure Arc management, Azure Backup and Azure Site Recovery in some form.
The Azure Local OS is not a Windows Server edition and not a Windows Server role. Think of it as a dedicated host image that bundles the infrastructure features and drops the general-purpose roles.
Decision guide
Work through these questions in order. The first clear “yes” usually decides the direction.
- Do you need to run server roles directly on the host, or keep hosts as a general-purpose Windows Server? If yes, use Windows Server with Hyper-V.
- Can every site reach Azure at least every 30 days, or do you need an Azure-style local control plane? If no, and you do not want disconnected operations, use Windows Server.
- Do you need hardware flexibility beyond the Azure Local Catalog, or specific storage such as SMB or an unsupported SAN? If yes, use Windows Server.
- Do you want Azure-native VM management, built-in AKS or AVD, and a managed update stream across many sites? If yes, shortlist Azure Local.
- Model the licensing. Compare Azure Local (tier, guest licensing, Azure Hybrid Benefit eligibility) against Windows Server licensing over the hardware life.
- Pilot before committing. Deploy a small Azure Local instance on validated hardware, or the evaluation image in a lab, and test your backup, DR and monitoring workflow.
More guides on Windows Server, Hyper-V, Azure and hybrid infrastructure are on VMoreCloud.
Frequently asked questions
Is Azure Stack HCI the same as Azure Local?
Yes. Microsoft renamed Azure Stack HCI to Azure Local, effective November 19, 2024. Clusters are now called Azure Local instances and servers are called Azure Local machines. The Microsoft.AzureStackHCI resource provider name stays the same.
Does Azure Local use Hyper-V?
Yes. Azure Local uses the Hyper-V hypervisor, Windows Server Failover Clustering and Storage Spaces Direct, packaged in a purpose-built operating system and delivered as an Azure service.
Can Azure Local run without an internet connection?
Connected deployments must connect to Azure at least once every 30 days. For fully on-premises operation, Microsoft offers disconnected operations with a locally hosted control plane, priced through your account representative.
Do I still need Windows Server licenses on Azure Local?
You need guest licensing for Windows Server VMs. Options are the Windows Server subscription, Azure Hybrid Benefit (for eligible L1 deployments with Datacenter and Software Assurance) or bring your own license. The host fee does not include guest rights.
Can I run Active Directory, file services or other roles directly on an Azure Local host?
No. Run workloads inside VMs or containers. Azure Local is not licensed for clients to connect directly to the host with CALs.
Do I need Azure Local to use Azure Arc?
No. Windows Server hosts can be Arc-enabled with the Azure Connected Machine agent to gain extensions, policy, monitoring and update management. Azure Local adds Azure-native VM management and cluster integration.
Sources and further reading
- Microsoft Learn: Compare Azure Local to Windows Server
- Microsoft Learn: Renaming Azure Stack HCI to Azure Local
- Microsoft Azure: Azure Local pricing
- Microsoft Learn: OEM license and billing FAQ for Azure Local
- Microsoft Learn: What’s new in Azure Local
- Microsoft Learn: Architecture best practices for Azure Local
- Microsoft Learn: Disconnected operations for Azure Local
- Microsoft Learn: Virtual machine resiliency for Azure Local
- Microsoft Learn: Hyper-V to Azure disaster recovery support matrix
- Microsoft Learn: MABS protection matrix
- Cristian Schmitt Nieto: Azure Local evolution, use cases and comparison (community analysis)
This guide is based on Microsoft documentation and pricing pages available on October 27, 2026, plus clearly labelled community analysis. Prices, tiers, supported configurations and preview status change often. Price figures marked “reported” come from secondary sources, so confirm them in the Azure pricing calculator and with your Microsoft representative before making purchasing decisions.
