Azure Local vs Nutanix
We compare Azure Local and Nutanix against the workloads that need to stay local, the licences you already hold and the way your team runs infrastructure. We then design, migrate and manage the selected platform, with hardware, recovery and the cost of change accounted for before purchase.
- 01 Workload profile Utilisation, latency and growth
- 02 Dependency complexity Applications, identity and connectivity
- 03 Operational fit Skills, management and lifecycle
- 04 Commercial fit Licences, hardware and ongoing cost
- 05 Cloud suitability What still needs to run locally
- 06 Migration risk Compatibility, cutover and rollback
Two platforms, different ways to run the environment
Azure Local and Nutanix both support local virtualisation, with hyperconverged (HCI) and qualified external-storage configurations. The better fit depends on how your team wants to manage local infrastructure, the licences already in place and the applications the platform has to carry.
Where Azure Local is the stronger candidate
Azure Local makes most sense where local infrastructure has to sit inside an established Azure operating model and eligible Microsoft licences improve the cost case. Its distinction is integration with Azure at the infrastructure level, so the cluster itself is deployed and managed through Azure.
Where Nutanix merits close consideration
Nutanix suits teams that work well with Prism, AHV and the Nutanix lifecycle, particularly when standardising across several sites. Choosing it still means committing to Nutanix software, licensing and lifecycle requirements.
The operating system rarely decides it
Both platforms run supported Windows and Linux workloads. Application certification, database licensing, storage performance and the team's skills carry more weight than a simple Windows-versus-Linux split.
Azure Local and Nutanix AHV, decision by decision
Both names cover several configurations, so we compare the specific deployment, edition and hardware being proposed.
| Decision | Azure Local | Nutanix with AHV |
|---|---|---|
| Platform | Hyper-V virtualisation, with Storage Spaces Direct in a hyperconverged deployment. | AHV virtualisation, with AOS distributed storage in a hyperconverged deployment. |
| Management | Azure Arc integration, Azure portal and Azure Resource Manager, alongside local administration. | Prism Element for a cluster and Prism Central for management across clusters. |
| Hardware and storage | Validated systems and configurations. Qualified external SAN deployments are also available. | Nutanix and approved OEM platforms. NCI Compute supports specific external storage integrations. |
| Commercial model | A monthly Azure Local fee per physical core, plus guest licensing and any eligible Azure Hybrid Benefit. The deployment model matters. | NCI subscription, selected edition and any additional capabilities. AHV is included in NCI; guest licences remain separate. |
| Moving from VMware | Azure Migrate and supported partner methods, checked against the source environment and target release. | Nutanix Move supports ESXi-to-AHV migration, subject to the supported source, guest and target configurations. |
Azure Arc works with both
Azure Arc can also manage supported guest operating systems running on Nutanix, so Azure governance alone isn't a reason to choose Azure Local. Its distinction is that the infrastructure itself is registered and operated through Azure.
AHV, AOS and Prism in practice
AHV is Nutanix's KVM-based hypervisor, included with a Nutanix Cloud Infrastructure (NCI) licence. In a hyperconverged deployment, AOS provides distributed storage and data services, while Prism brings virtual machines, storage and cluster administration together.
Storage performance and usable capacity
A Controller VM on each node runs the storage services. AOS uses local data where possible and distributes copies across the cluster according to the resilience policy. This makes the storage design part of the platform decision: replication, failure tolerance and rebuild capacity affect how much storage is available to applications.
We size for peak demand and operation during a node failure or maintenance window. Controller and management VMs also consume CPU and memory, so the hardware's headline capacity is not the application capacity.
Management across clusters and sites
Prism Element manages an individual cluster. Prism Central provides a shared management view across clusters, including virtual machines, resources and policies. This can make a common operating approach practical across sites that still need local compute.
We account for the management platform's own sizing and availability, local access during a connectivity incident and the skills needed to investigate storage or host faults. The number of consoles is only one part of the operating workload.
Compare the licences you need and the price of changing
Azure Local and Azure Hybrid Benefit
Windows Server Datacenter licences covered by active Software Assurance can materially change the comparison. With the required core coverage and benefit activation, Azure Hybrid Benefit can waive the Azure Local host service fee and the Windows Server guest subscription charge.
That benefit currently applies to qualifying hyperconverged deployments with cloud-connected management and no external storage. It does not apply to every Azure Local architecture. We check the selected deployment, licence allocation and ongoing Software Assurance cost, with other Azure services and application licences priced separately.
Nutanix subscriptions and feature scope
Core-based NCI licensing uses physical CPU capacity. The selected edition and any additional products determine the available capabilities. We price the required replication, security and management features explicitly, including Nutanix Cloud Manager where its additional functions are needed.
AHV and Prism are included with NCI. Windows Server, SQL Server and other application licences still need their own entitlement checks. Azure Hybrid Benefit for the Azure Local platform is not a discount on a local Nutanix cluster.
NCI-Edge for smaller sites
NCI-Edge offers per-VM licensing for qualifying small deployments. The cluster must use the Edge licensing model throughout, with no mix of Edge and core-based NCI licences, and it can't be used as a backup-only or replication-only target.
We check growth against those limits and price any disaster recovery site separately. A site that exceeds the limits needs a different licensing model, which can change the comparison substantially.
nodes per cluster at most
VMs powered on at once
memory per VM
Price both platforms over the same operating period
Include hardware and warranty, platform and guest licences, backup, recovery capacity, monitoring, migration, training and ongoing engineering. Allow for temporary overlap with VMware and for the cost of adding capacity later. A lower software line item may be outweighed by replacement hardware or a more demanding operating model.
Check what can be reused before committing to a platform
Serviceable equipment may have useful life remaining. We check the exact server, processor, NIC, drive, firmware and driver combinations against the selected platform's compatibility requirements, then test the remaining capacity and warranty period against the planned service life.
Retain storage through a supported design
Azure Local supports qualified external SAN deployments using Fibre Channel or iSCSI. We check the array, hardware and software release against the supported configuration. Nutanix NCI Compute has qualified paths for external storage, including Dell PowerFlex, Dell PowerStore and Everpure (formerly Pure Storage) FlashArray. These options can let compute and storage grow separately, but the array, server configuration, network and software versions must form a supported combination.
An existing SAN's useful life can strengthen the reuse case. Changes to storage networking, platform charges and benefit eligibility may offset that value, so we include them before choosing between external storage and a hyperconverged design.
Make the incident path explicit
Nutanix is available on platforms from vendors including Dell, HPE and Lenovo, as well as Nutanix appliances. Azure Local also relies on validated hardware and the corresponding vendor support. The exact product and contract determine who owns the first support call, replacement parts and software escalation.
We agree who investigates a fault, coordinates the hardware and software vendors, and keeps the client informed. Response coverage, renewal dates and exclusions belong in the operating agreement, alongside responsibility for switches, backup and applications.
Plan maintenance and recovery before go-live
Updates need capacity and a supported sequence
Nutanix Life Cycle Manager inventories supported components, checks dependencies and orchestrates software and firmware updates. Its prechecks and rolling upgrade process reduce manual coordination, but the cluster still needs sufficient capacity and a valid upgrade path.
For Azure Local, we work within the supported solution update process and the hardware vendor's validated packages. On either platform, we check cluster health, available capacity, application constraints and the maintenance window before changes begin. Guest operating systems and applications also need their own patching plan.
Recovery must work beyond a node failure
Cluster resilience handles a different failure from a compromised administrator account, deleted data or the loss of a site. We define the recovery time and acceptable data loss for the applications, then design backup and replication around those requirements.
That includes supported backup integration, protected or immutable copies where required, separate recovery access and a tested restore sequence for identity, DNS, databases and applications. We include destination capacity and licences in the recovery design, then test that users can resume work.
Prove the move with representative workloads
We establish the supported route from the current environment before ordering the destination platform. The renewal date, hardware expiry and application change windows set the timetable; the dependency map determines the sequence.
Validate the applications and conversion method
For an ESXi-to-AHV move, we check the Nutanix Move support matrix, guest preparation and required source access. Disk layouts, boot mode, drivers, network mappings and application licences tied to virtual hardware identifiers all need attention. For Azure Local, Azure Migrate supports VMware migrations, and the same application checks apply against its supported configurations.
Pilot the cutover and define the limits of rollback
We use representative workloads to test transfer speed, shutdown and final synchronisation, application start-up, performance and backup. Database owners and application vendors are involved where consistency or certification depends on their procedures. The cutover plan states when a workload can return to its source and how new transactions would be handled. Once users write data to the destination, switching on the old VM alone is not a complete rollback.
Retire the source after validation
We confirm application acceptance, monitoring, recovery and the support handover before removing the old environment. Source licences, backups and access remain available for the agreed overlap period. The plan also covers removing redundant jobs, updating the asset record and ending contracts when the source is no longer needed.
Size the local platform for the workloads that will remain
A platform change may sit alongside a move of other systems to Azure or SaaS. Specialist applications may also need a retained VMware environment until their support or replacement path changes. We account for those decisions before sizing Azure Local or Nutanix, and price the extra licences and administration that a mixed estate creates.
See what we’ve delivered for our clients
For PPK Mining Equipment, we compared six paths, including Nutanix and Azure Local. The selected and delivered platform was Azure Local.
nodes in the VMware estate
virtual server workloads migrated
landing paths assessed before selection
Azure Local and Nutanix questions we hear most
Is Azure Local the same as Nutanix AHV?
No. Azure Local and Nutanix are separate platforms. Azure Local uses Hyper-V with Azure management integration. AHV is the KVM-based hypervisor from Nutanix, managed through Prism. Their hyperconverged configurations use Storage Spaces Direct and AOS respectively, and both also have qualified external-storage options.
Does using Microsoft 365 and Azure make Azure Local the obvious choice?
It makes Azure Local worth examining, particularly where existing skills and eligible licences carry value. The local applications, hardware, recovery design and operating cost still need to justify it. Nutanix can also run Microsoft workloads and use Azure Arc for supported guest management.
Do we need Azure Local or Nutanix at all, or can everything move to Azure?
Some environments can move entirely to Azure or SaaS. A local platform still earns its place where applications need low latency to site equipment, large local data sets, continued operation through an internet outage or a vendor that won't support cloud hosting. We work through each workload before sizing local hardware. If Nutanix is the preferred operating model, Nutanix Cloud Clusters can also run it on dedicated hosts in Azure, including Australia East.
Which platform costs less?
It depends on the core count, your existing Microsoft entitlements and the deployment model. Windows Server Datacenter with Software Assurance can remove the Azure Local host fee on qualifying deployments, while Nutanix pricing depends on the NCI edition and add-ons. We compare hardware, licences, migration and operating effort over the same period before recommending either.
Can we reuse our existing servers or SAN?
Possibly, on either platform. The exact servers, processors, network adapters, drives, firmware and drivers have to match the selected platform's supported configurations. Azure Local can attach qualified Fibre Channel or iSCSI arrays and Nutanix supports specific ones through NCI Compute. On Azure Local, external storage also rules out the Azure Hybrid Benefit fee waiver, so we price reuse against replacement.
Can either platform run through an internet outage?
Local virtual machines can continue running, subject to the applications' own external dependencies. Cloud management and services may be unavailable. Cloud-connected hyperconverged Azure Local must synchronise with Azure within each 30-day period. Beyond that, existing VMs continue to run, but new VM creation is restricted until synchronisation resumes. Microsoft's disconnected operations model is a separate deployment choice. For Nutanix, we plan local management access and the effect of losing any central or cloud services.
Can we keep the existing backup product?
Possibly. We check the product's support for the selected hypervisor, platform release and storage design, including application-aware backup, restore methods and recovery to another site. A working VMware backup job does not establish that the same method will protect the replacement platform.
Does leaving VMware require replacing all workloads at once?
No. We can stage compatible groups of workloads and retain VMware where an application still requires it. The plan needs sufficient licences and capacity during overlap, plus a clear cost and operating arrangement for anything retained.
Compare Azure Local and Nutanix before the decision is locked in
Bring us the workload inventory, current licences and hardware position. We'll work through the platform design and full cost, then carry the selected approach through migration and ongoing operation.