Microsoft Windows Server and SQL Server licensing on a VMware (Broadcom) estate carries specific host-affinity, cluster-boundary and Software Assurance considerations. The Admodum read on the rules, the Broadcom transition implications and the renewal contest.
Microsoft Windows Server and SQL Server are licensed per physical core. The baseline product term sets a sixteen-core minimum per processor (a processor with fewer than sixteen physical cores still counts as sixteen for licence purposes). On a VMware estate, the licensing route is one of two: per-host (licence all physical cores on every host that runs the Windows Server or SQL Server VM) or per-VM (licence the virtual cores assigned to the VM, with an eight-core minimum per VM).
The per-host route is the default for production estates with dense Windows or SQL Server consolidation; the per-VM route reads commercially for sparse Windows or SQL Server consumption on a primarily non-Microsoft VMware estate. The wider Windows Server core licensing and SQL Server licensing spokes are the per-product framework reads.
VMware vMotion is the live migration of a running VM from one ESXi host to another inside a cluster (or across a stretched cluster). The Microsoft licensing position reads the vMotion movement against the per-host rule: a VM that runs on a host carries a licence position against that host for the duration of the run.
Without Software Assurance, the licence-reassignment restriction applies: a VM that vMotions across hosts inside a ninety-day window requires each of those hosts to be licensed for the VM's cores; the licence cannot be reassigned from one host to another more frequently than every ninety days. The audit reads the vMotion log (the VMware vCenter event history) against the licence allocation; a VM that moves across an unlicensed host inside ninety days is an audit finding.
Software Assurance on the Windows Server or SQL Server licence (or a Windows Server subscription via the Azure Hybrid Benefit, or a SQL Server subscription) waives the ninety-day reassignment restriction. Licence Mobility through Software Assurance permits the VM to vMotion freely across any licensed host inside the same Server Farm (the Server Farm boundary is defined in the product terms as a single data centre and a synchronously connected secondary data centre within a defined geographic boundary).
The wider Software Assurance benefits framework reads SA as a portfolio of fifteen-plus benefits, of which Licence Mobility is the one most directly relevant to a VMware estate. The wider Azure Hybrid Benefit spoke reads the Azure-side Licence Mobility, which extends the SA benefit to the Azure hyperscale surface.
The principal audit finding on a VMware estate is the cluster-boundary breach: a VM moves to a host outside the licensed cluster. The most common patterns are the disaster-recovery cluster activation (a Windows or SQL Server VM is failed over to a DR cluster that is not licensed for production-grade Windows or SQL Server cores), the cross-production-cluster vMotion (a VM moves to a different production cluster that has different licence allocation), and the test-environment promotion (a VM moves from a non-production cluster to a production cluster, or vice versa, without the licence following).
The buyer-side artefact that closes the cluster-boundary question is the cluster-licence map: every ESXi cluster, every host inside the cluster, the per-host core count, the licensed-or-unlicensed declaration, the Server Farm membership, the Software Assurance attachment. The wider SAM audit anatomy framework reads the cluster-licence map against the vMotion event history.
The Broadcom acquisition of VMware and the transition of the perpetual VMware estate to the VMware Cloud Foundation (VCF) subscription has parallel implications for the Microsoft licence position. The Microsoft licence cost scales with the physical core count of the hosts that run Windows or SQL Server VMs; a host-count reduction (achieved by consolidating onto fewer, larger hosts under VCF) reduces the Microsoft core surface; a cluster-topology change (introducing or removing DR clusters, separating production clusters) changes the licensed-host inventory.
The wider Broadcom / VMware practice reads the VCF transition with the Microsoft licence position as a parallel consideration: a buyer rationalising VCF subscription scope reads the Microsoft licence-cost-per-host as a parallel optimisation, not as a separate exercise. The interlock is a renewal-cycle interlock.
The renewal contest on the Microsoft-and-VMware position carries four questions. First: is every licensed host correctly licensed for its per-core consumption (every host, every VM, every running core). Second: is the Software Assurance attachment optimised against the vMotion footprint (a Software-Assurance-attached licence pool is the structural answer to a dense, mobile VMware estate). Third: is the cluster topology and the licence allocation aligned (the cluster-licence map). Fourth: is the Azure Hybrid Benefit being used where the Azure-side workloads are present (the parallel Azure-side optimisation).
The wider engagement sits in the Microsoft practice; the aggregated reading list sits in the Microsoft knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The per-core SQL Server framework against which the VMware host-affinity question is read.
The Windows Server per-core baseline against which the VMware cluster boundary is contested.
The Azure-side Licence Mobility that extends the Software Assurance waiver to the cloud surface.
A senior Admodum Microsoft advisor will read your cluster-licence map, your vMotion event history and your Software Assurance attachment against your renewal and audit posture on a private call. The parallel Broadcom transition can be read on the same call.