Windows Server 2025 Kept Per Core. Sixteen Cores Per Server.

You opened a 2022 versus 2025 comparison URL. Keep it. Windows Server 2025 is the current commercial version. Windows Server 2022 is still what a lot of estates run. They are not the same page.

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). New version rights still sit on Software Assurance or a subscription.

The 2022 metric stays at the Windows Server 2022 licensing guide. The 2025 metric stays at the Windows Server 2025 licensing guide. This URL is the delta: what Microsoft actually changed, and what it did not.

That’s the problem.

A feature matrix is not a license position. An invented 16-core list price is not a position. Mix Standard’s two OSEs into “one instance plus two VMs” and you brief the wrong grant. Paste a Datacenter hike as Product Terms and you walk into a quote with folklore instead of a file.

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

What did not flip

Microsoft’s Windows Server 2025 licensing guidance is written for 2025. The core model is the same one the core-based licensing models brief and the virtualization licensing guidance already taught for Windows Server 2022.

The 16-core-per-server floor is Windows Server. It is correct on this URL. Do not copy it onto a SQL true-up. SQL Per Core is four core licenses per physical processor.

Eight cores 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 floor did not move from 2022. Core-based licensing models: software partitioning or BIOS disabling does not shrink the count.

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

Worked shapes from Microsoft’s own table (same on 2022 and 2025):

• 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. That 16 is the Windows Server floor, not a SQL server minimum.

Standard is still two OSEs

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. Or, with SA or a subscription, license extra VMs by vCore. 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.

How to count, how to stack, and how CALs sit on top of the cores is the 2025 metric. That file stays at the Windows Server 2025 licensing guide. The 2022 estate stays at the Windows Server 2022 licensing guide. Do not flatten those two URLs into this one.

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.

The VM rule is from October 2022, not from 2025

October 2022 added VM licensing. 2025 guidance, core-based licensing models, 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. Windows Server 2025 did not reverse it.

How to count a VM (both versions):

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).

What 2025 actually changed

These are the licensing and edition deltas that move a true-up. They are not a 93 percent list-price story.

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. Learn editions comparison: 2022 Hotpatch is Azure Edition only. 2025 Standard and Datacenter get Arc-enabled Hotpatch. Azure Edition has it 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.

CALs still sit on top of the cores, except PAYG. A 2025 CAL or EC accesses 2025, 2022, and 2019. A 2022 CAL does not access 2025. 2025 guidance. Entra ID sync remains an exception: no Windows Server CAL when access is solely to sync AD with Entra ID.

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

• 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.

Edition features that still decide Datacenter

These did not flip with the version. They still decide whether Standard stacking is even the right conversation.

Microsoft’s Windows Server licensing resources edition table, matching Learn editions comparison and locks and limits:

Do not brief Shielded Virtual Machines as a Standard feature. Do not mark SDN as “Limited” on Standard. Storage Replica overview: Standard on Windows Server 2019 or later replicates a single volume up to 2 TB.

Host Guardian Service as a *role* can sit on Standard. Host Guardian Hyper-V Support (the shielded guest host) is Datacenter. Do not flatten those two rows.

What SA (or a subscription) still decides

The bit that decides a 2022-to-2025 conversation is whether SA or a subscription sits on the paper, not whether the binaries say 2025.

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.

Desktop chrome is not a core count

What’s new in Windows Server 2025 is the feature file: Windows 11-style desktop, Bluetooth, DTrace, ZIP / 7z / TAR compression, Credential Guard on by default, optional 32k Active Directory database pages, OpenSSH server installed by default. Features removed or no longer developed is the removal file: DES, IIS 6 Management Console, NTLMv1, SMTP Server, WordPad, Internet Explorer 11 standalone, PowerShell 2.0 (from the September 2025 update). Deprecated: Computer Browser, Network Load Balancing, Remote Mailslots, TLS 1.0 / 1.1 (disabled by default), WMIC as a Feature on Demand, Windows Internal Database.

Those pages decide whether an application still runs. They do not change 8 cores per processor, 16 cores per server, two Standard OSEs, or the 2025 CAL. Do not brief DTrace as a reason to pay a made-up Datacenter hike.

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 feature table and not an invented price list.

1. Every host, edition, version, OSE type. Physical, VM, Hyper-V isolated container, Windows Server container. 2022 versus 2025 called out. 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, a 2025 upgrade right, 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 “Datacenter is ninety-three percent more” or “Standard includes one instance plus two VMs” 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 comparison URL bookmarked. The quote walking in may already say 2025. Neither document is the estate. The number is cores after the 8/16 floors, edition actually installed, version actually running, 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: 2022 versus 2025, 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 2025 Datacenter, unlimited virt is included, here is the list price.” 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, or treat PAYG as extra VMs on an already licensed Standard host. The right question is: which version, which edition, how many cores after the 8-per-processor and 16-per-server floors, 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, CAL version table): https://www.microsoft.com/licensing/guidance/Windows-Server-2025
• Windows Server licensing resources (editions table, Shielded VMs Datacenter-only, SDN Datacenter, Storage Replica Standard 2 TB footnote, 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 (2022 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
• Comparison of Windows Server editions (2022 vs 2025: Hotpatch, SMB over QUIC, Host Guardian Hyper-V Support, Network Controller, Storage Spaces Direct): https://learn.microsoft.com/en-us/windows-server/get-started/editions-comparison
• Locks and limits (Storage Replica Standard 1 partnership / 2 TB both versions; OSE rights): https://learn.microsoft.com/en-us/windows-server/get-started/locks-limits
• Storage Replica overview (Standard single volume up to 2 TB): https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/storage-replica-overview
• SMB over QUIC (2022 Azure Edition only; any edition of Windows Server 2025): https://learn.microsoft.com/en-us/windows-server/storage/file-server/smb-over-quic
• What’s new in Windows Server 2025 (product chrome, not a metric): https://learn.microsoft.com/en-us/windows-server/get-started/whats-new-windows-server-2025
• Features removed or no longer developed: https://learn.microsoft.com/en-us/windows-server/get-started/removed-deprecated-features-windows-server
• Listed Providers (do not treat FVB as a pass onto these clouds): https://aka.ms/listedproviders