Azure Local as a VMware Alternative: When It Fits and When It Does Not
Azure Local comes up in almost every VMware exit conversation, and for Microsoft aligned organisations it deserves a serious look. But it is not a like for like swap, and the thing that makes it powerful, the Azure control plane, is also the thing that does not suit everyone. Here is an honest, vendor neutral view of where it fits and where it does not.
If you are weighing a move off VMware and your organisation already runs on Microsoft, Azure Local will be near the top of the shortlist. That is reasonable. It is a credible platform with real momentum behind it. But the question we are asked is rarely "is it good", it is "is it right for us", and the honest answer turns entirely on how Microsoft centric you are and how you feel about a cloud connected control plane. So let us deal with what it actually is first, then with fit.
What Azure Local actually is
Azure Local is Microsoft's on premises infrastructure platform, and it is the evolution of what was previously called Azure Stack HCI. The renaming was not just cosmetic. It signalled Microsoft folding its on premises and edge infrastructure into a single Azure managed story. You run virtual machines and containers on validated hardware in your own data centre or at the edge, the hypervisor underneath is Hyper-V, and you operate the whole thing through Azure rather than through a separate on premises management console.
The hardware comes from the usual partners, Dell, HPE, Lenovo and others, as validated systems rather than anything you assemble yourself. The commercial model is a subscription billed per physical core through your Azure agreement, which will feel familiar if you have been through the Broadcom shift, because the unit of account is the same. What is different is where the management lives.
Azure Local is not a drop in replacement for vSphere that happens to be cheaper. It is a different operating model. You are not just swapping a hypervisor, you are moving your control plane into Azure. That is the real decision, and everything else follows from how you feel about it.
The Arc managed model, and why it cuts both ways
The defining feature of Azure Local is that it is managed through Azure Arc. Your clusters, your virtual machines, your policies and your monitoring are all projected into the Azure portal and governed with the same tools you use for cloud resources. For an organisation already living in Azure, that is genuinely attractive. One control plane, one identity model through Entra, one set of governance and policy tooling, one billing relationship. The on premises estate stops being a separate world with its own console and its own habits.
That same design is also the reason Azure Local does not suit everyone. The control plane is in Azure, which means the platform expects regular connectivity back to the cloud. It is built to tolerate short periods of disconnection, but it is not designed to run indefinitely cut off, and it is not the right choice for a genuinely air gapped or sovereignty constrained environment that must operate with no cloud dependency at all. You are also accepting that your on premises infrastructure now has a commercial and operational relationship with Azure that you cannot fully sever. For some that is a feature. For others it is exactly the dependency they were trying to escape when they looked past VMware.
VMware kept your infrastructure self contained and charged you heavily for the privilege. Azure Local lowers that wall and ties your on premises estate into Azure. Whether that is liberating or concerning depends on whether Azure is where you already want to be.
Where Azure Local fits well
There is a clear profile of organisation for which Azure Local is not just viable but arguably the natural destination. It is rarely about the technology in isolation, it is about alignment.
The Microsoft centric estate
Best fit
If your identity is Entra, your productivity is Microsoft 365, your cloud is Azure and your teams already operate with Azure tooling, Azure Local extends a world you know rather than introducing a new one. The learning curve is shallow because the management model is one your people already use, and the governance story is consistent end to end.
The hybrid by design organisation
Strong fit
If you genuinely run workloads across on premises and Azure and want one consistent way to govern both, the Arc model earns its place. Workloads that need to sit on premises for latency, data residency or cost can do so while still being managed alongside everything in the cloud.
The edge and distributed estate
Good fit
Retail, manufacturing and distributed sites that need local compute but central control are a natural use case. Managing many small clusters from a single Azure pane is far more tractable than maintaining a traditional management server per location.
Where it does not fit
Equally, there are situations where Azure Local is the wrong answer, and it is more honest to say so plainly than to let an organisation discover it after a migration.
- You want genuine independence. If the goal of leaving VMware is to reduce dependence on any single large vendor's ecosystem, moving your control plane into Azure does not deliver that. It changes which ecosystem you depend on, it does not remove the dependency.
- You need to run disconnected. Air gapped environments, or estates with strict rules against a cloud control plane touching production, are not a good match for a platform whose management lives in Azure.
- You are not really a Microsoft shop. If your identity, tooling and skills are not already Microsoft aligned, much of the advantage evaporates, and you take on the Azure relationship without the benefit of already being there.
- You assume it will simply be cheaper. Per core subscription plus the Azure services you consume can add up. Azure Local can be cost effective, but it has to be modelled honestly against your actual usage, not assumed to undercut VMware by default.
Ask one question before anything else: are we trying to consolidate onto Microsoft, or are we trying to get out from under a dominant vendor altogether. Azure Local is an excellent answer to the first and a poor answer to the second. Be clear which one you are.
What migrating from VMware actually involves
If Azure Local does fit, treat the migration with the same respect you would any platform move. The hypervisor change from vSphere to Hyper-V is rarely the hard part. The effort sits in the same places it always does: data gravity, disaster recovery coupling, networking and firewall dependencies, backup interlock and the operational tooling your teams rely on day to day. Microsoft provides tooling to assess and move workloads, but the runbooks, the integrations and the validation are where the real work lives. We cover that ground in detail in our guide on migrating off VMware without breaking production, and the same discipline applies here.
It is also worth comparing Azure Local honestly against the other credible destinations rather than defaulting to it because it is familiar. For organisations that are not Microsoft anchored, a platform such as Nutanix may be a better fit, and the right way to weigh them is on your own requirements rather than on brand comfort.
How to decide
Azure Local is one option on a wider map, and the sensible way to approach it is to place it inside the bigger stay versus go question rather than evaluating it in isolation. Our decision framework for whether to leave VMware sets out how estate size, feature use, renewal uplift and risk appetite should drive the call, and where each destination earns its place. If you decide Microsoft alignment is genuinely your direction, Azure Local becomes a strong candidate. If you are unsure, that uncertainty is itself the signal to model it properly before committing.
This is the kind of evidence based comparison we run for clients every week, and we have seen what it looks like when it is done well. Our case study on a VMware and Broadcom licensing transformation shows how an independent audit and honest modelling kept a major UK enterprise in control of the decision rather than cornered by the renewal clock.
Weighing Azure Local against the alternatives?
Tell us about your estate and your Microsoft alignment, and we will give you an independent view: whether Azure Local genuinely fits, how it compares to the other destinations, and what a sensible path looks like. Vendor neutral, with no platform to sell. We have sat on the other side of the table.
Prefer email? Reach us directly at hello@c4cgroup.co.uk.
Frequently asked questions
Is Azure Local the same as Azure Stack HCI?
Effectively yes. Azure Local is the renamed and evolved form of Azure Stack HCI. The change reflected Microsoft pulling its on premises and edge infrastructure into a single Azure managed platform, so if you researched Azure Stack HCI in the past, Azure Local is its direct successor rather than a separate product.
Does Azure Local need a constant connection to Azure?
It needs regular connectivity rather than a permanent live link. The platform is designed to tolerate short periods of disconnection, but its management and billing live in Azure, so it is not built to run indefinitely cut off. For genuinely air gapped environments that must operate with no cloud dependency, it is not the right choice.
How is Azure Local licensed and priced?
It is a subscription billed per physical core through your Azure agreement, plus the Azure services you choose to consume on top. The per core model will feel familiar after the Broadcom changes. The important discipline is to model it against your actual usage rather than assume it automatically undercuts VMware.
Is Azure Local a good fit if we are not a Microsoft centric organisation?
Usually not. Most of its advantage comes from extending a Microsoft world you already run, the same identity, tooling and governance. If your identity, skills and cloud are not already Microsoft aligned, you take on the Azure relationship without the benefit of already being there, and another destination may fit better.
What does migrating from VMware to Azure Local involve?
The hypervisor move from vSphere to Hyper-V is rarely the hard part. The effort is in data gravity, disaster recovery coupling, networking and firewall dependencies, backup interlock and operational tooling. Microsoft provides assessment and migration tooling, but the runbooks, integrations and validation are where the real work sits.
Is Azure Local cheaper than staying on VMware?
Sometimes, but not by default. It can be cost effective for Microsoft aligned estates, but per core subscription plus consumed Azure services has to be modelled honestly. Cost should be one input into the decision, alongside fit and independence, not the headline assumption that drives it.