Windows Server comes in two editions. Standard allows two virtual machines per set of licences. Datacenter allows unlimited. The economics are governed by a single variable: how many virtual machines will you run on each physical host? Get this calculation wrong and the consequences compound silently.
This guide is part of the Mastering Windows Server Licensing series. For core counting, see Core-Based Licensing Mechanics. For virtualisation, see Virtualisation and Containers.
Windows Server is licensed per physical core on the host server. Not per virtual machine, not per user, and not per server instance. Every physical host must be licensed with a minimum of 16 core licences, sold in packs of 2. If the host has more than 16 physical cores, you must licence every core.
The critical principle. You licence the physical host, not the virtual machines running on it. The edition you purchase (Standard or Datacenter) determines how many Windows Server VMs you are entitled to run on that licensed host. This is where the Standard-vs-Datacenter decision becomes a financial calculation rather than a feature comparison.
One set of Standard core licences assigned to a physical host entitles you to run two Windows Server virtual machines (plus the physical host OS, if used). Need more VMs? Buy additional sets. Four VMs require two sets. Six VMs require three sets. Eight VMs require four sets. Each additional set doubles the cost for that host without adding any functionality.
Standard pricing reference. Open NL / retail pricing for Windows Server 2022 Standard: approximately $6,000-$6,200 for a 16-core licence set (the minimum per host). EA pricing varies by organisation, typically 30-55% below retail depending on your EA pricing level and negotiated discounts.
One set of Datacenter core licences assigned to a physical host entitles you to run unlimited Windows Server virtual machines on that host. Two VMs, twenty VMs, two hundred VMs. The licence cost is the same.
Datacenter pricing reference. Open NL / retail pricing for Windows Server 2022 Datacenter: approximately $16,000-$16,400 for a 16-core licence set. That is roughly 2.6-2.7x the Standard price for the same 16 cores.
| Feature | Standard | Datacenter |
|---|---|---|
| Core OS features | ✓ Full | ✓ Full |
| Hyper-V | ✓ | ✓ |
| VM rights (OSEs) | 2 per licence set | Unlimited |
| Windows Server containers | ✓ Unlimited | ✓ Unlimited |
| Hyper-V isolated containers | 2 per licence set | Unlimited |
| Storage Spaces Direct (S2D) | ✗ | ✓ |
| Software-Defined Networking (SDN) | ✗ | ✓ |
| Shielded Virtual Machines | ✗ | ✓ |
| Hot-patching | ✗ | ✓ (Azure Arc) |
| Azure Hybrid Benefit | ✓ (with SA) | ✓ (with SA) |
| Approximate retail price (16-core set) | ~$6,000 | ~$16,000 |
This is the section that saves or costs you six figures. The math is deterministic. There is a precise VM density per host at which Datacenter becomes cheaper than stacking Standard licences.
The crossover calculation. Assume a standard dual-processor server with 16 cores total. Standard cost: ~$6,000 per 16-core set (allows 2 VMs). Datacenter cost: ~$16,000 per 16-core set (unlimited VMs). The crossover: $16,000 / $6,000 = 2.67 sets. Since Standard allows 2 VMs per set, the crossover is 2.67 x 2 = 5.3 VMs. At 6+ VMs per host, Datacenter is cheaper.
| VMs Per Host | Standard Sets | Standard Cost | Datacenter Cost | Cheaper Edition | Savings |
|---|---|---|---|---|---|
| 1-2 | 1 | $6,000 | $16,000 | Standard | $10,000 |
| 3-4 | 2 | $12,000 | $16,000 | Standard | $4,000 |
| 5-6 | 3 | $18,000 | $16,000 | Datacenter | $2,000 |
| 7-8 | 4 | $24,000 | $16,000 | Datacenter | $8,000 |
| 9-10 | 5 | $30,000 | $16,000 | Datacenter | $14,000 |
| 19-20 | 10 | $60,000 | $16,000 | Datacenter | $44,000 |
The 40-host VMware cluster scenario. A financial services firm operates a VMware cluster with 40 dual-processor hosts (16 cores each), running an average of 12 Windows Server VMs per host. Standard cost: 40 hosts x 6 sets x $6,000 = $1,440,000. Datacenter cost: 40 hosts x 1 set x $16,000 = $640,000. Overpayment: $800,000. When the compliance review discovered 8 hosts actually running 14-16 VMs (but licensed for only 12), the additional true-up added another $96,000. Total cost of the wrong edition choice: $896,000.
The hypervisor platform introduces a licensing dimension that Standard-vs-Datacenter comparisons frequently omit.
VMware: where the compliance trap lives. When running Windows Server VMs on a VMware cluster with vMotion enabled, Microsoft requires that every host in the cluster be licensed for the maximum number of VMs that could run on any single host. A 10-host VMware cluster running 80 Windows Server VMs total must licence each host for the possibility that all 80 VMs could land on any single host. With Standard, that is 40 licence sets per host x 10 hosts = 400 licence sets. With Datacenter, it is 1 licence set per host x 10 hosts = 10 licence sets.
For any VMware environment with DRS or vMotion enabled, Datacenter is not just cheaper. It is the only edition that provides compliance certainty. Unlimited VMs per host means it does not matter where VMs migrate, how many land on a single host, or how the cluster redistributes workloads.
Dual-use opportunity. With Software Assurance, Windows Server licences can be applied simultaneously to on-premises hosts and Azure VMs during cloud migration (typically 180 days of concurrent use). Datacenter's unlimited on-premises VM rights combined with AHB Azure entitlements create the most flexible hybrid licensing posture available.
Trap 1: VM density exceeding Standard entitlement. The most prevalent finding. An organisation purchases Standard for a host, runs 2 VMs initially (compliant), then the virtualisation team adds VMs over time (4, 6, 8, 10) without informing licensing. By the time the audit discovers 10 VMs on a Standard-licensed host, the remediation cost is 5x the original licence investment plus retroactive fees.
Trap 2: vMotion on Standard-licensed VMware clusters. vMotion requires every host in the cluster to be licensed for the maximum VM capacity. Organisations that licence each host for its average VM count (rather than the cluster maximum) are non-compliant on every host. This is the single most expensive Windows Server compliance finding.
Trap 3: Unlicensed physical cores. The 16-core minimum per host and 8-core minimum per processor are floors, not caps. A host with two 20-core processors (40 physical cores) requires 40 core licences, not 16. Modern server processors routinely exceed 16 cores per socket.
Trap 4: Missing Software Assurance on mobile VMs. Licence Mobility requires active SA. Without SA, each host must be independently licensed for all VMs it could potentially host. Organisations that let SA lapse while continuing to use vMotion or Live Migration lose mobility rights.
Trap 5: Container miscounting. Hyper-V isolated containers follow the same rules as VMs: 2 per Standard licence set, unlimited on Datacenter. Organisations deploying container workloads with Hyper-V isolation on Standard frequently miss this because containers do not appear in traditional VM inventories.
| Server Role / Scenario | Recommended Edition | Rationale |
|---|---|---|
| Physical-only server (no VMs) | Standard | No virtualisation = no density premium |
| 1-2 VMs, static assignment | Standard | Within Standard entitlement, no mobility complexity |
| 3-4 VMs, static assignment | Standard (2 sets) | Still cheaper, but evaluate trajectory |
| 5+ VMs per host | Datacenter | Cheaper at ~6 VMs and above |
| VMware cluster with vMotion/DRS | Datacenter | Eliminates cluster-wide compliance risk |
| Hyper-V cluster with Live Migration | Datacenter | Same mobility licensing risk as VMware |
| Hyper-converged (S2D, SDN) | Datacenter | S2D and SDN are Datacenter-exclusive |
| Branch office (1 server, 1-2 workloads) | Standard | Low density, no mobility, minimal risk |
| Azure Hybrid with extensive AHB | Datacenter + SA | Maximum AHB flexibility + unlimited on-prem |
Technically yes, but for clusters with live migration enabled, every host must be licensed for the maximum VM count that could land on it. If one host has Datacenter (unlimited) and another has Standard (2 VMs), a migration event placing a third VM on the Standard host creates a compliance gap. Clusters with live migration should be uniformly licensed, and Datacenter is almost always the correct choice for the entire cluster.
Indirectly. SQL Server is licensed independently from Windows Server, but the Windows Server edition determines how many VMs the host is entitled to run, and each SQL Server VM requires its own SQL Server licence. Datacenter eliminates the VM-count compliance risk for the Windows layer, but you still need to licence SQL Server separately for each instance.
Yes. Without SA, your on-premises Windows Server licences cannot be applied to Azure VMs. You must pay the full Azure "licence included" rate, which is 40-80% more expensive. Maintaining SA on your Datacenter licences preserves the AHB entitlement that makes Azure VMs economically viable.
Physical cores only. Hyperthreading (logical cores) does not affect the licence count. A processor with 16 physical cores and 32 logical threads requires 16 core licences, not 32. This is one of the most common over-licensing mistakes we encounter.
For any organisation with 20+ virtualised Windows Server hosts, independent advisory delivers material value. An advisor audits your VM density per host, vMotion/DRS scope, core counts, and SA coverage, identifying compliance gaps before Microsoft does. The remediation cost of gaps found proactively is typically 30-50% lower than gaps discovered during a Microsoft audit.