Azure Local vs. VMware ESXi: Key differences you need to know
The VMware renewal quote arrives and looks nothing like last year’s. The bundle is different, the license is now a subscription, and the minimum core count doesn’t match the two small hosts in your server closet. That has been a common experience since Broadcom bought VMware and changed how it sells vSphere, and it is why so many conversations about Azure Local vs. VMware start with a renewal notice. We support Azure Local, Hyper-V and VMware at client sites, and most of our clients are moving off VMware to Hyper-V in some form.
Talk to an advisor
Ask about your own setup.
We ask what you’re trying to accomplish and tell you what we’d look at first. It costs nothing to talk, and no price comes up on this call.
Azure Local vs VMware at a glance
| Azure Local | VMware vSphere | |
|---|---|---|
| What it is | Microsoft’s on-premises virtualization platform, built on Hyper-V and failover clustering and managed through Azure | The ESXi hypervisor, managed through vCenter |
| How it is sold | Billed at a flat rate per physical processor core, monthly, on your Azure subscription, with a 60-day free trial after registration | Per-core subscription with a minimum of 16 cores for each physical CPU |
| Windows Server VMs | An add-on Windows Server subscription for unlimited VMs, or your existing licenses | Licensed separately |
| Management | Azure portal, Azure CLI and templates, with Azure role-based access control and Azure Policy | vCenter |
| Hardware | Validated systems from Microsoft’s Azure Local catalog, with joint support from Microsoft and the hardware vendor | VMware’s own compatibility guide |
| Cloud connection | Must sync with Azure at least once every 30 days | No comparable cloud dependency |
One licensing detail changes the math for many Microsoft shops. If you own Windows Server Datacenter core licenses with active Software Assurance (or qualifying subscription licenses), Azure Hybrid Benefit can waive the Azure Local host fee and the Windows Server subscription. Which platform costs less depends on your core counts, how many Windows Server VMs you run and what licenses you already own, so price both against your actual hardware. As a Microsoft CSP partner, we can help sort out the licensing side.
What changed with VMware
ESXi and vCenter remain mature platforms with deep features and a large pool of experienced admins. What changed is how they are sold.

- 01In December 2023, Broadcom stopped selling perpetual licenses and support renewals for them, moving customers to subscriptions.
- 02The product line was consolidated into bundles, led by VMware Cloud Foundation and vSphere Foundation.
- 03Licensing is per core, with a minimum of 16 cores for each physical CPU, even if the CPU has fewer cores.
- 04vSphere 7 reached end of general support on October 2, 2025, and vSphere 8 is scheduled to reach it on October 11, 2027.
If you are still on vSphere 7, you are past end of general support and no longer getting new security patches from the vendor. That needs fixing whichever platform you choose next. Our post on building an IT refresh plan covers how to keep track of dates like these.
When Azure Local fits
Microsoft renamed Azure Stack HCI to Azure Local in its 2411 release in November 2024, so older quotes and articles may still use the old name. Your VMs and data stay on servers in your building, and Azure handles deployment, updates, monitoring, access control and policy. Optional services such as Azure Monitor or Microsoft Defender for Cloud can be added.
- You already run Microsoft 365 and Azure and want one identity system and one set of admin tools.
- You own Windows Server Datacenter licenses with Software Assurance, so Azure Hybrid Benefit applies.
- You are buying new hosts anyway and can choose from the validated catalog.
- You want evidence for auditors. Azure Local applies Microsoft security baseline settings to its hosts and reports compliance in the Azure portal.
- You want updates for the operating system, agents and supported drivers and firmware to arrive as one combined package.
The traditional design is hyperconverged, with compute and storage on the same servers and storage pooled across them. Microsoft has since added support for external SAN storage, single-node deployments for small sites, and a disconnected mode for strict sovereignty cases.
When something else fits better
- Plain Hyper-V on Windows Server, for a small environment that doesn’t need Azure management.
- Moving workloads to the cloud, when the server room itself is the problem.
- Staying on VMware with a right-sized subscription, when your team knows vSphere well and the numbers work.
- A site that can’t count on reaching Azure. If a connected Azure Local system goes 30 days without syncing, it enters a reduced functionality mode where existing VMs still run but you can’t create new ones.
- Hosts that aren’t in the Azure Local catalog. You can’t install it on any server you have lying around.
Questions to ask before you decide
- How many physical cores do our hosts have, and what would each platform cost on those exact cores?
- Which Windows Server licenses and Software Assurance do we already own?
- Are our current servers in the Azure Local catalog or on VMware’s compatibility guide?
- Can this site reliably reach Azure at least once every 30 days?
- How much downtime can each VM tolerate during a move?
- Who on our side, or our IT provider’s, will manage Azure as well as the hosts?
If you move: a migration plan
Microsoft supports migrating VMware VMs to Azure Local with Azure Migrate. It needs no agents installed in the VMs beforehand, keeps the data flowing locally instead of through the cloud, and is designed for minimal downtime. A sensible plan:
- Inventory your VMs: size, operating system, dependencies and tolerance for downtime.
- Check licensing before you price anything.
- Size new nodes from the validated catalog, or confirm existing servers qualify.
- Back up everything and test a restore. Our client backups run hourly, are copied off-site daily and are immutable, and that copy is what makes a cutover safe to attempt.
- Migrate in waves, starting with low-risk VMs, then move business-critical systems in planned windows.
- Keep the old environment until everything is confirmed, then wipe and retire the old hosts properly.
Whatever you pick, keep the platform on a supported version, protect admin accounts with MFA, and back up VMs to a separate system so a compromised host can’t destroy your only copy. Our guide to secure data backup covers that last part, and lifecycle management keeps server replacements on the calendar.
Got a VMware renewal quote on your desk? Book a 15-minute call, bring the quote and your host specs, and we will lay out what each option looks like for your hardware. More on our hosted and cloud services.
Frequently asked questions
What is Azure Local?
Azure Local is Microsoft’s on-premises virtualization platform, built on Hyper-V and failover clustering and managed through Azure. Your VMs and data stay on validated servers in your building, and Azure handles deployment, updates, monitoring and access control. Microsoft called it Azure Stack HCI until the rename in November 2024.
Can Azure Local replace VMware?
Yes, for many Microsoft shops. Microsoft supports migrating VMware VMs to Azure Local with Azure Migrate, with no agents installed in the VMs beforehand and the data moving locally instead of through the cloud. It needs hosts from Microsoft’s validated catalog and a site that can sync with Azure at least once every 30 days. If either is a problem, plain Hyper-V or a right-sized VMware subscription may fit better.
Is Azure Local the same as Hyper-V?
Not quite. Azure Local is built on Hyper-V and failover clustering, but it adds Azure management for deployment, updates, monitoring, access control and policy, and it runs only on validated hardware. Plain Hyper-V on Windows Server is managed locally, runs on servers you already own and has no Azure sync requirement, which often suits a small environment that doesn’t need cloud management.
Is Azure Local free?
No. Azure Local is billed monthly at a flat rate per physical processor core on your Azure subscription, with a 60-day free trial after registration. Windows Server VMs need an add-on subscription or licenses you already own. If you have Windows Server Datacenter core licenses with active Software Assurance, Azure Hybrid Benefit can waive both the host fee and the Windows Server subscription.
Sources
- Microsoft Learn: What is Azure Local?
- Microsoft Learn: What’s new in Azure Local 24xx releases (2411 rename)
- Microsoft Learn: Azure Local billing and payment
- Microsoft Learn: Azure Hybrid Benefit for Azure Local
- Microsoft Learn: Activate Windows Server VMs on Azure Local
- Microsoft Learn: Hyperconverged deployments of Azure Local
- Microsoft Learn: Azure Migrate based VMware migration for Azure Local
- Microsoft Learn: Azure Local FAQ (connectivity and 30-day sync)
- The Register: Broadcom VMware licensing changes, December 2023
- Broadcom: Counting cores for VMware Cloud Foundation and vSphere Foundation
- Northdoor: VMware vSphere end of support guide
Next step
Let us handle this for you.
Cloud and hosted servers set up, secured and kept within budget.
- 15 minutes
Tell us which question brought you here and how your office runs.
We’ll tell you how it applies to you and what we’d look at first.
If we’re not the right fit, we’ll say so.
