Windows Server is licensed per-core on the Datacenter and Standard editions, with CAL requirements on top of the core licences. The Admodum read on the editions, the per-core minimum, the virtualisation density, the Datacenter-versus-Standard arithmetic and the Azure Hybrid Benefit.
Windows Server runs in two principal commercial editions for production deployments. Datacenter Edition carries unlimited virtualisation rights on the licensed host: the buyer who licenses all cores on a host can run an unlimited number of Windows Server VMs on that host. Standard Edition carries two Operating System Environments (OSEs) per licensed host: the buyer who licenses all cores on a host can run two Windows Server VMs (or one physical OSE plus one VM) on that host, with the option to stack additional Standard licences to add OSEs (two further OSEs per additional Standard licence stack).
The Essentials Edition (single-server SMB) and the Hyper-V Server (free Hyper-V hypervisor, deprecated) sit outside the per-core EA model. The Web Edition (deprecated) and the Foundation Edition (deprecated) are no longer current product lines.
The per-core licensing model applies on Datacenter and Standard. Each physical core on the host requires a Windows Server core licence; the per-host minimum is 16 cores (eight cores per processor, two processors minimum). A single-processor host with eight cores requires 16 core licences; a two-processor host with 32 cores total requires 32 core licences; a four-processor host with 96 cores total requires 96 core licences. The wider EA framework against which the Windows Server portfolio is licensed sits at the Enterprise Agreement overview; the wider editorial sits in the Microsoft pillar.
Windows Server CALs apply on top of the core licences. Each user or device that accesses a Windows Server instance requires either a User CAL (one per user, with the user accessing from any device) or a Device CAL (one per device, with the device accessing from any user). The User-versus-Device CAL choice tracks the access pattern: many users per device favours Device CALs (call centres, shift workers, shared workstations); many devices per user favours User CALs (knowledge workers, mobile users, multi-device).
The CAL is version-matched. A Windows Server 2022 host requires Windows Server 2022 CALs from the access population. A buyer running a mix of Server 2019 and Server 2022 carries the version-mismatch question: in practice the buyer holds CALs at the highest-version host the user accesses.
Additional CALs apply for specific roles: Remote Desktop Services CAL (RDS CAL, formerly Terminal Services) for any user or device using the RDS surface; Active Directory Rights Management Services CAL (RMS CAL) for the rights-management workload. The wider per-user-versus-per-device CAL framework sits at the per-user versus per-device spoke (forthcoming).
The Datacenter-versus-Standard decision is virtualisation-density arithmetic. Datacenter wins when the density on the host exceeds the breakeven; Standard wins below the breakeven. The breakeven moves on the buyer's specific discounting and on the host core count, but typically sits around 12 to 14 Windows VMs per host at standard EA pricing.
The arithmetic: a 32-core host running 4 Windows VMs licenses under Standard with 8 Standard 16-core licence stacks (4 stacks × 2 OSEs each = 8 OSEs, comfortably above 4 VMs); the same 32-core host running 20 Windows VMs licenses under Standard with 40 Standard 16-core licence stacks (20 stacks × 2 OSEs each = 40 OSEs), which is dramatically more expensive than the single Datacenter licence at 32 cores. The Standard-stacking arithmetic crosses the Datacenter line at the breakeven density.
The decision is per-host, not portfolio-wide. A buyer can run a mix of Datacenter hosts and Standard hosts within the same EA, licensed against the density at each host. The wider Datacenter-versus-Standard arithmetic sits at the Datacenter versus Standard spoke (forthcoming).
The Azure Hybrid Benefit applies on Windows Server SA. A buyer with SA on the on-prem core licence can apply the licence to an Azure VM at a saving against the PAYG Windows rate; the saving runs in the order of 30 to 40 percent against the PAYG Windows-included rate, before any reserved-instance overlay. The application is per-core: each on-prem core licence applied covers one Azure VM core.
The Datacenter SA bearer carries dual-use rights: the same Datacenter core licence under SA can apply to the on-prem workload and to the Azure VM concurrently during the 180-day dual-use migration window, and indefinitely if the on-prem workload runs in a permitted disaster-recovery posture. The Standard SA bearer carries single-use rights during the migration window: the Standard licence applies to either the on-prem OSE or the Azure VM, but not both concurrently.
The wider Azure Hybrid Benefit framework sits at the Azure Hybrid Benefit spoke; the wider SA framework sits at the Software Assurance benefits spoke; the wider Azure MACC framework sits at the Azure MACC design spoke.
Windows Server is consistently in the top two Microsoft SAM-audit scopes (alongside SQL Server). The audit examines four principal axes: the per-host inventory (every host, every processor, every core, every Windows OSE), the edition declaration against virtualisation density (Datacenter where density justifies; Standard where density does not, with stacking reconciled), the SA position (every core licence, every SA term-end), the CAL reconciliation (every user-or-device CAL count against the actual access population).
The frequent false-positive patterns: a Standard-licensed host running more Windows VMs than the stacked OSEs cover (under-licensed; requires either Datacenter migration or additional Standard stacking); a Datacenter host that has been re-clustered such that a Standard-licensed neighbour host has absorbed a portion of the Datacenter workload (the Datacenter unlimited-virtualisation right does not extend to the neighbour host); a CAL-count mismatch where the AD user population exceeds the User CAL inventory (or vice versa for Device CALs); a version-mismatch on the CAL surface (Server 2022 hosts accessed by Server 2019 CALs).
The buyer-side artefacts to hold against the Windows Server estate are: the per-host inventory (every host, every processor, every core, every Windows OSE, every edition), the edition declaration against density (Datacenter or Standard, with stacking reconciliation), the SA position (every core licence, every SA term-end, every license-mobility transition), the CAL reconciliation (User-or-Device CAL inventory against the AD access population, RDS CAL inventory against the RDS user population), the Azure Hybrid Benefit register (every on-prem SA licence applied to an Azure VM, every dual-use transition).
The renewal-time conversation is then a negotiation against artefacts. The publisher's renewal proposal carries the Windows Server SA renewal across the inventory; the buyer's decision is per-host, against the artefacts; the SA drops, the SA retentions, the Datacenter-versus-Standard rebalancing, the Hybrid Benefit applications and the CAL-class transitions are taken on shared arithmetic.
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 wider SAM audit framework sits at the SAM audit anatomy spoke; the wider True-Up framework sits at the True-Up mechanics spoke; the wider SQL Server framework sits at the SQL Server licensing spoke.
The database tier that most often runs on top of the Windows Server estate.
The SA-mediated bridge from on-prem Windows Server to the Azure VM estate.
The audit phases against which the per-host inventory is the principal posture.
A senior Admodum Microsoft advisor will read your per-host inventory, your Datacenter-versus-Standard density, your SA position and your Hybrid Benefit application against your renewal and audit posture on a private call. Active audit moments route to Audit Defence.