Windows Server Licensing: Core Packs, CALs & Costs

Before buying licenses or Windows Server support, you need three numbers: physical core count, VM count, and user count. Those three determine the entire licensing cost. This page documents the core-based model, Standard vs Datacenter rights, CAL requirements, and Microsoft's published prices for Windows Server 2025.

The core-based model

Since Windows Server 2016, both Standard and Datacenter editions are licensed per physical core, subject to two minimums stated on Microsoft's Windows Server licensing page:

• All physical cores in the server must be licensed. Disabling cores in firmware does not reduce the count in practice; audits count what the hardware has.
• Minimum 8 core licenses per physical processor. A 6-core CPU still needs 8 core licenses.
• Minimum 16 core licenses per server. A single-socket 8-core server still needs 16.

When licensing individual virtual machines instead of hosts (a Standard-edition option), each virtual core needs a license, with a minimum of 8 per VM.

2-core and 16-core packs

Core licenses sell in two SKU sizes: packs of 2 and packs of 16. A 16-core pack covers the minimum for one single- or dual-processor server; 2-core packs top up servers with more cores. A dual-processor server with 12 cores per socket (24 total) takes one 16-core pack plus four 2-core packs.

Standard vs Datacenter

The two editions are nearly identical in features. The price gap buys virtualization rights.

Standard stacking: a fully licensed Standard server grants rights to two VMs (plus the host OS when it does nothing beyond hosting). Each additional pair of VMs requires licensing all physical cores of the server again. Six VMs on one host means three full sets of Standard core licenses. Datacenter licenses the cores once for unlimited VMs; the crossover between the editions on one host sits at roughly 10–12 VMs at current prices.

Published pricing

Microsoft's Windows Server pricing page lists suggested MSRP for Windows Server 2025, in USD:

Both editions require Windows Server CALs. Microsoft does not publish CAL unit prices on the pricing page; CALs transact through resellers and volume agreements, and street prices vary by channel. Actual license prices also vary by country and agreement — EA, CSP, and Open Value all price differently from MSRP, but the Standard-to-Datacenter ratio (about 5.8:1 per core) holds, so the edition math below is channel-independent.

CALs

Core licenses cover the server. Access requires Client Access Licenses on top, per Microsoft's CAL licensing page:

• User CAL or Device CAL. One per user, or one per device, whichever counts lower for your environment. Office staff with multiple devices favor User CALs; shared shift workstations favor Device CALs. Mixing is allowed.
• RDS CALs are separate and additive. Remote Desktop Services sessions require an RDS CAL per user or device in addition to the base Windows Server CAL. The same additive pattern applies to Active Directory Rights Management Services CALs.
• External Connector. For servers accessed by external users you cannot count (customers, business partners), an External Connector license per server replaces individual CALs for those external users.
• Pay-as-you-go waives base CALs but RDS CALs are still required for RDS workloads.

CALs are version-specific: a Windows Server 2022 CAL does not cover a 2025 server, while a 2025 CAL covers 2022 and earlier (downgrade direction only).

Pay-as-you-go via Azure Arc

Windows Server 2025 can run without perpetual licenses by connecting the machine to Azure Arc with pay-as-you-go billing: $33.58 per physical core per month, or $0.046 per core per hour, billed to an Azure subscription. At the 16-core minimum that is $537.28/month — it overtakes a perpetual Standard license (16 cores, $1,176) in just over two months, so it fits short-lived, seasonal, or lab servers, not steady-state production.

Azure Hybrid Benefit and Software Assurance

Software Assurance adds, on top of the license, rights that matter for Windows Server: new-version rights, license mobility, disaster-recovery server rights, and eligibility for Azure Hybrid Benefit. Azure Hybrid Benefit lets Windows Server licenses with active SA (or subscription licenses) cover the OS cost of Azure VMs, so you pay the Linux base compute rate instead of the Windows rate. Each set of 16 Standard core licenses covers one Azure instance up to 8 cores or two up to 8 cores each with Standard's assignment rules; Datacenter licenses may be used both on-premises and in Azure simultaneously. SA is also the path to Extended Security Updates at no extra charge in Azure when a version reaches end of support — see Windows Server 2022 and Windows Server 2025 for the support dates.

Common licensing mistakes

• Hardware refresh adds cores, licenses do not follow. A host replaced 16-core to 32-core still carries 16 core licenses; every VM-pair set on Standard must be re-counted at 32.
• Missing CALs entirely. The server was bought with core licenses and deployed; nobody bought CALs. Every AD-joined user reaching a file share, print queue, or DHCP lease needs one.
• Missing RDS CALs. The 120-day RDS grace period expires, someone installs a licensing server with base CALs only, and sessions keep working while unlicensed.
• Standard VM count drift. A host licensed for one set of Standard rights (2 VMs) accumulates 4–6 VMs over the years with no additional core sets.
• Counting vCPUs instead of physical cores when licensing the host, or ignoring the 8-per-VM minimum when licensing by VM.
• Reassigning licenses between hosts more often than once per 90 days without SA (license mobility).
• External users on a public-facing server covered by neither CALs nor an External Connector.

Worked example: one virtualization host

Host: 2 processors, 12 cores each — 24 physical cores (verify with (Get-CimInstance Win32_Processor).NumberOfCores summed across sockets). Requirement: 6 Windows Server VMs.

Core count. 24 physical cores; both per-processor minimums (8 each = 16) and the 16-per-server minimum are exceeded, so the licensable count is 24.

Standard. One set of 24 core licenses = one 16-core pack + four 2-core packs, and grants 2 VMs. Six VMs need 3 sets = 72 core licenses. At MSRP, 16 cores cost $1,176, so one core is $73.50: 72 × $73.50 = $5,292.

Datacenter. One set of 24 core licenses, unlimited VMs. 24 × ($6,771 ÷ 16 = $423.19) = $10,156.50.

At 6 VMs Standard is cheaper. Datacenter overtakes at the 12th VM on this host (6 Standard sets = $10,584 > $10,156.50), before counting the operational cost of tracking Standard sets as VMs are added. CALs are identical under both editions and come on top.

Reference documents

• Windows Server pricing — microsoft.com (published MSRP and pay-as-you-go rates)
• Windows Server licensing — Microsoft Licensing (core minimums, pack SKUs, edition rights)
• Client Access Licenses and Management Licenses — Microsoft Licensing
• Windows Server 2025 editions comparison — Microsoft Learn
• Windows Server pay-as-you-go — Microsoft Learn
• Azure Hybrid Benefit — Microsoft Azure

FAQ

How much does Windows Server 2025 cost?

Microsoft's published MSRP is $1,176 for Standard and $6,771 for Datacenter, each covering 16 core licenses — the minimum for one server. Servers with more than 16 cores add 2-core packs. CALs are required on top and are priced through resellers.

Do I need a CAL for every user?

Every user or device that accesses the server directly or indirectly needs a Windows Server CAL, unless the server carries an External Connector license for external users, or runs under pay-as-you-go billing (which waives base CALs but not RDS CALs).

How many VMs does Windows Server Standard allow?

Two per full set of core licenses covering all physical cores. Each additional pair of VMs requires licensing every physical core again. Datacenter allows unlimited VMs after licensing the cores once.

What is the minimum number of core licenses?

8 per physical processor and 16 per server, whichever is greater. Licensing by VM (Standard) carries a minimum of 8 per virtual machine.