Windows Server 2025 Licenses Cores. Standard Gets Two OSEs.

Windows Server 2025 Standard and Datacenter are licensed per core plus CAL: you license every physical core in the server, with a minimum of 8 core licenses per processor and 16 per server, and every user or device that accesses it needs a Windows Server 2025 CAL. Standard covers two virtual machines (OSEs) per fully licensed server; Datacenter covers unlimited VMs on that server. At Microsoft’s list prices a host running 11 or more Windows Server VMs is cheaper on Datacenter.

Windows Server 2025 has been available in volume licensing since November 2024 (the Product Terms for Windows Server list it from 11/24, with Windows Server 2022 as the prior version). It follows Microsoft’s Fixed Lifecycle Policy, with mainstream support to November 14, 2029 and extended support to November 15, 2034 (Microsoft Lifecycle). The dates for every release side by side are in our Windows Server versions and lifecycle table.

The core metric did not change from 2022. What 2025 added is a way to buy capacity by the month (pay-as-you-go through Azure Arc) and Hotpatch for on-premises Standard and Datacenter through Azure Arc. This guide covers the rules and how to license real hosts. The full version-to-version price table is in the Windows Server 2025 price comparison; older estates are covered in the Windows Server 2022 licensing guide.

What Windows Server 2025 costs at list price

Microsoft’s Windows Server pricing page gives a suggested list price (USD, checked October 2026) of $1,176 for Standard and $6,771 for Datacenter, each for 16 core licenses, the minimum for one server. Pay-as-you-go through Azure Arc is $33.58 per core per month ($0.046 per hour). Microsoft does not print CAL prices on that page.

These are reference prices. Microsoft says they vary by country, and what you pay depends on the channel (CSP, Enterprise Agreement, OEM, retail) and your agreement. Use them to compare options, not as a quote. For per-core arithmetic below, Standard works out at $73.50 per core and Datacenter at about $423.19 per core.

Standard, Datacenter, Essentials

Microsoft’s Windows Server 2025 licensing guidance and the Windows Server licensing resources page describe three editions you can buy for your own servers. A fourth, Datacenter: Azure Edition, may only be used on Microsoft Azure and Azure Stack.

Datacenter-only features in 2025, per Microsoft’s edition comparison and licensing page: Storage Spaces Direct, the Network Controller for software-defined networking, Host Guardian Hyper-V support (shielded VMs) and unlimited Storage Replica. Standard has Storage Replica limited to a single volume of up to 2 TB.

Unlimited virtualization belongs to a Datacenter license on physical cores. Microsoft’s licensing page footnotes that it does not apply to pay-as-you-go.

Physical cores: eight per processor, sixteen per server

When you license a physical server, you license all of its physical cores, subject to two floors in the Product Terms:

• Minimum 8 core licenses per physical processor
• Minimum 16 core licenses per server

Core licenses are sold in 16-packs and 2-packs. A “Windows Server 2025 Standard 16 core license pack” is one server’s minimum; 2-packs top up servers with more than 16 cores. The 16-core floor is a Windows Server rule. SQL Server has its own minimums (see the SQL Server 2025 licensing guide).

The shapes with 4, 10, 20 and 40 cores come from Microsoft’s own table in the 2025 guidance; the others apply the same two floors.

Standard is two OSEs, not “license the host and run whatever”

A Standard license covering all physical cores allows two OSEs on that server. You may also run Windows Server in the physical OSE if it is used only to host and manage those virtual OSEs (Product Terms).

For more VMs you stack: assign another full set of core licenses for the server and you get two more OSEs. Microsoft’s table for a 16-core host:

License for the peak. The virtualization guidance says that if you occasionally run more than two Standard OSEs at the same time, you must license for that peak. Licenses on physical cores cannot be reassigned on a short-term basis; generally they move to new hardware only after 90 days. A VM that live-migrates onto a host needs that host to be licensed for it already.

If the hypervisor is not Windows (VMware ESXi, for example), Windows Server is not in the physical OSE, but every Windows Server guest still needs licenses: either the host’s physical cores, or licensing by VM with Software Assurance or a subscription.

Standard or Datacenter: the break-even

Both editions are priced per core, so the comparison scales with the host. At list price, one Standard set for a host costs 1,176 ÷ 6,771 = about 17.4% of Datacenter for the same cores. Datacenter therefore costs about 5.76 Standard sets. Five sets (10 VMs) are cheaper than Datacenter; six sets (11 or 12 VMs) are not.

Worked example: a 2-socket, 32-core host

A server with two 16-core processors needs 32 core licenses, which is two 16-packs per edition.

So at list price Datacenter wins from 11 VMs, on any host size. Your break-even moves with your actual discount on each edition, and with cluster design: on a cluster where VMs can fail over to any node, each node must be licensed for the peak it may run, which pushes clustered hosts towards Datacenter sooner.

Count Windows Server VMs only. Linux guests on the same host do not consume Windows Server OSEs.

Licensing by virtual machine is not the default

You can also license an individual VM instead of the host. The 2025 guidance and the Product Terms allow it only for subscription licenses or licenses with active Software Assurance, and CALs used to access software under this model must also be subscription or have SA.

• License every virtual core in the VM, with a minimum of 8 core licenses per VM.
• Microsoft’s core-based licensing guidance also requires at least 16 core licenses (subscription or with SA) if you choose this model.
• Each licensed VM covers one OSE, or one Hyper-V isolated container, plus unlimited Windows Server containers without Hyper-V isolation inside it.
• Licenses can be reassigned between servers in the same server farm as often as needed; between farms, not within 90 days of the last assignment.

There are no physical OSE rights on this path. If Windows Server is the host OS, the host still needs physical-core licenses.

Worked example: three VMs on a shared VMware cluster

VMs with 4, 8 and 12 virtual cores need 8 + 8 + 12 = 28 core licenses with SA or a subscription (the 4-core VM rounds up to the 8-core minimum). They can move with the VMs across the cluster. Licensing the same three VMs on physical cores would mean licensing every host they could run on.

Containers are not a free edition upgrade

Windows Server containers without Hyper-V isolation share the host kernel and are unlimited on Standard and Datacenter when the server is licensed on physical cores.

Containers with Hyper-V isolation each count as an OSE: two on Standard (more by stacking), unlimited on Datacenter, one per VM when licensing by VM.

CALs still sit on top of the cores

Per core plus CAL means both. The 2025 guidance and Product Terms require:

• A Windows Server CAL, per user or per device, for each user or device that accesses the server, directly or through multiplexing.
• An External Connector on each physical server that external users access, as an alternative to CALs for them. External users are people who are not your or your affiliates’ employees, onsite contractors or onsite agents.
• Additive CALs for Remote Desktop Services (also required to host a graphical desktop for users) and Active Directory Rights Management Services; Microsoft Identity Manager uses its own CAL.

CAL version. A CAL accesses the same or earlier versions. A 2025 CAL accesses 2025, 2022 and 2019 servers. A 2022 CAL does not access 2025, so the first 2025 server in a domain that users touch brings a CAL upgrade with it.

CALs are not needed for access by another licensed server, for web or HPC workloads, for access to a physical OSE used only to host and manage VMs, or for users who only synchronize Active Directory with Microsoft Entra ID. Some subscriptions count as CAL equivalents, including the Core CAL and Microsoft 365 E3/E5 user licenses.

What 2025 actually changed

Pay-as-you-go through Azure Arc

Pay-as-you-go licenses an Arc-enabled Windows Server 2025 Standard or Datacenter machine outside Azure and bills it to your Azure subscription. It is not available for earlier versions or for machines on Azure itself, and the machine must not already be activated with another license.

• The cost is the same for Standard and Datacenter.
• No Windows Server CALs are needed for standard functionality. RDS CALs still are.
• The license covers only that machine. It gives no rights to VMs on the host, Automatic Virtual Machine Activation is not available, and each VM needs its own license.
• The first seven days are a free trial. If you shut down or deprovision the machine without disabling pay-as-you-go, billing continues.

At $33.58 per core per month, 16 billed cores cost $537.28 a month, or $6,447.36 a year. That is more than a 16-core Standard license ($1,176) after about 2.2 months. Pay-as-you-go suits short-lived or seasonal servers and capacity you cannot plan, not steady workloads.

Hotpatch

Hotpatch installs security updates without a restart in the two months between quarterly baseline updates, which still need one. Microsoft says Azure Arc-enabled Hotpatch for Windows Server 2025 Standard and Datacenter is now available at no extra cost. Datacenter: Azure Edition has Hotpatch built in on Azure and Azure Local.

Management through Azure Arc

Windows Server licenses with active Software Assurance or a subscription can enroll in Windows Server Management enabled by Azure Arc, which adds Azure Update Manager, change tracking and inventory and other tools at no extra license cost. Log ingestion, compute and storage may still be billed.

Azure Hybrid Benefit: the core math

Azure Hybrid Benefit lets core licenses with active SA or a qualifying subscription cover Windows Server VMs on Azure, so you pay the base compute rate. The licensing page sets the coverage:

• Each set of 16 core licenses covers up to 16 virtual cores across two or fewer VMs.
• Each additional set of 8 covers up to 8 more virtual cores and one more VM.
• Every VM needs at least 8 core licenses, so a 4-core VM still uses 8.
• Standard: on-premises or Azure, not both, except a one-time 180-day migration window.
• Datacenter: licenses used for VMs on Azure can stay in use on-premises. On an Azure dedicated host, Datacenter licenses for all of its physical cores give unlimited VMs; there the dual use is limited to 180 days.
• A processor license, if you still hold one, counts as 16 core licenses.

Example: 24 core licenses with SA cover two 8-core VMs (first 16) plus one more 8-core VM (the next 8). Two 16-packs can instead cover one VM of up to 32 virtual cores, as the virtualization guidance shows.

Software Assurance is the switch for movement, not for the two OSEs

Standard’s two OSEs and Datacenter’s unlimited OSEs on a physically licensed host are base rights of the edition. SA (or a subscription) adds:

• New version rights
• Step-up from Standard to Datacenter (not through Open License)
• Disaster recovery backup instances on dedicated DR servers or Azure: testing for one week every 90 days, and running while the production server is down
• Azure Hybrid Benefit
• The Flexible Virtualization Benefit for Authorized Outsourcers
• Licensing by VM, with reassignment inside a server farm

License Mobility through SA does not apply to the Windows Server OS; the Product Terms list it for the External Connector only. To run Windows Server on an outsourcer’s shared servers, the route is the Flexible Virtualization Benefit, which excludes Listed Providers.

Downgrade and down-edition rights

You do not need to buy 2022 licenses to run 2022. The 2025 guidance lets a 2025 Datacenter license run Datacenter, Standard or Essentials of version 2022 or earlier, and a 2025 Standard license run Standard or Essentials of 2022 or earlier. Use rights stay those of the edition you licensed: Standard running 2022 still gets two OSEs. CALs follow the server version: users of a 2022 server can use 2022 or 2025 CALs.

What to have this week

Before the next true-up, Enterprise Agreement amendment or CSP quote, put together a Windows Server position, not a pasted Microsoft PDF.

1. Every host, edition, version and OSE type. Physical, VM, Hyper-V isolated container, Windows Server container. Azure Edition kept apart from on-premises Datacenter.
2. Cores the way Microsoft counts them. Physical cores after the 8-per-processor and 16-per-server floors, or virtual cores per VM with the 8-per-VM floor.
3. Peak OSEs per host or cluster, not the average, for every Standard host.
4. Whether SA or a subscription covers each license. It decides licensing by VM, license movement, Azure Hybrid Benefit, DR rights and step-up.
5. CALs. Users, devices, External Connectors, RDS and AD RMS, and the version: 2022 CALs do not reach a 2025 server. Pay-as-you-go machines called out so you do not count base CALs they do not need.

LICENSEWARE’s Microsoft Deployment Manager builds this from your inventory data, calculating the Windows Server and SQL Server license requirement per host.

If you also manage these hosts with System Center, its rules are in the System Center 2025 licensing guide.

Questions

How much does a Windows Server 2025 license cost?

At Microsoft’s suggested list price, $1,176 for Standard and $6,771 for Datacenter per 16 cores, plus CALs. Pay-as-you-go is $33.58 per core per month. Real prices vary by country, channel and agreement.

What is the Windows Server 2025 Standard 16 core license pack?

Sixteen Standard core licenses in one SKU: the minimum for any physical server. It covers a server with up to 16 physical cores (and at least 8 per processor) for two OSEs. Larger servers add 2-packs or further 16-packs.

How many cores do I license on a 32-core server?

All 32. A 2-socket server with 16 cores per processor needs 32 core licenses, two 16-packs, for each set of two Standard OSEs, or once for Datacenter.

How many VMs can I run on Windows Server 2025 Standard?

Two per full set of core licenses. Four VMs on a 16-core host need 32 Standard core licenses, six need 48. Datacenter covers unlimited VMs on the licensed server.

Can Windows Server 2022 CALs access Windows Server 2025?

No. A CAL accesses its own version and earlier. Users and devices reaching a 2025 server need 2025 CALs, which also cover 2022 and 2019 servers.

Can I run Windows Server 2022 with a 2025 license?

Yes. Downgrade rights let 2025 Standard and Datacenter licenses run 2022 or earlier, under the rights of the edition you bought.

Sources

• Windows Server pricing (list prices, 16-core basis, pay-as-you-go rate, CAL requirement; checked October 2026): https://www.microsoft.com/en-us/windows-server/pricing
• Windows Server 2025 licensing guidance (editions, Essentials limits, core floors, stacking table, VM licensing, CAL versions and exceptions, downgrade rights, DR, SA benefits): https://www.microsoft.com/licensing/guidance/Windows-Server-2025
• Windows Server licensing resources (edition features, 2-packs and 16-packs, unlimited virtualization not for pay-as-you-go, Azure Hybrid Benefit math, no License Mobility for the OS): https://www.microsoft.com/en-us/licensing/product-licensing/windows-server
• Product Terms, Windows Server Standard, Datacenter and Essentials (availability, OSE rights, licensing by VM, CALs, Entra ID sync exception, Azure Edition restriction, SA benefits, down-edition rights): https://www.microsoft.com/licensing/terms/productoffering/WindowsServerStandardDatacenterEssentials/EAEAS
• Core-based licensing models (core floors, 8 per VM and at least 16 when licensing by VM): https://www.microsoft.com/licensing/guidance/Core-based-licensing-models
• Windows Server virtualization technologies (peak licensing, 90-day reassignment, non-Windows hypervisors, containers, VM mobility, Azure Hybrid Benefit example): https://www.microsoft.com/licensing/guidance/Windows-Server-Virtualization-Technologies
• Flexible Virtualization Benefit: https://www.microsoft.com/licensing/guidance/Flexible-Virtualization-Benefit
• Azure Hybrid Benefit for Windows Server: https://learn.microsoft.com/en-us/windows-server/get-started/azure-hybrid-benefit
• Configure Windows Server pay-as-you-go with Azure Arc: https://learn.microsoft.com/en-us/windows-server/get-started/windows-server-pay-as-you-go
• Hotpatch for Windows Server: https://learn.microsoft.com/en-us/windows-server/get-started/hotpatch
• Comparison of Windows Server editions: https://learn.microsoft.com/en-us/windows-server/get-started/editions-comparison
• Windows Server 2025 lifecycle: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2025
• Listed Providers: https://aka.ms/listedproviders