Azure Local is not the default VMware exit path. Neither is VMware Cloud Foundation the unquestioned benchmark it was two years ago. And yet the industry keeps framing the VMware exodus as a binary choice: stay and pay, or move to Microsoft’s preferred Azure-connected platform. Both options serve somebody’s agenda. Neither starts from the question that actually matters to infrastructure operators: what do I need, and what’s the cheapest way to get it without creating new dependencies?

The series started with a simple question: if so many organizations are unhappy with the VMware commercial path they are on, where should they go next?

After twenty posts, the answer is clearer than ever.

For a lot of organizations, the right answer is not “stay where you are and absorb the bill.” It is also not automatically “move to Azure Local because it is Microsoft’s newest answer.” The right answer is often the platform that has been in the rack, in the OS, and in the skill set for years: Hyper-V on Windows Server 2025.

This series advocates for on-premises Hyper-V with three-tier SAN architecture. But intellectual honesty , and the credibility of everything we’ve written , demands that we evaluate every option fairly. Storage Spaces Direct and Azure Local have legitimate use cases. Three-tier isn’t always the right answer.

The cost lens matters, though. For many organizations leaving VMware, the decision is not just about technical elegance. It is about whether Azure Local’s host fee and potential hardware refresh are justified, or whether reusing existing compute and existing SAN is the smarter move for the workloads they actually run.

The servers sitting in your datacenter right now, the Dell PowerEdges, the HPE ProLiants, and the Lenovo ThinkSystems, were designed to run hypervisors, not a specific hypervisor. Any hypervisor.

This might seem obvious, but it’s worth stating clearly: enterprise server hardware is hypervisor-agnostic. The same CPUs, memory, storage controllers, and network adapters that run ESXi today will run Hyper-V tomorrow. You’re not abandoning hardware investments when you change virtualization platforms; you’re simply loading different software.

I’m in the middle of writing The Hyper-V Renaissance, an 18-part series making the case for traditional Hyper-V with Windows Server 2025 as a serious virtualization platform. It’s been consuming most of my writing time, and I’ve been heads-down on TCO comparisons, cluster builds, and PowerShell automation.

But sometimes you stumble across something that deserves its own post, and you have to step away from the main project for a minute.

The invoice arrived, and the meeting quickly followed.

For nearly two decades, the “cost of virtualization” was a line item we grumbled about but accepted. It was the “VMware Tax,” the price of admission for a stable, feature-rich datacenter. But in the wake of the Broadcom acquisition and the subsequent licensing overhaul, that tax has, for many organizations, turned into a ransom.

This isn’t just about price hikes. It’s about a fundamental shift in how infrastructure is consumed. We are forcibly moving from a world of perpetual licenses and optional support to a world of mandatory subscriptions and bundled software stacks.

Introduction

A Perfect Storm Creates Opportunity

If you’ve been watching the virtualization market over the past eighteen months, you’ve witnessed something extraordinary: a once-stable industry thrown into chaos by a single acquisition. When Broadcom completed its $69 billion purchase of VMware in November 2023, few anticipated how dramatically, and rapidly, the landscape would shift. What followed wasn’t just a pricing adjustment; it was a fundamental restructuring that has sent shockwaves through data centers worldwide.

From VMware vSphere to Azure Local: What Changes and Where to Click

The industry shift away from VMware has accelerated dramatically. Organizations worldwide are evaluating alternatives, driven by licensing changes, acquisition uncertainty, and evolving business needs. For many enterprises, this transition represents both a significant operational challenge and a strategic opportunity to modernize their virtualization infrastructure.

This blog addresses the practical reality facing infrastructure teams: when organizational decisions mandate a platform change, success depends on understanding exactly how daily operations translate to the new environment. Rather than debating platform merits, this analysis provides the detailed operational mapping that VMware administrators need to maintain service levels during transition.

(Note: AVS – Azure VMware Solution – is not covered in detail here since it’s essentially outsourcing VMware onto Azure’s hardware. That involves a different calculus: you avoid buying hardware entirely, but you pay cloud rental fees and must fit into Azure’s instance constraints. In this post, we focus on on-premises alternatives where you control the hardware.)

Hardware Considerations: Build Your Cloud on Your Terms

Series Recap: In Part 1 of this series, we examined the total cost of ownership (TCO) implications of different post-VMware paths, comparing capital expenditure vs. subscription models across on-premises Hyper-V, Azure Local (formerly Azure Stack HCI), and Azure VMware Solution (AVS). In Part 2, we dove into licensing – analyzing how VMware vSphere licensing stacks up against Microsoft’s offerings (Windows Server and Azure Local) in 2025, and what those licensing differences mean for choosing a virtualization platform. These earlier posts highlighted that organizations leaving VMware have viable Microsoft-based alternatives that can reduce costs and simplify licensing. Now, in Part 3, we turn to the infrastructure question: What are your hardware options when “rethinking virtualization” away from VMware? Can you reuse your existing servers and storage, or are you forced into buying new, validated hardware nodes? How do Microsoft’s two on-premises solutions – Windows Server Hyper-V with Failover Clustering (WSFC) and Azure Local – compare in terms of hardware requirements? We’ll explore scenarios for customers looking to leave VMware, whether they’re not ready for a hardware refresh or planning a refresh alongside the migration, and we’ll also briefly touch on upcoming VMware Cloud Foundation 9.0 hardware needs.

Welcome to Part 2 of our “Beyond the Cloud: The Case for On-Premises Virtualization” series. In our introductory post, we explored why organizations are reconsidering their virtualization strategies post-VMware acquisition. In Part 1, we conducted a detailed five-year Total Cost of Ownership (TCO) analysis comparing Windows Hyper-V, Azure VMware Solution (AVS), and Azure Local, revealing how different cost structures impact long-term budgets.

A key factor driving those cost differences was how each platform’s licensing model works. In this follow-up, we will demystify the various licensing models – per core, per socket, and per subscription – and compare how Windows Server 2025 (which reached General Availability in November 2024), Azure Local (formerly “Azure Stack HCI”), and VMware (both on-premises and via Azure VMware Solution) handle licensing. Our goal is to highlight not just the pricing structures, but also where hidden costs can lurk beyond the base license. The tone remains practical and evaluative: this isn’t about picking winners as much as helping IT directors and solution architects understand the financial and operational implications of each model.