Windows Server Licensing for Virtualization: Standard or Datacenter?

Windows Server licensing rules for virtualization: core minimums, Standard’s 2-VM right, Datacenter, clusters and the 90-day rule, and the break-even calculation.
Technical summary
Technology
Windows Server Standard, Windows Server Datacenter, Hyper-V, CAL, RDS CAL
Topic
Calculating Windows Server licenses on virtualization hosts
Level
Beginner–intermediate
Prerequisites
  • Host hardware inventory
  • Knowledge of the VM and cluster structure
In this article9 sections

In a virtualization environment, Windows Server is mostly licensed by the number of cores in the physical host and the highest number of Windows VMs that can run on that host at any moment. Organizations with subscription licenses or active Software Assurance can also choose licensing per virtual machine. In the physical core model, the second part, the highest VM count, is easily overlooked. Below we apply the per-core rules to Hyper-V, VMware or Proxmox hosts, and show the break-even point between Standard and Datacenter without giving prices, using formulas and worked examples. The audience is IT managers preparing a licensing budget before a host renewal or cluster expansion.

Basics of per-core licensing

Since Windows Server 2016, the Standard and Datacenter editions are licensed per physical core. The rules are:

  • All physical cores in the server are licensed. Logical processors created by Hyper-Threading aren’t counted.
  • Each physical processor needs at least 8 core licenses.
  • Each server needs at least 16 core licenses.
  • Core licenses are sold in 2-packs (and 16-packs).
  • In this model the license is assigned to the physical server, not the virtual machine. Whether the hypervisor is Hyper-V, VMware ESXi or Proxmox VE doesn’t change this rule; the cores of the host running Windows VMs are licensed.

In small server infrastructures, the minimum rules are decisive. The examples below show the number of core licenses required:

Server configuration Physical cores Cores to license
1 processor × 6 cores 6 16 (server minimum)
2 processors × 6 cores 12 16 (8 per processor)
2 processors × 12 cores 24 24
2 processors × 32 cores 64 64

Start the licensing calculation with the number of physical cores read on the host, not the value in the BIOS or on the quote:

# Windows (Hyper-V host)
Get-CimInstance -ClassName Win32_Processor |
  Select-Object SocketDesignation, NumberOfCores, NumberOfLogicalProcessors

# Linux-based hypervisor (e.g. Proxmox VE)
lscpu | grep -E "^Socket|Core\(s\) per socket|^Thread"

When buying a new server, this point directly determines cost. High-core-count processors can do the same work with fewer hosts, but since every core is licensed, more cores than needed increase the Windows Server licensing cost. Idle cores are licensed too. Choose processors together with VM sizing; for that, see the virtual machine sizing article.

Virtualization rights of the Standard edition

When all physical cores of a server are licensed with Standard, the right arises to run 2 Windows Server operating system environments (OSEs) on that server, i.e. 2 Windows Server VMs. For more VMs, all of the server’s cores are licensed again with Standard; each additional full license set adds 2 more VM rights.

There is a special rule for the physical operating system instance. If Windows Server is installed on the host itself (Hyper-V), the physical instance can also run while the 2 permitted virtual OSEs are in use; however, the physical instance may be used only to host and manage the virtual machines. Installing a file server, DHCP or an application on the host breaks this right. This is the common non-compliance on small office servers: a share folder or print server has been installed on the Hyper-V host “since it’s on anyway.”

Linux VMs don’t consume Windows Server OSE rights. If 2 Windows and 10 Linux VMs run on the same host, a single Standard set is enough. For Windows Server containers, in Standard, Hyper-V isolated containers also count toward the OSE limit.

The Datacenter edition and unlimited VMs

When all physical cores of a server are licensed with Datacenter, an unlimited number of Windows Server VMs can run on that server. Licensing is still per core; the 8/16 minimum rule applies as is.

Datacenter also includes features not in Standard: chief among them are Storage Spaces Direct, unlimited use of Storage Replica and software-defined networking (SDN) components. If a hyperconverged (S2D-based) Hyper-V cluster is to be built, the edition choice leans toward Datacenter regardless of the number of VMs. The current list of feature differences between editions is on the Windows Server edition comparison page in Microsoft Learn.

Licensing impact of clusters and live migration

A license is assigned to a physical server and, as a rule, can be reassigned from one server to another at most once every 90 days (permanent hardware failure is the exception). Live migration, however, moves VMs between hosts within minutes. Combining the two rules, the practical result is: each host must be licensed for the highest number of Windows VMs that could run on it at any moment.

Example: a three-node cluster has 12 Windows VMs in total, normally with 4 VMs on each host. When one host goes into maintenance, the remaining two hosts carry 6 VMs each. If licensed with Standard, each host must be licensed for 6 VMs, i.e. with 3 full Standard sets. In clusters using automatic load balancing where it isn’t restricted which host VMs run on, Datacenter is often the better option, since in the worst case all VMs could gather on a single host.

In clusters licensed with Standard, VM placement must be restricted (preferred owner lists, anti-affinity rules) and this must be documented. Otherwise, after a failure or maintenance night, licensing compliance breaks without anyone noticing.

Software Assurance (SA) or subscription licenses provide additional rights in some scenarios: using an on-premises license in Azure with Azure Hybrid Benefit and the per-VM licensing option are examples. The conditions of per-VM licensing are explained under a separate heading below. Because the conditions of these rights vary by version and agreement type, verify the details on Microsoft’s Windows Server licensing page.

Licensing per virtual machine

This is a second licensing option, separate from the physical core model, and can be used only with subscription licenses or licenses with active Software Assurance (SA). Its conditions are different:

  • The number of core licenses required equals the number of virtual cores assigned to the virtual machine; at least 8 core licenses are required per virtual machine.
  • Standard’s two-OSE right and Datacenter’s unlimited OSE right belong to the physical core model. In this model, each virtual machine is licensed separately.
  • Licenses can be reassigned as often as needed between servers in the same server farm.
  • The CALs used to access the server must also be covered by a subscription or active SA.

The rules, tables and worked examples in the other sections of this article are based on the physical core model.

Worked examples and the break-even point

With Standard, the number of license sets needed for N Windows VMs is N ÷ 2 rounded up. Each set covers all of the host’s cores. Datacenter is a single set regardless of the number of VMs. The break-even point is found with this formula:

Datacenter becomes economical when: ⌈N ÷ 2⌉ × (Standard core price) > (Datacenter core price)

In other words, if Datacenter’s core price is a certain multiple of Standard’s, Datacenter is cheaper at a VM count that requires more Standard sets than that multiple. Since prices vary by agreement type and period, calculate the ratio from your current quote. The table below shows the Standard core license need for a 2 × 12 = 24-core host:

Windows VMs per host Number of Standard sets Standard core licenses Datacenter core licenses
2 1 24 24
4 2 48 24
8 4 96 24
12 6 144 24
16 8 192 24

Worked example: assume Datacenter’s core price is 5 times Standard’s (a ratio chosen only to show the method). For 10 VMs, 5 Standard sets are needed; the cost is equal. At 11 or 12 VMs, 6 sets are needed and Datacenter becomes more economical. If the number of VMs on the host is expected to grow over the next 3–5 years, today’s break-even point is reason enough to decide in favor of Datacenter.

If a platform change is on the agenda, the licensing calculation is independent of the hypervisor choice: even if Windows VMs move to Proxmox VE or another hypervisor, the host cores still have to be licensed. The hypervisor changes. The licensing calculation doesn’t. The other items of the platform decision are in the platform choice after VMware article.

CALs and other additional licenses

A core license is only the right to run the server software. Users or devices accessing the server also need an access license:

  • Windows Server CAL: Per user or per device. Needed for every user or device accessing services such as authentication, file sharing and DNS/DHCP. The CAL version must be equal to or newer than the version of the server being accessed; when moving to Windows Server 2025, the CAL inventory is checked too.
  • RDS CAL: Needed in addition to the Windows Server CAL for users who open remote desktop sessions. Licensing differences by desktop virtualization model are in the RDS, VDI and Azure Virtual Desktop comparison article.
  • Application licenses: SQL Server is licensed separately; in the per-core model, the virtual cores assigned to the VM are licensed, with a minimum of 4 cores per VM. That’s why giving a VM extra vCPUs is a direct licensing cost.

The CAL equivalent of Microsoft 365 subscriptions varies by plan: enterprise plans such as Microsoft 365 E3/E5 may include Windows Server CAL use rights, but RDS CALs aren’t included in these plans. Don’t reduce the CAL count without verifying your plan’s coverage in the Product Terms. For user licenses on the cloud side, see the choosing Microsoft 365 licenses article.

License inventory checklist

Before an audit or renewal, the following information should be current and documented. A missing line means an open finding in the audit:

  • For each host, the number of processors, physical cores per processor, and the number of cores to license after applying the minimum rules.
  • Which edition (Standard/Datacenter) and how many sets each host is licensed with; license assignment dates.
  • The highest number of Windows VMs that can run on each host in normal and failure conditions; VM placement restrictions if Standard is used.
  • Windows Server CAL and RDS CAL counts, types (user/device) and versions.
  • SA or subscription coverage and end dates.
  • Verification that no role other than Hyper-V runs on the physical host.
  • That the inventory matches purchase documents and records in the licensing portal.

If a migration from versions whose support has ended is planned, handle the licensing calculation together with the migration schedule; the Windows Server 2016 end of support migration plan article gives this order. For planning the host and licensing structure together, see our virtualization and data management and IT consulting pages.

Frequently asked questions

How many core licenses does a single-processor, 8-core server need?

It needs 16 core licenses. The rules require at least 8 core licenses per processor and at least 16 per server; if the number of physical cores is below these minimums, the minimum value is licensed.

How many VMs can I run on a host with a Standard license?

When all of the host’s physical cores are licensed once with Standard, 2 Windows Server VMs can be run. For each additional 2 VMs, all cores must be licensed again with Standard. Linux VMs aren’t counted in this number.

Is the licensing rule different for Windows VMs running on VMware or Proxmox?

No. In the physical core model, the Windows Server license is assigned to the physical host’s cores regardless of the hypervisor. Whatever hypervisor runs on the host, the cores of the host running Windows VMs are licensed with Standard or Datacenter.

Do I have to license every host in a cluster separately?

In the physical core model, yes. The license is assigned to the physical server and can be reassigned at most once every 90 days. That’s why each host must be licensed for the highest number of Windows VMs that could run on it, including live migration and failure scenarios. In clusters where VM placement isn’t restricted, Datacenter is the practical choice.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek System Support

Server installation, configuration, incident response and scheduled maintenance. Active Directory, virtualization and backup are managed with the same discipline.

Knowledge Center

Other articles