Licensing

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.

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.