Windows Server: license the VM, not the host

Did you know that you can license Windows Server per virtual machine? Licensing every physical core, the old way, can leave your bill several times higher than it needs to be!

1. One host, four legal ways to license it

A Windows Server license lives in one of two places. It covers the physical host, or it covers a single virtual machine. That leaves you four variants.

1. Standard on the host. You license every physical core, at least 8 per processor and at least 16 per server. That covers 2 VMs.
2. Standard stacked on the host. Every further full set of core licenses on the same host covers 2 more VMs. Most estates know the pattern as placeholder licensing.
3. Datacenter on the host. The same core count, and the coverage runs to as many VMs as that host can run.
4. Per VM. Microsoft accepts the license on the machine itself: at least 8 core licenses per VM, matched to its virtual cores. Microsoft calls that licensing by virtual machine, and it holds only while the licenses carry active Software Assurance or run as subscriptions.

2. Density decides, and the break even sits high

You pay for cores, and cores are sold in 2-core packs. The example is one host with 64 physical cores running 7 VMs of 8 vCores each. Every price is an Estimated Retail Price for three years of license and Software Assurance.

• Datacenter 2-core pack = USD 1'164. The host has 64 cores, which makes 32 × 2-core packs. 32 × USD 1'164 = USD 37'248, and that covers as many VMs as the host can run.
• Standard 2-core pack = USD 205, about a sixth of it. A VM with 8 vCores needs 4 × 2-core packs. 4 × USD 205 = USD 820 per VM, so the 7 VMs come to 28 × 2-core packs and USD 5'740.

Break even = about 45 VMs. USD 37'248 divided by USD 820 per VM. Below 45 VMs on that host per VM is cheaper, above it the host is.

Outside dedicated VDI farms, few estates reach that density.

And VMs are not what you count. Every VM bills its own vCores, at least 8, so the measure that decides is licensed virtual cores per physical core. Per VM stays cheaper below roughly 5.7 of them. A handful of oversized VMs crosses that line as surely as a crowd of small ones.

3. 1'094 VMs, four scenarios, one winner

The numbers come from a real inventory, anonymized: 186 hosts in 35 VMware clusters plus 13 standalone servers, 10'104 physical cores on the VM hosts and 1'094 Windows Server VMs. That is about 7 VMs per active host.

We priced four compliant scenarios over that inventory at USD Estimated Retail Prices, three years, license and Software Assurance. Your contract prices will differ. The mechanism will not.

The last row is the surprise. The optimizer was free to keep Datacenter wherever it wins, and it kept it nowhere. Per VM won in all 35 clusters, because not one of them comes near the break-even density.

4. What the 83% is made of

The physical model licenses 10'104 cores of hardware. The per-VM model licenses the workload instead: 9'494 virtual cores, which become 4'901 × 2-core packs once every VM clears the 8-core minimum. And it buys them as Standard packs, not Datacenter packs.

Over three years that difference is USD 4'907'393, and it does not close in year four. At Estimated Retail Prices the annual Software Assurance renewal runs about USD 853'200 in the physical model and about USD 142'900 per VM. Six years of per-VM renewals, about USD 857'500, cost roughly what one year of the physical model costs.

None of this is a discount, a promotion, or a negotiation result. Microsoft published the option. This estate never took it.

5. You already own Datacenter, and the obvious move is the trap

Most estates are not starting from zero. They hold Datacenter core licenses for every physical core, bought years ago, and the reasonable reflex is that the money is spent and the model is settled.

Two purchases arrived together, and they are worth separating. The license is perpetual and paid. Software Assurance is the part that comes back every year, and per VM licensing hangs on it: Microsoft grants that model only for licenses with active Software Assurance or subscription licenses. The question is not what you spent. It is what the next renewal costs.

Your Datacenter licenses do qualify for the per-VM model, because the model is gated on active Software Assurance and not on the edition. Moving them over needs no purchase at all: this estate needs 4'901 × 2-core packs per VM and already holds 5'052. That looks like the answer. It is the trap.

It saves almost nothing. The pack count falls by 5.9%, from 5'206 to 4'901, because the same virtual cores still have to be licensed. The rate does not fall at all. Software Assurance on a Datacenter pack runs about 5.8 times a Standard pack, and Software Assurance steps up from Standard to Datacenter but never down. Reusing what you own keeps you on the expensive rate.

Buying the Standard licenses outright and letting the Datacenter coverage lapse costs USD 1'004'705 over three years, Software Assurance included. Renewing Datacenter for the same VMs across the same three years costs USD 2'469'957. Roughly fifteen months of Datacenter Software Assurance pays for the entire replacement.

The licenses you stop renewing are not wasted twice. They stay perpetual for every version released while the coverage was active, which leaves you a physical fallback you own outright and no longer pay for.

6. Five steps before your next renewal

1. Build the inventory. Every host with its core count and cluster, every Windows Server VM with its vCPU count. Two sheets are enough.
2. Check the prerequisites. Per-VM licensing requires licenses with active Software Assurance or subscription licenses, and every CAL used to reach those servers clears the same bar. That includes the RDS CAL, which the Product Terms carry as an additive access license with no exemption. Without it, the option does not exist for you.
3. Price all four scenarios with your contract numbers. Retail prices rank the options, only your prices size the decision. Run it per cluster, because density varies inside one estate.
4. Price the renewal, not only the purchase. If you already hold Datacenter, add two renewal paths to the comparison: keeping Software Assurance as you are, and keeping it after moving the same licenses per VM. Between those two the pack count barely moves and the rate does not move at all. That is why the third path usually pays: buy Standard for the VMs and let the Datacenter coverage lapse.
5. Set up tracking before you switch. Per VM means the license follows the VM. Record the assignment per VM and re-run the comparison when the estate changes. The Windows Server module of the Zation Platform computes all four scenarios from the two-sheet inventory and keeps the assignment current.

Limits and exceptions

This is one estate, not a law. A host farm running 50 small VMs per host sits past the break even, and there Datacenter stays the right answer. The 83% belongs to this density. The mechanism belongs to everyone.

Estimated Retail Prices are not contract prices. The table uses the USD Estimated Retail Price from the Microsoft price list for Windows Server 2025. Enterprise Agreement and CSP pricing shift the totals, rarely the ranking at this distance.

The Hybrid Benefit argument rarely survives the math. Azure Hybrid Benefit belongs to Software Assurance, not to Datacenter: Standard licenses with active SA carry it too. Datacenter adds simultaneous use on premises and in Azure, where Standard covers one place at a time. Weigh that extra right against the renewal difference. About USD 710'300 per year pays the compute of roughly 422 general purpose D4s v5 VMs (4 vCPUs, 16 GiB, USD 0.192 per hour) running around the clock.

The prerequisite has a tail. Per-VM licensing binds you to active Software Assurance or subscriptions, on the server licenses and on every CAL, the RDS CAL included. The totals above price the server licenses only, so the CAL side lands on top of them. The commitment also costs you the freedom to let SA lapse later.

Two things depend on your agreement, not on the rules above. Whether your program lets you renew Software Assurance on a reduced number of perpetual licenses, and what ends when Datacenter coverage lapses. per VM licensing on those licenses, the Flexible Virtualization Benefit for outsourcer hosting, disaster recovery rights, the step up to a newer edition, Azure Hybrid Benefit and the ability to buy Extended Security Updates all stop with the coverage. Price that loss instead of assuming it is zero.

Reassignment rules cut both ways. In the per-VM model you may reassign within a server farm as often as needed. The physical model does not allow that: there the 90 day rule applies. License Mobility, by contrast, covers only the External Connector for Windows Server, never the core licenses. Check your agreement type before you move, not after.

Six questions for your next renewal

1. How many licensed virtual cores do the VMs on each host add up to, and how many physical cores does that host have?
2. Which of our Windows Server licenses carry active Software Assurance or run as subscriptions?
3. Do our CALs meet the same requirement?
4. What do a Standard pack and a Datacenter pack cost in our agreement, and what does it cost to renew Software Assurance on each? The renewal rate decides more than the pack price.
5. Can we renew Software Assurance on fewer licenses than we own, and what minimum does our program impose?
6. Who updates the license assignment when a VM is created, resized, or deleted?

Bottom line

Datacenter pays for density, and density is counted in virtual cores, not in VMs. Add up the licensed vCores per host before you renew: below roughly 5.7 per physical core the license belongs on the VM, above it on the host. And if you already own Datacenter, the model is the smaller half of the decision. Moving those licenses per VM saves a few percent. Putting the workload on the right edition saves the rest.