Azure Hybrid Benefit Windows Server Core Calculator
Add your Azure VM sizes and quantities to see the Windows Server core licenses needed with Azure Hybrid Benefit. No Azure login, prices or account data.
Your VM sizes
24 core licenses required - 3 x 8-core pack equivalents. Updates as you type.
3 VMs x 8 required cores = 24 core licenses required for this row.
4 vCPUs per VM - 8 licensed cores per VM (8-core minimum)
Checked sizes and exclusions
Choose or paste an exact size. This catalog covers 732 exact A, B, D, E, F, L and M-family sizes, checked 2026-11-04. It includes older sizes for existing deployments, not just new deployments. Preview, ARM, constrained-vCPU, confidential, GPU, FPGA and HPC sizes are outside this catalog. Unknown sizes block the total instead of guessing.
What licenses do I need?
The total above is the number of Windows Server core licenses required for these VMs under Azure Hybrid Benefit. It does not change based on what licenses you already own.
- Count: one core license per VM vCPU, with at least 8 per VM. Multiply by quantity, then add the rows.
- Coverage: Windows Server Standard or Datacenter core licenses need a qualifying subscription or active Software Assurance. An old perpetual license without that coverage does not qualify.
- Apply the benefit: you must have enough eligible licenses available and enable Azure Hybrid Benefit for the Azure VMs. This calculator does not check your agreement or Azure account.
License eligibility has not been checked. The count is a requirement, not confirmation that you own qualifying licenses.
Core requirements
| VM size | VMs | vCPUs each | Licensed cores each | Licensed cores |
|---|---|---|---|---|
| Standard_D4s_v6 | 3 | 4 | 8 | 24 |
- VMs
- 3
- vCPUs each
- 4
- Licensed cores each
- 8
- Total licensed cores
- 24
24Core licenses required
38-core pack equivalents
0Cores above the requirement
3 x 8 cores = 24 cores, with 0 beyond this requirement. This is an 8-core pack equivalent, not a statement that your reseller sells that pack size. Confirm the available license packs and qualifying coverage before purchase. Rounding happens after adding all VM requirements.
How the count works
For each VM, allocate one eligible core license per virtual core, with a minimum of 8. Multiply by the number of that size, then add the rows. There is no extra 16-core minimum across the whole deployment.
Example: three 4-vCPU VMs need 3 x 8 = 24 core licenses, or three 8-core pack equivalents. Two 12-vCPU VMs need 24 core licenses and three 8-core pack equivalents, not four. For example, Standard_M12s_v3 has 12 vCPUs.
Windows Server Standard and Datacenter use the same per-VM count here. For Standard, use the licenses either on-premises or in Azure, not both at the same time, except once for up to 180 days while migrating the same workloads. For Datacenter VM licensing, Microsoft permits simultaneous on-premises and Azure use indefinitely when migrating workloads. These are VM licensing rules; Dedicated Host rules differ. Your subscription or Software Assurance must remain active, and Azure Hybrid Benefit must be enabled separately on the VMs.
This calculator does not license SQL Server, Windows client/AVD, on-premises hosts, Azure Dedicated Host, Azure Local, AKS, RDS access or other software. It does not check regional VM availability or your actual Azure configuration.
Sources and checked date
Rules and catalog checked 2026-11-04. Microsoft Product Terms govern your agreement. Microsoft's Azure Hybrid Benefit guide explains the 8-core minimum and eligibility. Some generic licensing FAQs retain older 16-core allocation wording; this calculator follows the current per-VM terms.
All 83 Microsoft size-table sources
- av2-series
- bv1-series
- basv2-series
- bsv2-series
- dadsv7-series
- daldsv7-series
- dalsv7-series
- dasv7-series
- ddsv7-series
- dldsv7-series
- dlsv6-series
- dlsv7-series
- dsv6-series
- dsv7-series
- dv3-series
- dv4-series
- dv5-series
- dav4-series
- dadsv5-series
- dadsv6-series
- daldsv6-series
- dalsv6-series
- dasv4-series
- dasv5-series
- dasv6-series
- ddv4-series
- ddv5-series
- ddsv4-series
- ddsv5-series
- dldsv5-series
- dlsv5-series
- dsv3-series
- dsv4-series
- dsv5-series
- dv2-series
- dsv2-series
- ev5-series
- edv5-series
- edsv5-series
- esv5-series
- eadsv5-series
- easv5-series
- ebdsv5-ebsv5-series
- eadsv7-series
- easv7-series
- edsv7-series
- esv6-series
- esv7-series
- ev3-esv3-series
- eadsv6-series
- easv6-series
- fadsv7-series
- faldsv7-series
- falsv6-series
- falsv7-series
- famdsv7-series
- famsv6-series
- famsv7-series
- fasv6-series
- fasv7-series
- fsv2-series
- fx-series
- fxmdsv2-series
- fxmsv2-series
- laosv5-series
- lasv5-series
- laosv4-series
- lasv3-series
- lasv4-series
- lsv2-series
- lsv3-series
- lsv4-series
- m-series
- mbdsv3-series
- mbsv3-series
- mdsv2-mm-series
- msv2-mm-series
- mdsv3-mm-series
- msv3-mm-series
- mdsv3-vhm-series
- mv2-series
- mdsv3-hm-series
- msv3-hm-series
Listing a size confirms its documented vCPU count only. It is not a recommendation or a guarantee of availability, lifecycle status, supported Windows image or Azure Hybrid Benefit eligibility. Check the linked Microsoft page, your region, image and agreement. Unlisted sizes are blocked rather than inferred.
Inputs stay in this page's memory unless you choose to copy a shared link. Shared links include only checked Azure VM sizes and quantities, not your license eligibility. Anyone with the link can see those sizes and quantities. Do not enter machine names or other private information.