Azure Local
This guide to Azure Local covers pricing, competitive trade-offs, and deployment realities.
Table of Contents
Azure Local Overview
Azure Local puts Azure services on servers you own and operate. Microsoft's product page tells you that much. What it doesn't cover is how the per-core subscription holds up once you factor in hardware, networking, licensing add-ons, and the work of managing hybrid workloads at scale.
Does the math still work once you add it all up?
For teams with existing Windows Server Software Assurance, the answer is usually yes. For everyone else, it depends on three cost layers that the pricing page doesn't break down. This guide walks through each one, along with the competitive trade-offs and deployment realities that shape the decision.
What is Azure Local?
Azure Local is Microsoft's hyper-converged infrastructure software for running Azure services on validated servers in your datacenter or edge site. It combines Hyper-V compute, Storage Spaces Direct, and high-speed networking into a single cluster, then runs virtual machines, Azure Kubernetes Service (AKS) containers, and Azure Virtual Desktop on top.
Once you register the cluster with Azure Arc, you can monitor, secure, and patch it from the same Azure portal you already use. Sensitive data stays on-prem for compliance, data-residency, or low-latency scenarios.
What changed from Azure Stack HCI?
Three things changed when Microsoft rebranded Azure Stack HCI to Azure Local in late 2024. The minimum cluster size dropped from two nodes to one. The on-prem service catalog expanded to include AKS and Azure Virtual Desktop session hosts. And the billing model shifted to a pay-as-you-go Azure subscription at $10 per physical core per month.
For a detailed breakdown of how Azure Local differs from Azure Stack Hub, see the FAQ at the end of this article.
| Capability | Azure Local (2025) | Azure Stack HCI (pre-2024) | Standalone Hyper-V |
|---|---|---|---|
| Azure subscription billing | Per core, pay-as-you-go | Yes (per core) | No |
| Azure portal + Azure Arc management | Built-in | Limited | None |
| Supported services on-prem | VMs, AKS, AVD | VMs, AKS (preview) | VMs only |
| Cluster size | 1 to 16 nodes | 2 to 16 nodes | N/A (single host or SCVMM) |
| Disconnected mode | Yes | Limited | N/A |
The single-node option and expanded service catalog are the two changes that matter most for edge and branch deployments.
How much does Azure Local cost?
The base price is $10 per physical core per month after a 60-day free trial. But the total cost depends on three layers that stack on top of that base fee. Your finance team sees $10/core and approves the project. Then the Windows Server guest add-on doubles the number.
Base host fee. $10/core/month covers the Azure Local OS, Azure Arc management, and cluster services. If you already hold Windows Server licenses with Software Assurance (SA), Azure Hybrid Benefit waives this fee entirely.
Windows Server guest rights. Running Windows VMs requires an optional add-on at $23.30 per core per month for unlimited guest VMs. Azure Hybrid Benefit also waives this charge for qualified licenses. That drops your per-core cost to $0.
Network and egress. ExpressRoute Local circuits bundle all inbound and outbound transfer into the port price. That eliminates per-GB egress fees. Standard or Premium circuits charge egress separately.
| Cost component | Azure Local (on-prem) | Azure pay-as-you-go VM | VMware vSphere / VCF |
|---|---|---|---|
| Base host fee | $10/core/month (waivable with AHB) | None (per VM hour) | Per-core license + SnS contract |
| Windows Server guests | $23.30/core/month (waivable with AHB) | Included in VM rate | Separate Datacenter licenses |
| Cloud management | Included via Azure Arc | Native | vCenter + add-ons (vSAN, NSX) |
| Data egress | None on ExpressRoute Local | Per GB | N/A |
| Hardware | Customer-owned, validated servers | None (Azure hardware) | Customer-owned servers |
Azure Local consolidates hypervisor, storage, and management into one per-core subscription. For teams with existing SA, the subscription cost can drop to zero. For teams without SA, compare the three cost layers above to your current VMware renewal or cloud VM spend before committing.
The AVD total cost calculator is a useful starting point for virtual desktop workloads.
How can you reduce Azure Local costs?
Three options beyond the base subscription can lower your bill:
- Right-size core counts. Billing tracks physical cores, so scaling from 32 to 24 cores per node trims the monthly host fee by 25% with no effect on RAM-heavy workloads.
- Free AKS on-prem. AKS on Azure Local (release 2402+) carries no additional control-plane charge. Container clusters cost only the host cores you already pay for.
- Reserved instances for burst. When you burst VMs into an Azure region, pair with 1- or 3-year reserved VM instances to lock in lower compute rates.
Each lever targets a different piece of the cost stack. Right-sizing reduces the base host fee, free AKS avoids new charges, and reserved instances cut your cloud burst bill.
How does Azure Local compare to VMware, AWS Outposts, and Google?
Azure Local is the only option where you own the hardware, manage everything through Azure, and can operate fully offline. AWS Outposts and Google Distributed Cloud take different approaches to the same problem. The key differences are hardware ownership, offline capability, and which cloud services run locally.
| Capability | Azure Local | AWS Outposts | Google Distributed Cloud |
|---|---|---|---|
| Hardware ownership | Customer-owned, partner-validated (1 to 16 nodes) | AWS-owned racks or servers delivered as a service | Google-owned racks (Connected) or customer hardware (Software Only) |
| Management plane | Azure portal via Azure Arc | AWS Console via Region | Google Cloud Console |
| Local services | VMs, AKS, Azure Virtual Desktop | EC2, EBS, RDS, EKS (subset) | GKE, Anthos, AI accelerators |
| Offline / air-gapped | Yes (disconnected mode) | No (requires AWS link) | Yes (GDC Air-gapped) |
| Billing | Per physical core, monthly Azure invoice | Capacity-based rack/server rental | Subscription or hardware purchase |
Choose Azure Local when you want customer-owned hardware with cloud-based management and optional offline operation. The single-vendor stack for OS, hypervisor, and cloud services eliminates separate vSAN and NSX renewals for teams migrating from VMware.
Outposts fits better when you prefer vendor-managed hardware and tight service parity with AWS regions.
Google Distributed Cloud stands out for air-gapped deployments that need Google Kubernetes Engine and AI services on-prem.
For VMware-specific migration scenarios, Azure Local rolls virtualization, storage, and management into one Azure subscription. Your team reuses existing Windows Server skills and manages clusters in the Azure portal instead of juggling separate vCenter, vSAN, and NSX consoles.
What does an Azure Local deployment require?
You need validated hardware, a network topology, Active Directory, and an Azure subscription. Here's what to verify before imaging the first node.
Hardware. Choose servers from Microsoft's validated catalog. TPM 2.0 and Secure Boot are required. All-flash NVMe or SSD drives power Storage Spaces Direct. Optional GPUs support AI workloads with up to 192 GB memory per host. Clusters start at a single node for edge closets and scale to 16 nodes for core datacenter or virtual desktop farms.
Network. Pick a reference topology: switchless direct connections for 2-node remote sites, dual top-of-rack switches for most production clusters (3 to 16 nodes), or spine-leaf for large multi-rack deployments. Reserve RDMA-capable (Remote Direct Memory Access) 25 to 100 GbE links and allocate 1 to 2% of bandwidth for system heartbeats.
Identity and DNS. You need an Active Directory domain, DNS records for each host, and a service account with "Create Computer Objects" permissions.
Azure subscription. Contributor-level rights to register the cluster. The first 60 days are free, then billing starts at $10 per physical core per month.
What are the steps to deploy Azure Local?
Once prerequisites are in place, the deployment sequence is:
- Cable and power nodes according to the selected network topology.
- Install the Azure Local OS from the latest ISO or using Windows Admin Center.
- Create the cluster in Windows Admin Center or PowerShell.
- Register with Azure, which starts Arc governance and the 60-day trial.
- Run Cluster-Aware Updating for the latest cumulative patches.
- Enable services like AKS or Azure Virtual Desktop through Arc.
- Configure backup and disaster recovery using Azure Backup Server and Azure Site Recovery.
For a deeper look at VM sizing and host pool architecture, Nerdio's resource library covers the planning details.
Optimize and save
See how you can optimize processes, improve security, increase reliability, and save up to 70% on Microsoft Azure costs.
Which workloads run best on Azure Local?
Edge computing, regulated industries, distributed retail, and VMware migration are the four scenarios where Azure Local delivers the clearest value.
Edge and branch operations. Run real-time analytics or AI inference next to machines and IoT sensors instead of sending data on a round trip to the cloud. A single-node appliance fits a retail store closet; a 16-node cluster powers a regional manufacturing hub. CDW, an early Azure Local adopter, deployed the platform to consolidate hybrid infrastructure and saw SQL performance nearly double compared with its previous environment.
Regulated industries with data-residency requirements. Disconnected mode keeps workloads entirely on-prem to meet sovereignty or classified-network rules. When connectivity is allowed, Azure Arc applies policy and collects logs without copying customer data to the public cloud.
Retail and manufacturing at scale. Drop-in clusters at each store or plant deliver uniform point-of-sale, analytics, or manufacturing execution stacks. Central IT manages hundreds of sites through Azure Monitor and GitOps instead of dispatching engineers to each location.
VMware migration. Consolidate hypervisor, storage, and network licensing into one per-core Azure charge. Reuse existing Windows Server skills. The hybrid AVD deployment model lets you run Azure Virtual Desktop session hosts on Azure Local hardware while maintaining cloud-based management.
These four scenarios share one thing: workloads that need to stay close to the data or the user but still benefit from Azure-based governance and tooling.
How does Nerdio Manager simplify Azure Local management?
Nerdio Manager for Enterprise gives you a single console to automate provisioning, scaling, and lifecycle management for Azure Local workloads. It plugs into Azure Arc and the Azure Local resource bridge to manage Cloud PCs through Microsoft Intune and Azure Virtual Desktop session hosts.
Windows Cloud (the umbrella covering both Windows 365 and Azure Virtual Desktop) increasingly runs on hybrid infrastructure. Most enterprises operate both desktop types, and Nerdio Manager handles them from the same console.
On the Windows 365 side, Unified Application Management deploys apps in roughly 30 seconds versus native Intune's typical 3-hour window. Nerdio Advisor right-sizes Cloud PC licenses based on actual utilization data.
On the AVD side, Nerdio Manager creates host pools on Azure Local clusters in minutes and wires up FSLogix profiles automatically. Patented auto-scaling powers down unused VMs during off-peak hours.
What cost and license visibility does Nerdio add?
Nerdio Manager dashboards surface idle hosts and per-user cost so you can right-size core counts and reclaim under-used nodes. License alignment reports show where Azure Hybrid Benefit can eliminate the monthly per-core host fee.
| Task | Native tools | With Nerdio Manager |
|---|---|---|
| Create AVD host pool | PowerShell + JSON templates | Guided wizard, roughly 5 minutes |
| Scale hosts on demand | Manual sizing or custom script | Auto-scale engine (CPU, RAM, schedule) |
| Image management | Azure portal + CLI | Central image gallery with versioning |
| Cost visibility | Azure Cost Management (cloud only) | Per-user cost dashboards across cloud and on-prem |
With automation handling provisioning and scaling, your team focuses on running the business instead of managing the platform.
Schedule a demo to see how Nerdio Manager handles your Azure Local environment.
Take Windows to the Cloud with Microsoft and Nerdio
Join us for a webinar to discover how to take Windows to the cloud. Get insights from industry leaders on navigating the modern workspace and driving secure, cloud-powered operations.
Frequently asked questions about Azure Local
Learn more about Azure Local
About the author
