Hosting more than VMs on a Standard Server, can i licensing the vm instead of host server?

Question

We have a host server with 32 cores and we are moving from ESXI to Hyper-V. We already have licenses for 6 of our VMs.

My question is can we reuse those 6 licenses, to licensing our VMs. And only buy new 32 cores license for the physical host server instead of having to buy 96 cores license for the host server?

As we understand, in the image is the scenario that we are falling into. So that we only need to buy new 32 cores for the physical host, and reuse 4 old VM licenses to have 6 VMs on that physical host?
https://www.licensingschool.co.uk/wp-content/uploads/2025/10/Windows_Server_virtualization_licensing_guidance-August-2025.pdf

Answer 1

Dear Lam Pham,

Thank you for sharing the details about moving from ESXi to Hyper‑V and the licensing scenario. Windows Server licensing requires that the physical host be licensed for all of its cores. For a server with 32 cores, a 32‑core license must be purchased and applied. Once the host is properly licensed, virtualization rights are included, allowing a specific number of virtual machines to run without requiring separate VM licenses. Existing VM licenses cannot be reused in this context, as the virtualization rights are tied to the host license rather than individual VM licenses. To ensure compliance, the correct approach is to license the physical host with the appropriate number of cores, and then use the virtualization rights granted by that license to cover the VMs.

If this answer resolves your concern, please click Accept the answer so that confirmation is received.

Best regards,

QQ.

Answer 2

Windows Server core licenses can be applied either to the physical host (pCore licensing with Standard or Datacenter) or to individual VMs (vCore licensing with Standard), but the rules are strict and the same licenses generally can’t be “double‑counted” for both host and VMs at the same time.

From the provided material:

• For Windows Server 2012/2012 R2 ESUs enabled by Azure Arc (the clearest formal statement of the core rules, which mirror the base licensing model):
  • vCore (VM) licensing has an 8‑core minimum per VM and uses Standard edition rates.
  • pCore (host) licensing has a 16‑core minimum per physical server and can use Standard or Datacenter.
  • With pCore licensing on a Standard host, up to 2 guest VMs are covered; additional VMs require additional ESU licenses. With Datacenter, all VMs on the host are covered.

Applied to the scenario:

1. Licensing the host only
   • If the 32‑core physical host is licensed with Windows Server Datacenter (all 32 cores), all Windows Server VMs on that host are covered; there’s no need to license each VM separately.
   • If the host is licensed with Windows Server Standard (all 32 cores), that covers the host plus up to 2 VMs. Any additional VMs require additional Standard licenses (effectively stacking Standard licenses to cover more VMs).
2. Licensing individual VMs instead of the host
   • Each VM can be licensed based on virtual cores, with a minimum of 8 cores per VM.
   • This model is intended for cases where licensing the entire host is not cost‑effective or where the host is not under your control (for example, third‑party clouds).
3. Reusing existing VM licenses
   • The context does not state that existing VM licenses can be reused in a way that reduces the required core count for the host. To license the host for unlimited virtualization (Datacenter) or for the Standard entitlements, all physical cores on the host must be licensed.
   • Therefore, if the goal is to license the physical host, the requirement is to license all 32 physical cores on that host; existing VM licenses do not reduce that 32‑core requirement.

In other words, to avoid buying 96 cores, either:

• License the 32‑core host fully (Standard or Datacenter) and rely on host‑based entitlements, or
• License only the VMs individually by vCores (8‑core minimum per VM) and do not rely on host‑based virtualization rights.

The same core licenses cannot be counted simultaneously as both VM licenses and host licenses to reduce the physical‑core requirement.

---

References:

• Lifecycle FAQ - Extended Security Updates
• License provisioning guidelines for Extended Security Updates for Windows Server 2012
• License SQL Server, Windows Server, and Linux in Azure VMware Solution
• Azure Hybrid Benefit for Windows Server