What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Azure Stack HCI is now called Azure Local in Microsoft’s current documentation. Recent releases have strengthened Azure-managed operations, VMware migration, security, Kubernetes integration and GPU administration, making the platform a more credible alternative for organizations that want on-premises infrastructure tied closely to Azure. That is progress in specific areas—not proof of complete feature parity with VMware or Nutanix.
There is also a versioning issue for existing installations: support for the Azure Stack HCI 23H2 operating system ended in April 2026. The final 23H2 release was October 2025, version 11.2510. New projects should be planned against current Azure Local release guidance, while existing deployments should confirm their upgrade and support path.
What changed in Azure Stack HCI?
The most consequential change is operational: Azure Local uses Azure Arc as its management connection to Azure. Administrators can manage the environment through the Azure portal, CLI, PowerShell and ARM templates, including VM lifecycle tasks and, for supported configurations, GPU assignment. The Arc resource bridge represents on-premises VMs, logical networks, disks and related resources in Azure. Microsoft’s current Azure Local release notes describe cloud-based deployment and updates, cloud monitoring, simplified VM management and security.
This model will feel familiar to teams already using Azure’s identity, policy and automation tools. It can reduce the separation between datacenter operations and Azure operations, but it also makes Azure Arc connectivity and the associated management model central to the design.
Recommended Free Tools
#1 Best Overall
- Server 2022 Standard 16 Core
Can you migrate VMware VMs to Azure Local?
Yes. Azure Migrate supports VM migration workflows from both VMware and Hyper-V to Azure Local. Microsoft’s 2026 additions include dedicated migration roles for Azure Local and Terraform support for replication and migration. Subsequent updates describe recovery options after replication setup failures and preservation of Secure Boot for eligible UEFI Generation 2 VMs.
This is an increasingly automated path, not a guarantee that every VM can move unchanged. Before scheduling a migration, validate the source version, Azure Migrate appliance, guest operating system, network design and VM firmware requirements against the applicable Microsoft instructions. Treat Secure Boot preservation as conditional on the VM being an eligible UEFI Generation 2 machine.
For a VMware estate, migration tooling answers only part of the decision. Application dependencies, downtime tolerance, storage and network design, backup and disaster-recovery arrangements, and operational skills still need to be assessed for the target environment.
What Azure Local adds for Kubernetes and cloud-native workloads
Azure Stack HCI 23H2 introduced container-based applications running alongside existing VMs through AKS enabled by Azure Arc. The Kubernetes workloads are automatically Arc-enabled, so Azure configuration, observability and security services can extend to the cluster.
Rank #2
- Windows Server Standard 2022 English 1pk DSP OEI 4Cr NoMedia/NoKey (APOS) AddLic
That makes Azure Local relevant to organizations that need both conventional virtualization and cloud-native applications on-premises. It is a different value proposition from evaluating a platform only as a hypervisor: the question becomes whether Azure-integrated Kubernetes and governance fit the team’s application and operating model.
Security and governance: a notable strength, with a dated claim
Microsoft’s 2023 Azure Stack HCI announcement reported that 23H2 covered “100% of applicable settings in the Azure security baseline,” describing that as a 2x increase over version 22H2. This is a vendor-reported baseline-coverage figure for that release, not an independent security certification or a guarantee that a deployed system is secure regardless of configuration.
Microsoft’s architecture guidance describes a defense-in-depth setup that can use Defender for Cloud, Microsoft Sentinel, Azure Policy and Trusted launch. Their value depends on deployment choices, supported hardware and how the organization configures and operates the services. Teams should map these controls to their own security requirements rather than treating a baseline-coverage percentage as a substitute for that work.
GPU administration and AI workloads
Microsoft’s current release notes list GPU Management from Azure as a preview. It is intended to centralize GPU inventory, partition configuration, assignment to workloads and lifecycle management. Azure Local VM management documentation also describes orchestration for assigning GPUs to VMs.
Rank #3
- HPE MS WS22 10USR CAL WW LICSS22 10USR CAL WW LTU
This is useful for assessing Azure Local for AI inference, graphics or other accelerated workloads, but it is not enough by itself to establish suitability. Preview status, supported hardware, drivers and deployment type can affect what is available. Confirm support for the exact server and GPU configuration before treating the feature as a production requirement.
How Azure Local compares with VMware and Nutanix
The evidence supports a narrower conclusion than “Azure Local now matches VMware and Nutanix.” Microsoft’s own positioning distinguishes Azure VMware Solution, which it says works best when a customer wants to stay on VMware, from Azure Stack HCI, positioned for customers who want to stay on-premises and virtualize workloads while running cloud-native apps. Nutanix’s AHV administration guide documents familiar VM operations, live migration, high availability and resiliency. These are comparison points, not a complete side-by-side capability test.
| Decision area | What the available platform documentation establishes | What to validate for your environment |
|---|---|---|
| VM lifecycle and self-service | Azure Local VM management is exposed through Azure Arc and Azure management tools (Microsoft Azure Local VM management documentation). | Required self-service workflows, role boundaries and integration with existing provisioning. |
| Live migration and high availability | Nutanix AHV documentation describes live migration, high availability and resiliency. A directly comparable Azure Local capability assessment is not stated in the cited Microsoft material. | Maintenance behavior, failover design, workload recovery objectives and operational procedures. |
| Storage and networking | A complete like-for-like comparison is not stated in the cited Microsoft and Nutanix materials. | Required storage features, network segmentation, throughput, failure handling and integration with existing systems. |
| Kubernetes and cloud-native services | 23H2 introduced AKS enabled by Azure Arc, with workloads automatically Arc-enabled (Microsoft’s 23H2 announcement and architecture guidance). | Cluster lifecycle, supported Kubernetes features, application dependencies and how teams will operate the cluster. |
| GPU and AI support | Azure GPU Management is listed as a preview; Microsoft documentation also describes GPU assignment orchestration. | Hardware, drivers, workload type, deployment support and whether preview functionality is acceptable. |
| Security and governance | Microsoft describes Defender for Cloud, Sentinel, Azure Policy and Trusted launch; its 100% applicable-baseline figure is a vendor-reported 23H2 claim from 2023. | Required controls, licensing, configuration, monitoring ownership and audit evidence. |
| VMware migration | Azure Migrate supports VMware and Hyper-V workflows; Microsoft lists 2026 additions for migration roles, Terraform automation and selected recovery and Secure Boot scenarios. | Source and guest compatibility, appliance and network prerequisites, downtime and application testing. |
| Automation and APIs | Azure Local management includes CLI, PowerShell and ARM templates; Terraform support for migration was added in preview in 2026. | Coverage of the team’s specific deployment, day-two operations and infrastructure-as-code needs. |
| Hardware and support ecosystem | A comparative hardware and support-ecosystem assessment is not stated in the cited materials. | Validated systems, component choices, regional support, lifecycle commitments and escalation paths. |
| Licensing and total cost | Microsoft’s current Architecture Center guidance describes a monthly subscription charged per physical processor core; a directly comparable VMware or Nutanix total cost is not stated. | Subscription scope, infrastructure and support costs, Azure services, migration effort and operating costs over the intended term. |
Use the table as a shortlist for a workload-specific evaluation, not as a verdict on feature equivalence. Microsoft’s cited release and architecture material explains Azure Local’s direction; Nutanix’s AHV guide describes AHV administration. Neither establishes that one platform covers every feature, integration or support requirement of another.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What does Azure Local cost?
Microsoft Architecture Center guidance describes Azure Local as a monthly subscription charged per physical processor core. The cited guidance does not establish a single total price for an installation. Hardware, support, Azure services, workload scale and migration or operating effort affect the cost case, so compare a deployment estimate with the existing platform using the same workload scope and time horizon.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWho should consider Azure Local?
- Azure-centric IT teams: Arc-based management and Azure governance may fit teams seeking a shared operating model between Azure and on-premises infrastructure.
- Organizations combining VMs and Kubernetes: AKS enabled by Azure Arc provides a cloud-native option alongside VM workloads.
- Teams moving from VMware: Azure Migrate provides a supported migration workflow, but compatibility and operational planning remain necessary.
- GPU workload owners: GPU administration is developing, but preview status and hardware support need to fit the intended production use.
- Organizations committed to VMware: Microsoft positions Azure VMware Solution for customers who want to remain on VMware, so compare that option as well as a platform change.
The practical takeaway is to evaluate Azure Local against the workloads and operations you actually need, not against a blanket claim of catching up. Its clearest advances are Azure-connected management, migration tooling, cloud-native integration and expanding GPU administration; the right choice still depends on validated capabilities, ecosystem fit and total cost.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
