Azure Local for Small Sites: What It Is, How It Is Licensed, and When It Beats Plain Azure VMs or Hyper-V

Microsoft's overview (November 2025) calls Azure Local "Microsoft's distributed infrastructure solution that extends Azure capabilities to customer-owned environments," using "Azure Arc as the unifying control plane" and supporting "deployments that are connected or disconnected from the cloud." It is the product formerly sold as Azure Stack HCI.

On the hardware it is a hyperconverged cluster: Hyper-V, Storage Spaces Direct and software-defined networking, deployed and updated from Azure. Virtual machines are Azure Arc resources; Microsoft's Arc VM management page (July 2026) describes creating, updating and deleting VMs, disks, logical networks and images from the Azure portal or CLI through an Arc resource bridge and a custom location. Management is "via Azure portal, Azure CLI, and ARM templates": one portal, one RBAC model, one bill.

Pricing is "per physical core on your on-premises machines, plus any consumption-based charges for additional Azure services you use. All charges roll up to your existing Azure subscription."

Microsoft's system requirements page (September 2026) sets the rules; these are limits, not recommendations.

• Machines: "1 to 64 machines are supported," and every machine must be "the same model, manufacturer, have the same processor types, have the same network adapters, and have the same number and type of storage drives." The deployment guide (November 2025) describes portal patterns for one to 16 machines, including one or two machines without a storage switch.
• Support: "Microsoft Support may only be provided for Azure Local running on hardware listed in the Azure Local catalog."
• Per machine: a 64-bit Intel Nehalem-grade or AMD EPYC or later processor, "a minimum of 32-GB RAM per machine with Error-Correcting Code (ECC)," TPM 2.0 and Secure Boot turned on, a boot drive of at least 200 GB, and at least two data drives of 500 GB or more. Storage Spaces Direct is required even on a single node.
• Network: a high-bandwidth, low-latency link between machines and "connectivity to public endpoints in Azure," at a minimum of 10 Mbit.
• Identity: deployment starts with preparing Active Directory, so a site with no domain controller needs one first.

For a branch that means two catalog servers, typically 16 cores and 128 GB or more each, four to six NVMe drives, two 25 Gb ports cabled directly between them, and a reachable domain controller: a two-node switchless cluster.

Three charges make up the licensing. Microsoft documents all three without numbers we can reprint, so we describe the model and send you to the Azure pricing page for the rate.

The host fee. Azure Local is "priced per core on your on-premises servers," billed "per physical processor core in an Azure Local instance," and appears "on your Azure subscription bill just like any other Azure service" (billing page, June 2026). The cluster "must connect to Azure at least once every 30 days to allow for billing."

Windows Server inside the VMs. Microsoft's activation page (June 2026) gives three options: the Windows Server subscription add-on, "per physical core/per month pricing, purchased and billed through Azure," with "no CAL required"; Automatic Virtual Machine Activation with Datacenter keys you own; or generic AVMA keys with the subscription enabled. Windows Server 2025 licensing covers the Datacenter route and its CALs.

Azure Hybrid Benefit for Azure Local. With Windows Server Datacenter licenses under active Software Assurance you can "exchange a 1-core license of Software Assurance-enabled Windows Server Datacenter for 1-physical core of Azure Local," and "this benefit waives the Azure Local host service fee and Windows Server guest subscription" (June 2026). Azure Hybrid Benefit explained covers the proof and the CSP route.

Then the consumption line: Azure Monitor, Update Manager, Defender for Cloud, Backup and Site Recovery are metered separately, as they are for servers you keep and onboard to Arc. Those meters are the customer's.

The pattern that justifies it is a site that cannot depend on the WAN: a distribution center whose warehouse system must keep scanning when the circuit drops, a plant with a historian that needs single-digit millisecond latency, a retailer with a store server per location and a headquarters that wants all of them updated from one portal.

In each case Azure VMs fail on latency or on the outage case, and standalone Hyper-V fails on management: forty stores, forty consoles. Azure Local gives the site compute and storage that keep running on their own, with updates, monitoring, policy and VM lifecycle from the same portal as everything else.

It is also the on-premises exit for VMware customers who want to keep a cluster, covered in leaving VMware after the Broadcom changes.

Plain Azure VMs win when the workload does not need to be in the building. A file server that becomes Azure Files, an application server, a domain controller: moving the last on-premises servers to Azure walks through that trio. No hardware to buy or refresh, no catalog to match, no cluster to patch, and reservations and savings plans cut the compute line for steady workloads. The bill is consumption; the failure mode is the WAN.

Hyper-V on Windows Server 2025 wins when you already own Datacenter licenses without Software Assurance, or Standard licenses, and want no monthly host fee and no Azure dependency. Datacenter's unlimited virtualization rights still apply; the Windows Server calculator works out the core count.

Azure Local wins when you need local continuity and central management at the same time, especially with Datacenter plus SA in hand, because Azure Hybrid Benefit turns the host fee off. Without SA, the per-core fee is the price of the Azure control plane, and for one site with steady workloads it often buys less than it costs.

Timing matters more than any of this: if the hosts are due for replacement, switch now; if they are two years old, wait for the refresh.

Take a manufacturing site with twelve VMs: a domain controller, a file server, an ERP application server, a SQL Server, a historian, a print server, two line-of-business apps, a monitoring box, a jump host and two test machines, about 40 vCPU, 300 GB of memory and 6 TB of storage.

Hardware: two catalog nodes with 16 cores and 256 GB each and six 1.92 TB NVMe drives per node, switchless: 32 physical cores and roughly 5.7 TB usable with two-way mirroring.

Licensing, as cost drivers: 32 physical cores of host fee per month, or none with 32 Datacenter cores under Software Assurance. Windows Server for twelve guests through the subscription add-on on the same 32 cores, or through the same Datacenter licenses with AVMA. SQL Server is licensed separately either way; the SQL licensing calculator covers it.

The same twelve VMs in Azure: twelve reserved VMs, premium disks, a VPN gateway, egress, no hardware. Costs less when the site tolerates a WAN outage; costs more once the historian and SQL need local latency and the file server serves 200 GB a day to the floor.

The same twelve on Hyper-V 2025: the same two nodes, 32 Datacenter cores at purchase, no monthly host fee, Windows Admin Center and Arc for management. Lowest on paper over five years for one site; the gap closes at three or more sites.

Timeline: two weeks of design and hardware order, four to eight weeks of lead time, a week of network and Active Directory preparation, two days of deployment, one to two weeks of VM migration; our Azure Local design and deployment engagement runs six weeks around the hardware lead time.

Does Azure Local work without internet?

Microsoft describes support for "deployments that are connected or disconnected from the cloud." A standard connected deployment must reach Azure at least once every 30 days for billing; verify disconnected-operations requirements on Microsoft Learn.

Do I need Windows Server licenses for VMs on Azure Local?

Yes, one way or another: the Windows Server subscription add-on billed per physical core through Azure, Datacenter licenses you own with Automatic Virtual Machine Activation, or Datacenter with Software Assurance through Azure Hybrid Benefit, which also waives the host fee.

Can I run Azure Local on one server?

Yes. Single-machine deployments are supported, with or without a switch, and Storage Spaces Direct is still required. There is no host redundancy, so treat it as an edge appliance with a backup plan.

Is Azure Local cheaper than Hyper-V?

Not for a single site with owned licenses and no Software Assurance; the per-core host fee is a new monthly line. With Datacenter plus SA the host fee is waived and the two converge, and at several sites the central management usually decides it.

• Microsoft Learn source files on GitHub (MicrosoftDocs/azure-stack-docs), opened 2026-09-27: "What is Azure Local?", ms.date 11/18/2025; "System requirements for Azure Local", 09/04/2026; "About Azure Local deployment", 11/19/2025; "Azure Local billing and payment", 06/25/2026; "Azure Hybrid Benefit for Azure Local", 06/25/2026; "Activate Windows Server VMs on Azure Local", 06/29/2026; "What is Azure Arc VM management on Azure Local?", 07/23/2026
• IT Partner blog articles and service and tool pages linked above; IT Partner engineering notes from Azure Local and Hyper-V cluster projects, September 2026
• No Azure Local, Windows Server subscription or Azure VM prices are printed; they are not on the September 2026 price list we publish from.