Windows Server 2025 Licenses Cores. Standard Gets Two OSEs.

You opened a 2025 licensing URL. Keep it. Windows Server 2025 is the current commercial version. The Product Terms for Windows Server (EA/EAS/SCE) list Windows Server 2025 Standard and Datacenter as 2-packs and 16-packs of Core Licenses, date available 11/24. Prior version is Windows Server 2022 (8/21).

The core metric did not flip from 2022. What changed is how you buy burst capacity and how you patch: pay-as-you-go through Azure Arc, and Hotpatch on Arc-enabled 2025 Standard or Datacenter. The 2022 spoke stays at the Windows Server 2022 licensing guide. Version-to-version comparison stays at Windows Server 2022 vs 2025. This URL is the 2025 metric.

That’s the problem.

A host list of Windows installs is not a position. Edition, physical cores versus vCores, whether Software Assurance or a subscription sits on the paper, whether the instance is a physical OSE, a VM, or a Hyper-V isolated container, and whether users still need CALs are different objects. Mix them and you either stack Standard until it costs more than Datacenter, or you brief unlimited VMs you do not have.

Do not invent a list price. Your number is the quote, the MLS, or the CSP subscription in front of you.

Standard, Datacenter, Essentials

Microsoft’s Windows Server 2025 licensing guidance and the Windows Server licensing resources page split three editions.

Do not brief Shielded Virtual Machines as a Standard feature. Microsoft’s edition table grants Shielded VMs to Datacenter, not Standard. Storage Replica on Standard is limited to a single volume up to 2 TB. Software-defined networking is Datacenter.

PAYG is not “unlimited virt.” The product-licensing page footnotes unlimited OSEs as not applying to a pay-as-you-go subscription.

Physical cores: eight per processor, sixteen per server

When you license the physical box, you license all physical cores on the server. Product Terms and the 2025 licensing guidance:

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

That 16-core floor is Windows Server. It is not a SQL Server rule. Do not import it onto a SQL true-up.

Core-based licensing models: software partitioning or BIOS disabling does not shrink the count. Volume Licensing guidance still tells you to license disabled cores. Retail and OEM terms can exempt cores the manufacturer disabled. They do not drop the 8/16 floors.

Core licenses are sold as 2-packs and 16-packs. Product Terms list both for 2025 Standard and Datacenter.

Worked shapes from Microsoft’s own table:

• 1 processor, 4 cores: 16 core licenses
• 2 processors, 6 cores each: 16 core licenses (both floors bind)
• 2 processors, 10 cores each: 20 core licenses
• 4 processors, 8 cores each: 32 core licenses

A one-socket box still needs 16 cores. A two-socket box with eight cores per socket is 16 cores, one 16-pack.

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

Product Terms, Standard, physical cores: two OSEs on the licensed server. You may also run the software in the physical OSE if that physical OSE is used solely to host and manage the virtual OSEs.

Need more VMs? Stack. Assign another full set of core licenses equal to the physical-core requirement, get two more OSEs. Microsoft’s stacking table: a 16-core Standard host covering 6 OSEs needs 48 core licenses.

Datacenter on a fully licensed physical server: unlimited OSEs on that server. That grant is the edition, not a “13 VM” Product Terms trigger. Microsoft’s planning language still points Datacenter at highly virtualized hosts. The old “13 OSEs and Datacenter wins” line is a price heuristic from list-price ratios. It is not a use right. Compare your quote, not a folklore crossover.

Peak capacity matters. Windows Server virtualization licensing guidance: if you occasionally run more than two Standard OSEs at the same time, you license for the peak. Physical-core licenses do not move with the VM on a short-term basis.

If the hypervisor is bare metal (ESXi or similar), you are not running Windows Server in the physical OSE. Guest Windows Server still needs licenses assigned to that server, either physical cores or by VM with SA or a subscription. Do not invent a VMware product URL for that topology. Infrastructure Mapper is the host-to-VM file.

Licensing by virtual machine is not the default

October 2022 added VM licensing. 2025 guidance and Product Terms: subscription licenses or licenses with active Software Assurance only. CALs used to access software under this model must also be subscription or have SA.

How to count a VM:

1. Count virtual cores in that virtual OSE.
2. Minimum 8 core licenses per VM.
3. Minimum 16 core licenses per customer when you elect this model.
4. Sold in 2-packs and 16-packs.
5. One OSE (or one Hyper-V isolated container) per licensed VM. Unlimited Windows Server containers without Hyper-V isolation inside that licensed VM.

No physical OSE rights on the VM path. If Windows Server is the host OS, the host still needs physical-core licenses. VM licensing is the guest path, or the way to add a few extra VMs on a Standard host without stacking the whole box.

With SA or a subscription, you may reassign those VM-allocated licenses across servers in the same server farm as often as needed. Across farms: not on a short-term basis (not within 90 days of the last assignment).

Containers are not a free edition upgrade

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

Windows Server containers with Hyper-V isolation: each one is a virtual OSE. Standard: two (plus stacking). Datacenter: unlimited. VM licensing: one per licensed VM.

CALs still sit on top of the cores

Per Core/CAL means cores plus access licenses. 2025 guidance and Product Terms:

• Windows Server CAL, User or Device, for each user or device that accesses the server, including multiplexed access.
• External Connector on each physical server that external users access, instead of CALs for those externals. External users are not your (or your affiliates’) employees, onsite contractors, or onsite agents.
• Additive CALs and ECs: Remote Desktop Services, Active Directory Rights Management Services, Microsoft Identity Manager. RDS is also required to host a graphical user interface via RDS (or similar).
• Version: a 2025 CAL or EC accesses 2025, 2022, and 2019. A 2022 CAL does not access 2025.

CAL exceptions (Product Terms and 2025 guidance):

• Access by another licensed server.
• Web workload or HPC workload.
• Access in a physical OSE used solely for hosting and managing virtual OSEs.
• Users accessing solely to sync Active Directory on your licensed servers with Microsoft Entra ID.

Essentials does not use the Windows Server CAL for base access. ADRMS on Essentials still needs the additive CAL.

Pay-as-you-go is different. See below.

Windows Server on Azure: base Windows Server CALs are not required. RDS CALs still are if you use that functionality.

What 2025 actually changed

Keep these as 2025 facts, not as if they were always the 2022 metric.

Pay-as-you-go, Azure Arc. Learn: Configure Windows Server Pay-as-you-go. Windows Server 2025 Standard or Datacenter, Arc-enabled, billed on an Azure subscription. Not for earlier versions. Not the licensing method for machines that already live on Microsoft Azure (Azure has other PAYG paths). Microsoft’s rules on this path:

• Cost is the same for Standard and Datacenter.
• No Windows Server CALs for standard functionality. RDS CALs are still required.
• The PAYG license covers that device only. It does not grant extra VMs on the host. Automatic Virtual Machine Activation is not available. Each VM needs its own license.
• First seven days after enablement are a trial. If you shut down the device without disabling PAYG, billing continues.

Do not paste a per-core hourly or monthly list price. Microsoft’s public pages change those figures. Your number is the Azure meter in front of you.

Hotpatch. Learn: Hotpatch and Arc-enabled Hotpatch. Security updates without a reboot in the hotpatch months. Azure Arc-enabled Hotpatch for Windows Server 2025 Standard and Datacenter is available at no extra cost. Datacenter: Azure Edition has Hotpatch on by default and does not need Arc for that. Product Terms: you may use Datacenter: Azure Edition only as an OS for virtualization on Microsoft Azure and Azure Stack. Hotpatch still needs virtualization-based security and Secure Boot. Baseline cumulative updates still reboot.

Azure Hybrid Benefit did not start in 2025. The coverage math is still the one in Windows Server licensing resources, Learn: Azure Hybrid Benefit, and the virtualization guidance:

• Qualifying core licenses with active SA or a qualifying subscription.
• Each set of 16 core licenses: up to 16 virtual cores across two or fewer Azure VMs (or one VM with up to 16 virtual cores). Each additional set of 8: up to 8 virtual cores and one VM.
• Standard: use on-premises or Azure, not both, except a one-time 180-day migration.
• Datacenter: dual use when licensing VMs in Azure (keep on-prem). Unlimited virtualization on an Azure dedicated host if you assign Datacenter cores for all physical cores on that host.
• Residual processor licenses, if you still hold them, convert as one processor license = 16 core licenses. 2025 SKUs are core packs, not processor packs.

Do not brief a made-up Azure saving percentage as the position.

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 edition rights. SA (or a subscription) is what adds:

• New version rights
• Step-up from Standard to Datacenter
• Disaster recovery backup instances (cold, with the testing and failover windows in the 2025 guidance)
• Azure Hybrid Benefit
• Flexible Virtualization Benefit
• Licensing by virtual machine, and reassignment of those VM licenses inside the server farm

Product Terms Software Assurance table: License Mobility is External Connector only. The Windows Server OS does not get License Mobility through Software Assurance. Microsoft’s Windows Server licensing FAQ says the same. The replacement for Authorized Outsourcers (shared or dedicated, not Listed Providers) is the Flexible Virtualization Benefit, with VM licensing if you need to move the guest.

Listed Provider clouds are a different file. Do not treat Flexible Virtualization as a free pass onto those providers.

What to have this week

Do this before the next true-up, EA amendment, or CSP quote. Produce a Windows Server pack, not a pasted Microsoft PDF.

1. Every host, edition, version, OSE type. Physical, VM, Hyper-V isolated container, Windows Server container. Azure Edition called out, not mixed into on-prem Datacenter.
2. Cores the way Microsoft counts them. Physical cores with the 8-per-processor and 16-per-server floors, or vCores per VM with the 8-per-VM floor and the 16-per-customer floor. One owner of the number. Infrastructure Mapper is the topology file.
3. Whether SA or a subscription sits on those licenses. That bit decides VM licensing, license movement, Azure Hybrid Benefit, Flexible Virtualization, and a step-up.
4. CALs. Users, devices, External Connectors, RDS / ADRMS / MIM additive, version (2025 versus 2022). PAYG boxes called out so you do not double-count base CALs they do not need.
5. What you own versus what you deployed. Microsoft Entitlements Manager is the MLS / entitlement side. Microsoft Deployment Manager is the SQL, Windows Server, and M365 requirement.

Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is “Standard includes unlimited VMs if we licensed the host” or “we do not need 2025 CALs because we have 2022 CALs”, you do not have a Windows Server position.

Picture your procurement director, sixty days out. Finance has this 2025 URL bookmarked. The quote walking in may already mix perpetual cores, CSP subscriptions, and Arc PAYG. None of those documents is the estate. The number is cores after the 8/16 floors, edition actually installed, OSE count, and whether SA is on the paper.

The decision layer, not another Windows inventory

You already have MAP, SCCM, or a CMDB full of Windows hosts. The gap is not another discovery export. The gap is turning that estate into a metric: edition, OSE type, cores Microsoft will count, SA yes or no, CAL population. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. MDM is the deployment file. MEM is the entitlement file. LCM is the renewal file.

If you are heading into a Windows Server true-up or a 2022-to-2025 conversation and your current tools still need three weeks to separate Standard hosts that need stacking from Datacenter hosts that do not, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.

Do not let the vendor frame this as “just buy Datacenter, unlimited virt is included” without counting the cores on that host. Do not let your own side frame the 16-core-per-server floor as a SQL rule, or treat a 2022 CAL as a 2025 access license. The right question is: which edition, how many cores after the 8-per-processor and 16-per-server floors, how many OSEs, is this a VM that needs SA, and what does the paper actually grant. That is a data question, not a sales question.

The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.

Sources

• Windows Server 2025 licensing guidance (8/16 floors, editions, stacking, CALs, PAYG pointer, downgrade): https://www.microsoft.com/licensing/guidance/Windows-Server-2025
• Windows Server licensing resources (editions table, Shielded VMs Datacenter-only, 2-packs and 16-packs, AHB 16/8 math, no License Mobility through SA for the OS, PAYG CAL note): https://www.microsoft.com/en-us/licensing/product-licensing/windows-server
• Product Terms, Windows Server Standard / Datacenter / Essentials, EA/EAS/SCE (2025 availability 11/24; prior version 2022 8/21; Per Core/CAL; VM licensing; Entra ID sync exception; Azure Edition restriction; SA License Mobility = External Connector only): https://www.microsoft.com/licensing/terms/productoffering/WindowsServerStandardDatacenterEssentials/EAEAS
• Core-based licensing models (Per Core/CAL vs SQL Per Core; 8/16 floors; VM licensing 8 per VM and 16 per customer): https://www.microsoft.com/licensing/guidance/Core-based-licensing-models
• Windows Server virtualization technologies (physical-core vs VM movement, ESXi guests, AHB 16-core Azure shapes, Flexible Virtualization, containers): https://www.microsoft.com/licensing/guidance/Windows-Server-Virtualization-Technologies
• Flexible Virtualization Benefit (Authorized Outsourcers, not Listed Providers; applies to Windows Server): https://www.microsoft.com/licensing/guidance/Flexible-Virtualization-Benefit
• Azure Hybrid Benefit for Windows Server (SA or subscription; Standard no dual use except 180 days; Datacenter dual use / dedicated-host unlimited virt; 8-core VM floor on Azure): https://learn.microsoft.com/en-us/windows-server/get-started/azure-hybrid-benefit
• Configure Windows Server Pay-as-you-go with Azure Arc (2025 only; no extra VM rights; no base CALs, RDS CALs remain; same cost Standard and Datacenter; 7-day trial): https://learn.microsoft.com/en-us/windows-server/get-started/windows-server-pay-as-you-go
• Hotpatch for Windows Server (Azure Edition images; Arc-enabled 2025 Standard/Datacenter at no extra cost): https://learn.microsoft.com/en-us/windows-server/get-started/hotpatch
• Enable Hotpatch for Azure Arc-enabled servers (VBS/Secure Boot; Azure Edition does not need Arc): https://learn.microsoft.com/en-us/windows-server/get-started/enable-hotpatch-azure-arc-enabled-servers
• Listed Providers (do not treat FVB as a pass onto these clouds): https://aka.ms/listedproviders