Licensing Windows Server 2022 - 2 Core and 16 Core.

[Paulo320]

Dear, good night.
Could you please help me regarding licensing Windows Server 2022 - 2 Core and 16 Core.

How many cores are licensed for each SKU.
02 Core
16 Core
I thank the community for the support.

[#2]

***Some general info***
- Each host needs to be licensed.
- A minimum of 8 core licenses is required for each physical processor and a minimum of 16 core licenses is required for each server.
- Core licenses are sold in packs of two.
- Standard Edition provides rights for up to 2 Operating System Environments or Windows Servers containers with Hyper-V isolation when all physical cores in the server are licensed. For each additional 1 or 2 VMs, all the physical cores in the server must be licensed again.
- DataCenter Edition provides rights for unlimited Operating System Environments or Windows Servers containers with Hyper-V isolation when all physical cores in the server are licensed.

[#3]

Any progress or updates? Please don't forget to close up thread by marking helpful replies.

[#4]

Ok.
Thanks a lot for the help

[#5]

Hello, thanks @Dave Patrick for these informations (any source link?)

BUT i must rebound on this : what if you want to licence one VM on a Vmware or PROXMOX environment. (VM with 2 cores).
Should you buy :
"Microsoft Windows Server Standard 2022 64Bit 1Pack DVD 16 Core" ~1000€
and then you can activate it 8 times for 4 VMs.

or should you buy for one VM:
"Microsoft Windows Server Standard 2022 2Core Pack" ~150€

This completely twisted tarifications doesnt makes lifes easy

[#6]

Just wanted to update this based on it being a search hit whilst I was trying to find the same info - hopefully this will help some people out now.

Windows Server 2022 Datacenter and Windows Server 2022 Standard are licensed under a core-based license
model. For both Datacenter and Standard , the number of core licenses required depends on whether a
customer is licensing based on the physical cores on the server or by virtual machine. The option to license
Windows Server by virtual machine was added in October 2022, and is available to customers with subscription
licenses or licenses with active Software Assurance only.
• When licensing based on the physical cores on the server, the number of core licenses required equals
the number of physical cores on the licensed server, subject to a minimum of 8 core licenses per
physical processor and a minimum of 16 core licenses per server.
• When licensing by virtual machine, the number of core licenses required equals the number of virtual
cores in the virtual operating system environment (i.e., virtual machine), subject to a minimum of 8
core licenses per virtual machine and 16 core licenses per customer.

From https://aka.ms/WindowsServerLicensingGuide

[#7]

So, if I want to have Windows Server 2022 Standard on my Dell PowerEdge R540 with Twelve Core 3Ghz processors, I need to purchase the package of 16 core licenses for Windows Server Standard, not the one with 2 core licenses. Correct?

[#8]

Necro this article because of past and upcoming changes.

@VINEIT if the DELL Server has 2 physical CPUs and 12 physical cores in total, then yes. 16-core pack for this device, for a regular Standard or Datacenter licensing.
Standard or Datacenter Edition is based on the amount of VMs
Azure Stack HCI requires Datacenter Edition

If it is one physical CPU with 12 physical Core you can mix and match to license 12 cores, like 6x 2 Core Packs of the same edition or other packs and filling up the rest with 2-core packs.

Mind that packs are available in different sizes with different rebates. So 1x 16-core pack might be even cheaper than 6x 2-core packs.

At times I've even seen 4-core packs in volume licensing price lists.

CSP (CSP Subscription mostly recommended due to the release of WS 2025 and more reasons), offer 8-core packs, only.


Understanding Licensing packs
License packs are literally packs. They can be seperated to be assigned to physical cores and even different servers. Like you can take one bottle of beer from a pack of 6. 

The only thing is you have to take care about your paperwork in your SAM / Excel in case of an audit, that it remains clear what you did and most importantly when.

The reason for 8-core packs in CSP Subscription is that everything is licensed as in Azure.
Also CSP Subscription would allow a per VM licensing.

"Per VM" licensing
In opposite / or even in addition to "per core licensing", you can add more licenses 
This makes especially sense in very special cases when having larger clusters with VMware or Proxmox or Azure Stack HCI, but only VERY few Windows Server VMs running on these and you want them to move within the cluster, without licensing every CPU core in this cluster. 

The rule here is 8-core pack "per VM", license still assigned to the HW but it can move. The number of virtual CPUs of the VM is near irrelevant. It is 8 or a multiple of 8 like 8, 16, 24 etc.
so 2 vCPUs still require a minimum  8-core pack for this VM.

Thank you for the excellent summary @Robin Clive-Matthews 

Windows Server licensing has a quite an amount of caveats but also chances to save :) 
It depends on the licensing model (Volume Licensing like Open, Enterprise Agreement), CSP, SPLA (for hosting) etc. pp. Variety of Azure Benefits, BYOL benefits etc pp. 

Even the perfect stated rule of @Dave Patrick becomes obsolete as soon choose for "per VM" licensing.
OEM licensing even allows to "break" the 8 Core per CPU / 16 Core per Server rule and allow you to pay only active CPU cores (de/activated to and present to the OS via UEFI setup), but this comes not handy if you want to add Volume Licensing Software Assurance. And then again the paperwork. Cannot really recommend unless you bought an OEM box with no intentions for Software Assurance and oversized the CPUs for whatever reasons.

Windows Server 2025 will offer on-demand licensing, but we consider it before not written in Product Terms.


Microsoft Licensing is often like white magic, and there is one source of trust to study:
Everything about it can be found here (and trusted for audit only here): https://www.microsoft.com/licensing/terms/
All other sources are complementary and not binding for audits (including my posting) ;)

Before checking details
- choose your licensing program you are into on the top bar
- if any, mind your licensing commitments to Microsoft (like MPSA, Enterprise Agreement), that you might not license certain products via other programs
- if you need to know the terms back in time of purchase use the date picker (if you know what you are doing). 

I could recommend a good tutor on YT, but still Product terms beat any other information.