Closed beta General availability Q1 2027. Request beta access →
IZT Cloud CLOUD FABRIC
See pricing Start free
Comparison

Fabric vs Azure Local

Azure Local is Microsoft’s HCI, billed per core per month through an Azure subscription and designed to stay connected to it. Hyper-V on Windows Server is the on-prem classic. Fabric is for the sites that must run whether or not the cloud does.

Comparing Fabric with Microsoft Hyper-V and Azure Local (formerly Azure Stack HCI) (Microsoft). Updated 2026-09-03. Fabric is in closed beta today. General availability is planned for Q1 2027. Competitor facts are drawn from public documentation and published or verified pricing; corrections welcome.

The short version
  • Azure Local bills per physical core per month via Azure and must sync with Azure regularly; Fabric is per node per year and needs no connection at all.
  • Azure Local runs only on validated hardware from the Azure Local catalog; Fabric runs on commodity servers.
  • Microsoft wins for Windows-centric estates and Azure hybrid services; Fabric wins for sovereignty, mixed Linux/Windows fleets and edge sites without an Azure relationship.
Pricing at a glance

One dual-socket server, 32 physical cores, fully loaded with VMs (annual, list unless noted)

Fabric — Medium class
$1,800/ node / yr

Fabric Medium class: $1,800 per node per year including the whole platform; guest OS licensing is unchanged either way.

Azure Local
Per-core monthly Azure billing plus guest licences

Model: Azure Local: per physical core per month, billed through an Azure subscription, plus Windows Server guest licensing. Hyper-V: included with Windows Server Datacenter, per core with a 16-core minimum per server.

Basis: Microsoft publishes regional per-core rates; totals depend on Azure agreement and guest OS licensing, 2026.

Dimension by dimension

Fabric vs Azure Local, honestly scored.

Where Azure Local is ahead we say so. Roadmap items are labelled and count against Fabric until they ship.

7 Fabric 3 Azure Local 3 Even 13 dimensions · roadmap items count against Fabric until they ship
Fabric compared with Azure Local, dimension by dimension
DimensionFabricAzure LocalEdge
Licensing model Per physical node by node class (five core bands: ≤8 / 9–16 / 17–32 / 33–64 / 65+), every feature in every class, free unlimited Community edition. No per-core meter, no feature matrix.Azure Local: per core per month through Azure. Windows Server Datacenter: per core, 16-core minimum, for unlimited Hyper-V guests.Fabric
Cloud dependency None. No registration, no sync, no kill-switch.Azure Local must register with Azure and sync at least every 30 days to stay in a supported, billable state.Fabric
What you install One signed firmware image per node plus a control-plane appliance.Azure Local OS on validated nodes, managed through Azure Arc and the Azure portal; or Windows Server with Hyper-V, Failover Clustering and System Center / Windows Admin Center.Fabric
Storage Distributed block storage pooled across every node, driven by storage policies: ordered device tiers, copies and minimum copies, host- or rack-level failure domains, per-disk IOPS/bandwidth QoS and inline compression with in-place re-pack. No SAN and no storage licence.Storage Spaces Direct: mirror or parity resiliency, tiering, deduplication — solid, and tied to validated hardware.Even
Networking Per-tenant SDN in the platform: overlay or VLAN-backed virtual networks, dual-stack IPv4/IPv6, built-in DHCP/DNS, micro-segmentation policies, distributed stateless gateways and ARP or BGP announcement of public prefixes. Not a separate SDN licence.Network ATC and optional SDN (Network Controller, gateways) — capable but complex to deploy.Fabric
High availability Acknowledged 10-second heartbeats, a liveness verdict in about 20 seconds, and no restart elsewhere until the failed node is verifiably fenced — powered off through its own BMC and blocked at the storage layer.Failover Clustering with quorum witnesses — mature and well understood.Even
Live migration Live migration; hibernate and resume on any node.Hyper-V live migration and storage migration.Even
Updates and lifecycle One signed A/B firmware image per node carries the hypervisor, storage, networking and agent. A rolling update evacuates each node by live migration, flips its image slot and rolls back automatically if it does not come up healthy.Cluster-Aware Updating; Azure Local lifecycle via Azure Update Manager. Monthly Windows patching cadence.Fabric
Multitenancy Built in. Tenants, quotas, isolated per-tenant networks with their own DHCP/DNS, and a tenant self-service portal with browser consoles — the same product an MSP bills monthly per node.Azure RBAC over Arc-enabled resources; no tenant self-service portal on-prem.Fabric
Snapshots and DRRoadmap Snapshots and cross-site replication are on the roadmap.Checkpoints, Hyper-V Replica and Azure Site Recovery integration.Azure Local
Hardware Commodity x86-64, any drive mix, no restrictive compatibility list.Azure Local requires validated systems from the catalog; Hyper-V is broader.Fabric
Windows guest economics Guest licensing is your existing Microsoft agreement; no advantage or penalty.Datacenter edition covers unlimited Windows guests; Azure Hybrid Benefit and AVMA can be compelling for Windows-only estates.Azure Local
Ecosystem New platform; REST API, Prometheus metrics.Deep Microsoft tooling, Azure hybrid services (Arc, Backup, Site Recovery, Monitor).Azure Local
Who should pick which

Choose Fabric if… Choose Azure Local if…

Fabric is the better fit for

  • Air-gapped, sovereign or regulated sites that cannot register with a public cloud
  • Mixed Linux/Windows estates on commodity hardware
  • Edge sites with no Azure agreement or unreliable connectivity
  • Buyers who want one predictable annual bill per node

Azure Local is the better fit for

  • Windows-only estates that already own Datacenter licences
  • Organisations committed to Azure hybrid services
  • Teams standardised on Microsoft tooling

Moving from Azure Local to Fabric

Hyper-V VHDX disks convert to standard images and import into Fabric as volumes; Windows guests keep their existing licences. Sites often start with Fabric at the edge where Azure connectivity is weakest.

See migration use cases
FAQ

Fabric vs Azure Local: common questions

Azure Local is designed to stay registered with Azure and must sync periodically; extended disconnection is a special case. Fabric never needs a connection.

More comparisons

How Fabric stacks up against the rest.

Fabric vs VMware VMware vSphere and VMware Cloud Foundation (VCF)Fabric vs Proxmox Proxmox Virtual Environment (Proxmox VE)Fabric vs Nutanix Nutanix Cloud Infrastructure (NCI) with the AHV hypervisorFabric vs Scale Computing Scale Computing SC//Platform (HyperCore)Fabric vs VergeIO VergeOS by VergeIOFabric vs Harvester Harvester HCI (SUSE Virtualization)Fabric vs XCP-ng XCP-ng with Xen Orchestra (Vates) All comparisons → Methodology and the full list

Try the whole platform free.

Community is unlimited nodes, every feature, forever. Move to a paid class when you want the production update channel and a support contract.