Clarification on Windows Server 2022 Datacenter activation and licensing count in a Virtualized Environment

Question

Clarification on Windows Server 2022 Datacenter activation and licensing count in a Virtualized Environment

Behrem Novruzov 0

Hi everyone,

I need clarification regarding Windows Server 2022 Datacenter licensing and activation in a virtualized environment.

Our organization purchased 10 standalone Windows Server 2022 Datacenter 16-Core licenses. We are running multiple Virtual Machines (VMs).

During deployment, we used a single 16-Core Datacenter product key to activate 5 different Virtual Machines. All 5 VMs activated successfully with the same key.

Given that Datacenter edition grants unlimited VM rights per fully licensed physical host, I have two questions:

Technically, how does Microsoft Activation Server handle multiple VM activations using a single Datacenter Retail/MAK key? Does it allow high activation limits specifically for VM deployments?
If all 5 VMs reside on the same physical host (16 cores), using 1 Datacenter key is fully compliant. But if these VMs are spread across different physical hosts, does using the same key cause an audit issue even if activation succeeds?

What is the best practice for assigning Datacenter keys to VMs across multiple hosts?

Thanks for your support!

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Behrem Novruzov 0 Reputation points

2026-07-30T10:41:59.7333333+00:00

I understood. So, 16 cores written above the activation key generally shows the number that we can use on a 16-core machine, but the key itself can be used multiple times for activation.
Behrem Novruzov 0 Reputation points

2026-07-30T10:48:48.53+00:00

But here is what I don't understand: how can we run ten virtual machines—each with 16 cores—on a physical server with 32 cores and utilize that 16-core license in each instance? After all, the physical server's core count exceeds the number specified on the virtual license key. I want to understand how this is possible.

1 answer

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Behrem Novruzov 0 Reputation points

2026-07-30T10:41:59.7333333+00:00

I understood. So, 16 cores written above the activation key generally shows the number that we can use on a 16-core machine, but the key itself can be used multiple times for activation.
Behrem Novruzov 0 Reputation points

2026-07-30T10:48:48.53+00:00

But here is what I don't understand: how can we run ten virtual machines—each with 16 cores—on a physical server with 32 cores and utilize that 16-core license in each instance? After all, the physical server's core count exceeds the number specified on the virtual license key. I want to understand how this is possible.

Answer 1

Hello Behrem Novruzov, thank you for posting in the Microsoft Q&A community.

The confusion in these scenarios stems from the difference between Technical Activation (the product key successfully activating the operating system) and Licensing Compliance (adhering to Microsoft's legal licensing terms). Microsoft’s activation servers validate the key's mathematical validity and activation allowance, but they do not actively monitor your physical host topology or audit your core counts.

To address your first question, Multiple Activation Keys (MAK) and Retail keys have a predefined activation limit allowed by Microsoft's activation servers. Activating a Virtual Machine simply consumes one of these activation counts. The server allows multiple activations because these keys are designed for bulk deployments. However, a successful activation does not automatically mean you are legally compliant. Microsoft relies on the organization to ensure licenses are correctly assigned to the physical hardware.

Regarding your second question about spreading VMs across multiple hosts, Windows Server Datacenter licenses are assigned to the Physical Host, not the Virtual Machines. If all physical cores of a single host are fully licensed with Datacenter, you are compliant and can run an unlimited number of VMs on that specific host. Conversely, if you spread those 5 VMs across 5 different physical hosts, each of those physical hosts must have all of its physical cores fully licensed. Using the same product key to activate VMs on unlicensed hosts will work technically, but it will result in a licensing violation during an audit.

In the follow-up comment, you asked how you can run ten 16-core VMs on a 32-core physical server using a 16-core license. The short answer is: you cannot use just a single 16-core license on a 32-core physical server. Microsoft licensing dictates that all physical cores on the host must be licensed. Therefore, a 32-core physical host requires 32 core licenses. Once the physical host is fully licensed, the Datacenter edition grants you unlimited virtualization rights. The number of virtual CPUs (vCPUs) you allocate to the VMs does not matter for Windows Server licensing. The license applies exclusively to the underlying physical hardware.

For your deployments, the official standard practice for activating VMs in a Datacenter environment is to use Automatic Virtual Machine Activation (AVMA). Instead of consuming your MAK/Retail key limits for every single VM, you should:

Activate your physical Hyper-V host using your purchased Windows Server 2022 Datacenter key.
Inside your guest VMs, apply the official Microsoft AVMA client setup key for Windows Server 2022 Datacenter: W3GPN-YWJQY-24DPB-HBPYW-Q7KGX
The VMs will automatically activate against the Hyper-V host without requiring an internet connection or consuming your MAK key limits.

For more details, please review the official Microsoft Learn documentation: