Windows Server licensing is built on two interlocking mechanisms: core-based server licences that cover the right to run the operating system on physical hardware, and Client Access Licences (CALs) that cover the right of users or devices to connect to that server. Getting either mechanism wrong leads to compliance exposure in audits and unnecessary cost in renewals. This guide covers every Windows Server licensing model in current use.
This guide is the foundation of our Windows Server licensing series. For detailed core mechanics, see Core-Based Licensing Mechanics. For virtualisation rights, see Virtualisation & Container Licensing. For hybrid cloud benefits, see Hybrid Cloud & Azure Benefits. For the full SAM guide, see Mastering Windows Server Licensing.
Since Windows Server 2016, Microsoft has used a core-based licensing model, replacing the older per-processor approach. Under this model, every physical core on a server must be licensed. Licences are sold in 2-core packs (with optional 16-core packs for convenience), subject to two mandatory minimums: 16 cores per physical server and 8 cores per physical CPU. A small single-socket server with only 4 physical cores still requires 16 core licences to be compliant. Once all physical cores are licensed, the server's Windows Server OS is covered for use on that hardware.
| Edition | Licensing Model | Virtualisation Rights | CAL Requirement | Best For |
|---|---|---|---|---|
| Standard | Core-based (2-core packs, 16-core minimum per server) | Up to 2 VMs per set of core licences; stack additional sets for more | Yes: User or Device CALs required | Low-density virtualisation, non-virtualised servers |
| Datacenter | Core-based (same mechanics as Standard) | Unlimited VMs on a fully licensed host | Yes: same CAL requirements as Standard | Dense virtualisation, private cloud, software-defined datacentre |
| Essentials | Single server licence, OEM only, up to 10 cores | None: covers one OS instance on one physical server | No CALs required: allows up to 25 users and 50 devices | Very small businesses (25 users or fewer), single-server |
| Azure Edition | Available only in Azure or Azure Stack with SA | Follows Azure VM licensing model | Azure-style billing: no traditional CALs | Cloud-native features (Hotpatch, SMB over QUIC), hybrid Azure |
Standard allows 2 VMs per set of core licences. If you need more VMs, purchase additional sets of core licences for the same server. A server with 20 physical cores needing 6 VMs requires 3 sets of 20-core licences (3 x 20 = 60 core licences). Beyond 4 VMs on a single host (2 stacks), the economics typically favour switching to Datacenter. Calculate the breakeven: if the cost of 3+ Standard stacks exceeds one Datacenter licence for the same core count, Datacenter is the better investment.
Datacenter is more expensive per core but scales VM count without additional licences. For highly virtualised environments, this dramatically simplifies both cost and compliance management. Datacenter also includes advanced features in newer versions: software-defined networking, storage spaces direct, shielded VMs, and other datacentre-class capabilities not available in Standard. See Core-Based Licensing Mechanics for detailed calculations.
Licensed as a single OEM SKU tied to one server (up to 10 cores), Essentials allows 25 named users and 50 devices without CALs. It runs Standard edition binaries with an enforced user limit: the server shuts down if the cap is exceeded. Essentials cannot be expanded beyond 25 users and has no virtualisation rights. It is available only through OEM channels bundled with new hardware. For very small offices, Essentials is the simplest and most cost-effective option.
Purchasing a Windows Server licence covers the server installation, but every user or device accessing the server requires a separate Client Access Licence. CALs are additive to the server licence and are one of the most commonly overlooked compliance requirements.
Choosing between User and Device CALs. You can mix both types, but each user or device needs one CAL of one type: they cannot be interchanged or double-counted. The optimal choice depends on your user-to-device ratio. If employees typically use 3-4 devices each, User CALs are far cheaper (1 CAL per person vs 3-4 Device CALs). If a factory has 50 shared workstations used by 200 shift workers, 50 Device CALs are cheaper than 200 User CALs. Review your CAL strategy annually or when workforce/device policies change.
CAL version requirements. CALs are version-specific: a Windows Server 2019 CAL covers access to Server 2019 and earlier versions, but not Server 2022 or newer. When upgrading server versions, you must also upgrade CALs, or maintain Software Assurance on CALs to access the latest versions automatically.
No CALs are needed for servers used purely as back-end infrastructure (virtualisation hosts running only Hyper-V, not providing file/print/authentication services to users), for anonymous public web access, or for certain HPC cluster scenarios with no direct user login. Always verify specific exceptions in Microsoft's Product Terms.
The base Windows Server CAL covers core OS services. Remote Desktop Services (RDS) for VDI or remote app access requires additional RDS CALs on top of base CALs. Active Directory Rights Management Services requires its own CAL. Budget for and track these additional CALs as closely as base CALs. See Mastering Windows Server Licensing.
Understanding how Windows Server licensing has evolved helps organisations manage legacy environments and plan for future changes.
| Era | Model | How It Worked | Current Status |
|---|---|---|---|
| Pre-2003 | Per-server or per-seat | Choose between licensing the server for a fixed number of concurrent connections, or licensing each client device | Legacy: no longer available |
| 2003-2012 R2 | Per-processor + CALs | One server licence covered up to 2 CPUs; CALs required for users/devices | Legacy: still in use for old installations but not available for new purchases |
| 2016-present | Per-core + CALs | Licence every physical core (16-core minimum, 8 per CPU); CALs required for users/devices | Current standard: applies to WS2016, 2019, 2022, and 2025 |
| 2025+ | Subscription / pay-as-you-go (optional) | Azure Arc-enabled per-core usage billing; no CALs required; Azure subscription charges | Emerging: available for Windows Server 2025 via Azure Arc alongside traditional perpetual |
The shift to per-core licensing in 2016 aligned server licensing with actual compute capacity as CPU core counts increased. Microsoft also introduced subscription options via CSP and Azure-based licensing, which use the same core metrics but offer different purchasing and billing models. Azure Arc pay-as-you-go for Windows Server 2025 represents the latest evolution: usage-based billing with no CAL requirement. See Hybrid Cloud & Azure Benefits for details on subscription and hybrid models.
Windows Server licensing errors are among the most frequent findings in Microsoft audits. Understanding these pitfalls prevents both compliance exposure and unnecessary cost.
| Pitfall | What Goes Wrong | How to Avoid It |
|---|---|---|
| Under-licensing cores | Forgetting the 16-core minimum or not licensing all physical cores. A 12-core server with only 12 cores of licences is non-compliant. Hardware upgrades without licence adjustments create gaps. | Always licence at least 16 cores per server and 8 per CPU. Include licensing in hardware change management. Document and reconcile after every upgrade. |
| Over-stacking Standard | Buying multiple Standard stacks for heavy virtualisation instead of switching to Datacenter. Beyond 4 VMs per host, Standard typically costs more while adding complexity. | Calculate the Standard vs Datacenter breakeven for each host. If stacking beyond 2 sets, evaluate Datacenter. Model costs before committing. |
| Ignoring CALs | Budgeting for server licences but forgetting CALs. Every internal user or device accessing Windows Server needs a CAL unless covered by an exception or bundled licence. | Include CAL purchases in every server deployment budget. Maintain a CAL inventory tracked as closely as server licences. Audit CAL counts annually. |
| Wrong CAL type | Defaulting to Device CALs when users have 3-4 devices (3-4x overspend), or buying User CALs for shared workstations (paying per worker instead of per device). | Analyse your user-to-device ratio. Choose the CAL type that produces the lower count. Review annually when workforce or device policies change. |
| Licence reassignment violations | Moving licences between servers more frequently than every 90 days without SA. Dynamic VM migration for HA or load balancing without ensuring destination hosts are fully licensed. | Plan licence assignments for 90-day minimum tenure. Invest in SA for environments requiring frequent reassignment. Ensure all potential failover hosts are licensed. |
The most common Windows Server audit findings are under-licensed cores (particularly the 16-core minimum on small servers), missing CALs for internal users, and Standard Edition stacking that exceeds the Datacenter breakeven point. A systematic annual review, reconciling physical core counts against licence entitlements and CAL allocations against Active Directory user counts, prevents the vast majority of compliance issues before they become audit findings.