Licensing Windows Server on Proxmox: cores, OSEs and the cluster question

Timo Wevelsiep•Updated: 09.07.2026

Editorial note: Versions, commands and prices may change. Please verify critical steps independently before production use. This guide does not replace individual consulting.

Not legal advice. This article reflects the state of July 2026 to the best of our knowledge. The Microsoft Product Terms and your license agreement alone are authoritative. For binding answers, consult your Microsoft licensing partner.

Windows Server runs on Proxmox just as legally as on Hyper-V or VMware - Microsoft licensing is hypervisor-neutral. Still, "licensing Windows Server on Proxmox" is one of the most common questions in migration projects, and the forums are full of half-knowledge. This article maps the Product Terms rules to the Proxmox context: core minimums, Standard vs. Datacenter, the cluster question with live migration, and activation without AVMA. It complements our guides on Hyper-V migration and VMware migration.

The core principle: you license the host, not the VM

Windows Server is classically licensed by the physical cores of the server the software runs on. The Product Terms put it like this: the number of licenses required equals the number of physical cores on the licensed server - subject to a minimum of 8 core licenses per physical processor and 16 core licenses per server. A single-socket server with 12 cores therefore still needs 16 core licenses; a dual-socket server with 2×24 cores needs 48.

Whether that server runs Hyper-V, VMware or Proxmox makes no difference to this calculation. The Product Terms contain no clause requiring a specific hypervisor - Microsoft's licensing guide itself speaks neutrally of "hardware virtualization software (such as Hyper-V)".

Standard vs. Datacenter: counting OSEs

The editions differ in their virtualization rights:

Edition	Virtualization rights on the fully licensed host
Standard	2 OSEs (VMs) - plus the physical instance if used solely for hosting/managing the VMs
Standard with stacking	every 2 additional VMs: license all host cores again (e.g. a 16-core host with 6 VMs = 3× 16 core licenses)
Datacenter	any number of OSEs on the licensed host

The practical rule of thumb: from roughly 5-7 Windows VMs per host, Datacenter usually becomes cheaper than stacked Standard - the exact threshold depends on your purchasing channel and prices.

Worked example: 16-core host with 6 Windows Server VMs

Model	Calculation	Licenses required
Standard with stacking	2 OSEs per full host licensing, 6 VMs = 3 passes of 16 cores	48 Standard core licenses
Datacenter	License the host fully once, unlimited OSEs	16 Datacenter core licenses
Per-VM (Flexible Virtualization Benefit)	6 VMs × 8-core minimum per VM	48 core licenses (subscription or active SA)

The decision therefore comes down to the price ratio of your purchasing channel: 48 Standard cores versus 16 considerably more expensive Datacenter cores. Two points shift the calculation in a cluster: the host models multiply with every node the VMs are allowed to run on - the per-VM model stays constant at 48 core licenses no matter how many nodes the cluster has. CALs apply on top in all three models.

The cluster question: live migration and the 90-day rule

This is where most uncertainty arises in Proxmox clusters. The relevant rules from the Universal License Terms:

Licenses are assigned to a specific physical server.
A license may be reassigned to another device no earlier than 90 days after its last assignment (exceptions: permanent hardware failure and similar).

A live migration is not a permitted license reassignment. The practical derivation (not a literal cluster clause, but the established reading): every host a Windows VM can run on must be sufficiently licensed. In a 3-node Proxmox cluster with freely movable VMs, that means licensing all three nodes per the core rules - or deliberately restricting the mobility of Windows VMs to licensed hosts via HA rules.

The official way out is not called "License Mobility". Microsoft explicitly states that Windows Server is not eligible for License Mobility through Software Assurance (that program targets application servers such as SQL Server). The matching mechanism is licensing by virtual machine (Flexible Virtualization Benefit, since October 2022): at least 8 core licenses per VM matching its virtual cores - available only with subscription licenses or active Software Assurance. For clusters with few Windows VMs on many hosts, this is often the more economical path.

New since Windows Server 2025, there is also pay-as-you-go via Azure Arc: monthly per-core billing instead of perpetual licenses, without the classic CAL requirement (except RDS CALs) - relevant for elastic environments, but it requires Arc-connecting the VMs.

Activation: AVMA does not work on Proxmox

Automatic Virtual Machine Activation is a Hyper-V feature: per Microsoft it requires an activated Datacenter host with the Hyper-V role and "doesn't work with other server virtualization technologies". On Proxmox you activate instead via:

KMS: platform-independent, activates physical and virtual systems, needs at least 5 servers in the network, renewal every 180 days - the standard path for domain environments (alternatively Active Directory-based activation).
MAK/retail keys: for small environments without KMS infrastructure.

Both are documented by Microsoft without any hypervisor condition. CALs remain mandatory regardless: every accessing user or device needs a Windows Server CAL (Standard and Datacenter alike).

Practical recommendations by size

1-2 Windows VMs on a single host: Standard license for the host (mind the 16-core minimum), KMS/MAK activation - done.
Mixed cluster with few Windows VMs: evaluate per-VM licensing (subscription/SA required) or pin Windows VMs to dedicated licensed nodes via HA rules.
Windows-heavy cluster: Datacenter per node pays off quickly - OSE counting disappears and VMs stay freely movable.
Always: document the core count (sockets, cores per node) - in an audit, that is half the battle. The platform's own cost side is covered in How much does Proxmox cost?.

How WZ-IT does it

In every Hyper-V or VMware migration, the Windows license check is part of the inventory: we count cores and VMs, calculate Standard stacking against Datacenter against per-VM licensing, and document the assignment traceably - binding sign-off rests with your Microsoft licensing partner. Afterwards we run the environment as Managed Proxmox from €179.90 per node per month. We are happy to discuss your setup in a free initial consultation.

You'd rather not run Proxmox yourself? WZ-IT handles setup, operations and maintenance – GDPR-compliant from Germany.

Managed Proxmox →

Frequently Asked Questions

Answers to the most important questions

Yes. The Microsoft Product Terms contain no restriction to a specific hypervisor. Core licensing applies to the physical server regardless of whether Hyper-V, VMware or Proxmox/KVM runs underneath. Microsoft's own licensing documents use hypervisor-neutral wording.

Per the Product Terms, the number of licenses equals the number of physical cores on the licensed server - subject to a minimum of 8 core licenses per physical processor and 16 core licenses per server. Licenses are sold in 2-packs and 16-packs.

Fully licensing the host with Standard permits two OSEs (virtual machines), plus the physical instance if it is used solely for hosting and managing the VMs. For every two additional Windows Server VMs, all cores of the host must be licensed again (stacking). Datacenter permits any number of VMs on the licensed host.

Licenses are assigned to a specific physical server and, per the Universal License Terms, may be reassigned no earlier than 90 days after the last assignment. In practice this means: if a Windows VM can live-migrate to multiple hosts, each of those hosts must be sufficiently licensed - or you license per VM. This is a derivation from the quoted rules, not a literal cluster clause.

Since October 2022 (Flexible Virtualization Benefit), VMs can be licensed instead of the physical host: at least 8 core licenses per virtual OSE, matching its virtual cores. It requires subscription licenses or licenses with active Software Assurance. Important: classic License Mobility through Software Assurance explicitly does NOT apply to Windows Server - Microsoft lists it as not eligible.

Per Microsoft, AVMA requires a Windows Server Datacenter host with the Hyper-V role installed and does not work with other virtualization technologies - so it is unavailable on Proxmox. The standard path is KMS (platform-independent, threshold of 5 servers, 180-day renewal), alternatively Active Directory-based activation or MAK keys.