Licensing Microsoft Products in Virtualized Environments: VMware and Hyper-V

Why Virtualisation Licensing Is Microsoft's Most Complex Area

More Microsoft compliance findings stem from virtualisation environments than from any other source. The reason is not that the rules are obscure — Microsoft's licensing terms are documented — but that those rules interact with virtualisation management features (live migration, DRS, HA failover) in ways that create licence obligations the organisation may not have anticipated when the infrastructure was designed.

The two dominant enterprise virtualisation platforms — VMware vSphere/vCenter and Microsoft Hyper-V — handle Microsoft product licensing quite differently, and the correct approach for each requires a clear understanding of Microsoft's core virtualisation licensing concepts before the infrastructure architecture is finalised. Getting this wrong is expensive: an unlicensed VMware cluster running SQL Server Enterprise can represent a compliance exposure of several hundred thousand pounds before any audit enhancement factor is applied.

This article covers the essential rules for both platforms, the impact of Broadcom's VMware acquisition, and the practical compliance checkpoints that should be part of every organisation's annual licence review. Our Microsoft licensing advisory team manages virtualisation compliance reviews for enterprises across all major infrastructure configurations.

Windows Server Licensing in Virtualised Environments

The Core Licencing Model

Windows Server 2019, 2022, and 2025 are all licensed by physical cores — specifically, a minimum of 16 cores per physical server (in increments of two cores above that minimum) for Standard and Datacenter editions. The edition choice determines the virtual machine rights attached to each physical licence:

• Windows Server Datacenter: Unlimited virtual machine rights on the licensed physical host. This edition is the correct choice for dense virtualisation environments where many Windows Server VMs run on each physical server.
• Windows Server Standard: Two virtual machine rights per licence set. For a 32-core host, you would need two Standard licence sets to run four Windows Server VMs. Standard is cost-effective for light virtualisation workloads or physical server deployments.

Windows Server 2025 introduced a new option: per-VM licensing for organisations with active Software Assurance or subscription rights. This allows individual VMs to be licensed at the VM level rather than the physical host level, which is valuable for environments where Microsoft workloads are a small fraction of the total VM estate. The practical trade-off is that per-VM licensing requires more granular tracking — you must maintain an accurate and current mapping of which VMs have per-VM licences versus host-licensed VMs.

The Cluster Problem

The most common compliance gap in Windows Server virtualisation licensing is the cluster scenario. When VMware vCenter's DRS (Distributed Resource Scheduler) or HA (High Availability) can migrate virtual machines between hosts automatically, every host in the cluster must be fully licensed for the Windows Server workloads that could run on it — not just the hosts where those VMs currently reside.

This catches organisations that have licensed only a portion of their cluster hosts for Windows Server Datacenter. The DRS policy may normally keep Windows Server VMs on licensed hosts — but the licence obligation is determined by the capability for migration, not the current state of placement. If DRS or HA could move a Windows Server VM to an unlicensed host, Microsoft's position is that the unlicensed host must be covered.

The practical options are: license every host in the cluster for Datacenter, establish DRS rules (VM/Host affinity groups) that prevent Windows Server VMs from migrating to unlicensed hosts and document those rules, or segregate Windows Server workloads into dedicated clusters with full Datacenter coverage. Each approach has operational trade-offs; the compliance requirement is the same across all three.

SQL Server Licensing in Virtualised Environments

Per-Core Licensing: The Safer Choice for Virtualisation

SQL Server can be licensed per core or per server with CALs. In virtualised environments, per-core licensing is almost always the more appropriate model because it avoids the user/device counting complexity that CAL licensing introduces when the user population is large or distributed.

The per-core licensing rules for SQL Server in virtualised environments work as follows:

• Per-VM licensing: License the number of virtual cores assigned to the VM, with a minimum of four cores per VM. A SQL Server VM with 8 vCPUs requires 8 SQL Server per-core licences.
• Per-host licensing: License all physical cores on the host (minimum 4 per processor), and run unlimited SQL Server VMs on that host. This is the Datacenter equivalent logic for SQL — it is valuable when SQL Server density per host is high.

The same cluster mobility problem that affects Windows Server applies to SQL Server. If SQL Server VMs can migrate between hosts via DRS or live migration, every host that those VMs could run on must be covered. This is the highest-value finding in most SQL Server virtualisation audits, and it affects both VMware and Hyper-V environments equally.

SQL Server Enterprise vs Standard in VMs

SQL Server Enterprise edition includes virtualisation rights that allow it to run in unlimited VMs on a fully licensed host. SQL Server Standard is limited to the licensed core count and does not provide unlimited VM rights. For organisations running multiple SQL Server Standard instances on a single VMware host, the per-host licensing model for SQL Server Enterprise may provide better economics — a calculation worth modelling before the next licence review.

Hyper-V vs VMware: The Licensing Difference That Matters

Microsoft Hyper-V has a structural advantage over VMware for Windows Server licensing: the Hyper-V host itself uses Windows Server Datacenter, and Datacenter's unlimited VM rights extend to the Hyper-V environment natively. There is no separate virtualisation fee, no third-party hypervisor consideration, and the licence mobility rules align precisely with how Hyper-V's live migration and clustering features work.

VMware vSphere introduces a third-party hypervisor layer that Microsoft's licensing terms treat differently in one important respect: Licence Mobility — the right to move software licences between servers within a Server Farm more frequently than the standard 90-day minimum — requires active Software Assurance. Without Software Assurance, you may only reassign a licence to a different server once every 90 days. In a VMware DRS environment where VMs migrate continuously, this 90-day rule applies at the licence level, not the VM level — and it is routinely violated by organisations that have not specifically addressed it in their infrastructure design.

With Software Assurance, the Licence Mobility rights in Server Farms allow much more frequent reassignment, effectively aligning licence mobility with DRS/live migration behaviour. The cost of Software Assurance (typically 25–33% of licence cost annually) must be weighed against the compliance risk of operating without it in a dynamic VMware environment. For organisations with active VMware DRS clusters running significant Microsoft workloads, Software Assurance is rarely optional from a compliance perspective.

The Broadcom VMware Acquisition: New Cost and Compliance Pressures

Broadcom's completed acquisition of VMware has materially changed the economics of running VMware-based infrastructure. The key developments that affect Microsoft licensing decisions include:

VMware Subscription Transition

Broadcom has discontinued VMware perpetual licences and moved to subscription-only VCF (VMware Cloud Foundation) bundles. For organisations renewing VMware contracts, this has produced reported cost increases of 15–30% for equivalent functionality. This changes the economic comparison between VMware and alternative hypervisors (Hyper-V, Nutanix AHV, KVM-based platforms) and for some organisations makes the migration away from VMware financially compelling even when factoring in transition costs.

Azure VMware Solution (AVS) Changes

From October 15, 2025, Azure VMware Solution stopped bundling VCF subscriptions with new nodes. Organisations using AVS must now bring their own VMware licences (BYOL) for new capacity. A deadline of October 31, 2026 applies to converting existing PayGo AVS nodes. This adds a new licence management obligation for organisations using AVS as a migration or disaster recovery platform, and the BYOL requirement interacts with the licence mobility rules discussed above.

The Case for Hyper-V Re-evaluation

For organisations with predominantly Microsoft workloads on VMware, the Broadcom acquisition creates a practical opportunity to re-evaluate Hyper-V (or Azure Stack HCI for hybrid scenarios) as the primary virtualisation platform. Hyper-V's native alignment with Windows Server Datacenter licensing, the absence of a third-party hypervisor cost, and the improved economics of Azure Arc management across Hyper-V and Azure environments make the total-cost comparison more favourable than it was when VMware perpetual licences were available at pre-acquisition pricing.

Azure Arc and Hybrid Licensing

Azure Arc has introduced a new licensing model for organisations that want to manage on-premises Windows Server and SQL Server workloads through Azure's management plane while maintaining or gradually transitioning their infrastructure footprint. The key Arc licensing options include:

• Azure Arc pay-as-you-go: $33.58 per core per month for Windows Server managed through Arc. This shifts traditional CapEx licence cost to an OpEx subscription model, which may align better with some organisations' financial structure.
• Extended Security Updates: Arc enables Extended Security Updates for Windows Server 2012 (end of mainstream support October 2023) at no additional cost for Arc-enrolled servers. This provides a compliance and security bridge for organisations that have not yet migrated legacy workloads.
• Azure Hybrid Benefit via Arc: Organisations with Windows Server Datacenter or Standard licences with active Software Assurance can apply Azure Hybrid Benefit through Arc to reduce Azure VM costs — a common optimisation for hybrid cloud deployments.

Azure Arc does not replace the on-premises licensing requirement — it adds management and billing options on top of it. An organisation must still comply with Windows Server and SQL Server virtualisation licensing rules for its on-premises estate regardless of whether Arc is deployed. Arc's value is in unified management, compliance reporting visibility, and access to Arc-specific pricing options for new capacity provisioning.

VDI Licensing: A Common Source of Non-Compliance

Virtual Desktop Infrastructure (VDI) deserves specific attention because it is the most frequently miscited area in Microsoft virtualisation licensing. The rules differ fundamentally depending on whether the VDI solution is persistent or non-persistent, and whether users are accessing from company-managed devices or personal/third-party devices.

Users accessing Windows 10 or Windows 11 virtual desktops from company-managed, commercially licensed devices are typically covered by the Windows licence on the physical device through Microsoft's VDA (Virtual Desktop Access) rights — but only if those physical devices are licensed with a qualifying Windows edition. Users accessing from personal devices or devices outside the physical device licence structure require a separate Windows VDA per user or device licence.

Microsoft 365 E3 and above include Windows 365 (Cloud PC) rights and VDA rights as part of the subscription — a significant benefit that organisations on perpetual Windows licensing do not have. For large VDI deployments, this is a meaningful cost consideration in the choice between perpetual and subscription licensing for Windows.

Seven Compliance Checks for Virtualised Microsoft Environments

The following checklist covers the compliance areas most commonly flagged in Microsoft virtualisation audits. These should be validated annually or whenever significant infrastructure changes occur:

1. Cluster host coverage: Are all hosts in VMware or Hyper-V clusters where Microsoft workloads can migrate fully licensed for Windows Server Datacenter?
2. 90-day reassignment rule: Do you have Software Assurance providing Licence Mobility, or are VMs pinned to specific hosts and migrating no more frequently than the 90-day minimum?
3. SQL Server per-VM core counts: Is the licensed vCPU count for SQL Server VMs equal to or greater than the assigned vCPU count, with a minimum of four per VM?
4. VDI access device coverage: Do all users accessing Windows virtual desktops have qualifying Windows device licences, VDA licences, or M365 subscription coverage?
5. CAL coverage: Are all users or devices accessing Windows Server, SQL Server, SharePoint Server, or Exchange Server covered by appropriate CALs or equivalent subscription rights?
6. Service provider licensing: If you use a managed service provider to host any Microsoft workloads, do they hold a valid SPLA (Service Provider Licence Agreement) for the software they operate on your behalf?
7. Azure VMware Solution BYOL: If using AVS, do you have valid VMware licences for BYOL requirements effective from October 2025, and have you assessed the October 2026 PayGo conversion deadline?

Planning Your Virtualisation Licence Strategy

The virtualisation licence strategy decision for most enterprises in 2026 comes down to three scenarios. For predominantly Windows Server workloads on a refresh cycle, Hyper-V or Azure Stack HCI is typically the lowest-cost and lowest-compliance-risk path, particularly as VMware costs have increased post-Broadcom. For mixed workloads where VMware provides operational benefits, the economics of VMware plus Software Assurance need to be reassessed against the post-Broadcom subscription pricing. For organisations on a hybrid cloud journey, Azure Arc with per-VM or pay-as-you-go licensing provides the most flexibility and the clearest path to cloud-native management without an abrupt break from existing investments.

Whichever direction makes sense for your organisation, the compliance foundation is the same: accurate inventory of physical hosts, VM assignments, and licence coverage; clear policies on cluster mobility and its licensing implications; and an annual review process that catches licence gaps before Microsoft identifies them first.

Our Microsoft licensing advisory specialists provide virtualisation compliance reviews as a standalone engagement or as part of a broader EA optimisation project. If your last virtualisation licence review was more than 18 months ago, or if you have made significant infrastructure changes in that period, a targeted review is worth the investment.