Cloudek.

Windows Server

Windows Server Licensing Explained: Standard vs Datacenter, Hyper-V and CALs

Windows Server licensing explained: core licenses, Standard vs Datacenter for Hyper-V VMs, user and device CALs, RDS CALs and Azure Hybrid Benefit.

Windows Server licensing looks confusing because four separate decisions get mixed together: how many core licenses a server needs, which edition covers your virtual machines, which client access licenses (CALs) cover your people, and which agreement you buy under. This guide takes them one at a time for Windows Server 2022 and 2025, and links to a free calculator that does the arithmetic in your browser.

Rules checked 1 November 2026 against Microsoft's own pages, listed under Sources at the end. This is general information and an estimate, not licensing advice. Your agreement (volume licensing, CSP, OEM, Software Assurance, subscription) can change the answer, and Microsoft's Product Terms control. The Microsoft licensing pages I read are written for Windows Server 2025; Windows Server 2022 uses the same per-core model, but confirm the details for your version. Where a point is unclear or depends on the agreement, this article says to confirm with your reseller or a Microsoft licensing specialist instead of guessing.

The short answer

  • Standard and Datacenter are licensed per physical core, with a minimum of 8 core licenses per processor and 16 per server. Core licenses come in packs of 2.
  • Standard covers two virtual machines (technically two operating system environments) on a fully licensed host. For more, you license the host again, over and over. Datacenter covers any number.
  • Datacenter becomes cheaper than stacked Standard once the number of VM pairs on a host exceeds the price ratio between the two editions. The break-even VM count therefore depends on the prices you actually pay, so work it out from your quote.
  • Every person or device that accesses a Windows Server needs a CAL, with a short list of exceptions. Remote Desktop Services needs RDS CALs on top.
  • Choosing the edition does not change the CAL cost. CALs cost the same whether the server is Standard or Datacenter.

Step 1: How many core licenses does one server need?

Count the physical cores in each processor. Each processor is licensed for at least 8 cores, and each server for at least 16 core licenses in total, whichever is higher. Because licenses are sold as packs of 2 cores, you round an odd total up to the next even number.

Worked examples, checked by hand and by the calculator:

  • One processor with 4 cores: 4 is below the 8-core minimum, so 8, and the 16-per-server minimum lifts the total to 16 core licenses.
  • Two processors with 6 cores each: 8 + 8 = 16, which also meets the server minimum, so 16.
  • Two processors with 12 cores each: 24 physical cores, no minimum applies, so 24.
  • One processor with 10 cores: 10 is above 8 but the server minimum applies, so 16.

Licensing is by physical cores in the host, not by how many virtual cores your VMs use.

Step 2: Standard vs Datacenter on a Hyper-V host

The editions also differ in some features (compare them on Microsoft Learn for your version), but for licensing the big difference is virtualization rights.

  • Standard covers up to two OSEs (operating system environments) on the licensed server. An OSE is a virtual machine, or a container that runs with Hyper-V isolation. The physical host can also run Windows Server if it is used only to host and manage those virtual machines.
  • Datacenter covers any number of OSEs on the licensed server.
  • Windows Server containers without Hyper-V isolation are not counted against the two in Standard, and they are unlimited in both editions. A Hyper-V-isolated container is counted as one OSE.

To run more than two Windows Server VMs under Standard you stack licenses: for each extra pair of VMs, you license all the physical cores of the host again with another full set of Standard core licenses. Microsoft's own example is a 16-core server with 4 VMs, which needs 32 core licenses. If the host also runs other roles (not only Hyper-V), it counts as one of the OSEs.

Worked example for one host with two 12-core processors and 10 Windows Server VMs:

  • Core licenses for the host: 24.
  • Standard: 10 VMs need 5 sets (10 divided by 2), so 5 x 24 = 120 core licenses.
  • Datacenter: 24 core licenses.

Only Windows Server VMs count. A Linux VM does not use a Windows Server license. Windows client desktops in VDI are licensed separately (more on that below).

Does Datacenter save money?

Datacenter needs fewer core licenses than stacked Standard once you have more than a few VMs, but each Datacenter license costs far more. Which edition is cheaper is a straightforward comparison:

  • Standard cost per host = number of sets x core licenses x Standard price per core.
  • Datacenter cost per host = core licenses x Datacenter price per core.

The core count cancels out. For a given host, Datacenter is cheaper when the Datacenter price for a set of 16 cores is lower than the number of Standard sets multiplied by the Standard price for a set. So the break-even point depends only on the ratio of the two prices.

Many articles say Datacenter pays for itself at about 7 to 8 VMs per host, and others say about a dozen. Both can be true for a particular price ratio, which is why you should not trust a rule of thumb. A ratio of 4 gives a tie at 7 to 8 VMs, and Datacenter wins from 9. A ratio of 5 gives a tie at 9 to 10 and Datacenter wins from 11. A ratio of 6 gives a tie at 11 to 12 and Datacenter wins from 13.

When I checked Microsoft's Windows Server pricing page on 1 November 2026, it showed US suggested prices of $1,176 for Standard and $6,771 for Datacenter, each for 16 core licenses (the page shows no effective date, and prices vary by country and reseller). These are the same figures the calculator pre-fills. That is a ratio of about 5.8, so on those list prices Datacenter becomes cheaper from 11 VMs per host, not 7 to 8:

  • 10 VMs on a 24-core host: Standard 120 core licenses, about $8,820. Datacenter 24 core licenses, about $10,156.50. Standard is cheaper.
  • 12 VMs on the same host: Standard 6 sets, 144 core licenses, about $10,584. Datacenter is still about $10,156.50. Datacenter is cheaper by roughly $427.

Those are list prices, before tax, discounts, CALs and Software Assurance. Your quote, agreement and country will differ, so overwrite the two pre-filled prices in the calculator with your own and let it find the break-even. Microsoft India shows no INR list price for Standard or Datacenter, so there is no INR option for them: local price depends on currency, partner and agreement.

Cost is not the only reason to choose Datacenter. Growth plans matter: a host that will outgrow the break-even number is cheaper to license as Datacenter from the start than to buy Standard sets and pay again later (step-up rights under Software Assurance can soften this, so ask). The opposite point also holds: if a host will only ever run one or two Windows Server VMs, Standard is almost always the sensible choice.

Worked scenario: two Hyper-V hosts and 10 to 15 Windows VMs

This is the question that comes up most often, and "10 to 15 VMs" can mean two different things, so here are both. Assume two identical hosts, each with two 12-core processors (24 core licenses per host), running only Windows Server VMs.

If 10 to 15 VMs are shared across both hosts (5 to 8 per host) and stay where they are:

  • 5 VMs per host (10 in total): 3 Standard sets per host, so 3 x 24 = 72 core licenses per host and 144 in total. Datacenter: 24 per host, 48 in total.
  • 8 VMs per host (15 in total, rounding up): 4 sets per host, so 96 per host and 192 in total. Datacenter: 48.

If each host runs 10 to 15 VMs (20 to 30 in total):

  • 10 VMs per host: 5 sets, 120 per host, 240 in total. Datacenter: 48.
  • 15 VMs per host: 8 sets, 192 per host, 384 in total. Datacenter: 48.

If the hosts form a cluster and the VMs can run on either one: each host has to be licensed for the most VMs it may run. With 10 VMs in the cluster, each host needs 5 sets (240 in total), the same as having 10 on each host. With 15 VMs in the cluster, each host needs 8 sets (384 in total). Datacenter stays at 48 whatever the VM count or where the VMs sit.

Whether the extra Standard core licenses cost more than Datacenter depends on your prices. Using the list prices quoted above (checked 1 November 2026) (24 cores per host, about $1,764 per Standard set and about $10,156.50 for Datacenter per host), two hosts cost about $10,584 (5 VMs each), $14,112 (8 each), $17,640 (10 each) and $28,224 (15 each) on Standard, against about $20,313 on Datacenter. On those list prices, Standard is cheaper at 10 VMs on a host and Datacenter is cheaper at 15. For a two-node cluster with 10 VMs, Standard is still cheaper by the same list prices, but Datacenter is simpler because nothing needs recounting after a failover or a live migration. The calculator has a "VMs can move between hosts" option and shows both results, with and without movement, so you can see what the assumption costs.

Clusters, live migration and the 90-day rule

A VM that can move between hosts has to be licensed on every host it can run on. In practice you license each host for the most VMs it may need to run, including after a failover or during maintenance. Microsoft's terms limit how often licenses can be reassigned to a different server (generally not within 90 days of the last assignment, with exceptions such as hardware repartitioning), so licensing only for the VMs that are on a host today can leave you short when a host fails. For a two-node cluster that is designed so either host can run everything, each host is effectively licensed for all the VMs. That is the situation in which Datacenter is simplest, because one Datacenter license per host covers any number of VMs wherever they land. Confirm your cluster design and any shared-storage or replica arrangements with your reseller.

Linux guests, Windows client guests and containers

Only Windows Server guests use Windows Server virtualization rights, so count only those. A Linux VM needs no Windows Server license, though the host that runs it still needs one, and so do any Windows Server VMs beside it. Windows client desktops in VMs (VDI) are a different product with their own licensing, covered below. Containers split two ways: Windows Server containers without Hyper-V isolation are unlimited and do not count, and a Hyper-V-isolated container counts as one OSE.

CALs depend on people and devices, not on VMs

A frequent mistake is to scale CALs with the number of VMs, hosts or cores. They do not scale that way. The number of CALs follows the people or devices that access your Windows Servers, so adding ten VMs does not add a CAL, and moving from Standard to Datacenter does not remove one. Conversely, a single user who reaches twenty servers still needs one user CAL, not twenty.

Client access licenses (CALs)

A server license lets you run the software. A CAL gives a person or device the right to access it. Every user or device that accesses a Standard or Datacenter server needs one, including employees and onsite contractors.

  • User CAL: one named person, using any number of devices.
  • Device CAL: one device, used by any number of people. This suits shared devices, such as shift-work PCs, kiosks or reception machines.
  • You can mix types in one environment, but each person or device must be covered. Compare the two counts. If you have 50 users and 80 devices, user CALs need fewer licenses. If 120 people share 40 devices, device CALs do.
  • A CAL permits access to the same version of Windows Server or an earlier one. A Windows Server 2025 CAL covers 2025, 2022 and 2019, but a 2019 CAL does not cover a 2025 server.
  • External users, such as customers and partners, need either CALs or an External Connector license for each physical server they access, whichever fits.
  • Some Microsoft subscriptions include CAL rights. Microsoft's licensing guidance says CAL equivalents, such as the Core CAL Suite and Microsoft 365 E3 or E5 user subscriptions, can count for the access they cover. Confirm this for your plan.

When you do not need a CAL

Microsoft's Product Terms list the cases where Windows Server CALs are not required:

  • Access by another licensed Windows Server (server-to-server access).
  • Access to a web workload or an HPC workload.
  • Access to the physical host used solely to host and manage its virtual machines.
  • Access only to sync Active Directory with Microsoft Entra ID.
  • Windows Server 2025 pay-as-you-go through Azure Arc, which needs no CALs for standard functionality (RDS CALs are still required).

Servers that do not run Windows Server (a Linux VM, for example) do not need Windows Server CALs at all.

What is unclear

Two points deserve a check with your reseller rather than a guess. First, anonymous internet access: the exemption in the terms is for web workloads, and the exact definition sits in Microsoft's glossary, which I could not read in full. A public website that does not sign visitors in is the usual example, but a server that authenticates visitors, or that issues or manages identities for external users, is a different question. Second, indirect access through another application or a pooling layer: do not assume that putting a front end between people and the server removes the need to license those people, and check your exact design.

RDS CALs

Remote Desktop Services is an add-on. Anyone who connects to a session host or hosted desktop needs a Windows Server CAL and an RDS CAL. Like Windows Server CALs, RDS CALs come as user or device versions, and external users can be covered with an External Connector. They are not included in the server license and cost extra regardless of edition. If you are moving users into a virtual desktop setup, count the RDS CALs separately in the calculator.

Volume licensing, Software Assurance and agreement types

What you can buy depends on how you buy. Microsoft's guidance notes that the Open License program retired on 31 December 2021, with no new licenses from 1 January 2022, so purchases now go through other routes, such as a Cloud Solution Provider partner, an OEM when you buy a server, or a volume agreement such as an Enterprise Agreement. Software Assurance and subscriptions are available only through certain agreements.

Software Assurance (SA) or a qualifying subscription unlocks several rights for Windows Server:

  • Licensing by virtual machine (a minimum of 8 core licenses per VM), which can suit small, mostly-virtual estates. It needs SA or a subscription.
  • New-version rights and step-up licenses, for example from Standard to Datacenter, which are not available through every program.
  • Limited disaster-recovery rights for a backup copy, with conditions.
  • Azure Hybrid Benefit (below).

Prices, minimum quantities, SA rules and whether you can buy per VM all differ by agreement. Treat anything that depends on the agreement as a question for your reseller.

Azure Hybrid Benefit, license mobility and pay-as-you-go

Azure Hybrid Benefit lets you use Windows Server core licenses that have active Software Assurance or a qualifying subscription to cover Windows Server VMs in Azure, so you pay only the base compute rate. Microsoft Learn states a minimum of 8 core licenses per Azure VM, even for a 4-core VM. Microsoft's licensing page adds how the first licenses are allocated: each set of 16 core licenses covers up to 16 virtual cores across at most two Azure VMs, and further VMs are covered in steps of 8. The benefit runs only while SA or the subscription is active. Datacenter licensing includes dual-use rights (running on-premises and in Azure at the same time), and Standard does not. Check the migration allowance and other conditions for your agreement.

License Mobility through Software Assurance, the benefit many people expect to apply, is not available for Windows Server, according to Microsoft's licensing FAQ. That page points to the Flexible Virtualization Benefit and to authorized providers instead.

Windows Server 2025 pay-as-you-go through Azure Arc is an alternative to buying licenses. You enable it on a server connected to Azure Arc and are billed per core through Azure. Standard and Datacenter are billed at the same rate, there is no minimum core count, and Windows Server CALs are not required for standard functionality, although RDS CALs still are. It licenses only the machine where it is enabled and gives no extra rights to the VMs running on it, so each VM needs its own license. It also keeps billing until you disable it. Check the current rate in the Azure portal, because the rate shown on Microsoft's pricing page is not dated.

Windows Server Essentials

Essentials is sold through OEMs only. It is meant for small organizations with up to 25 users and 50 devices. A license covers a single-processor server with up to 10 cores and one running instance in a physical or virtual environment. It is not a path to more VMs. If your numbers are above those limits, Standard is the next step. The calculator checks your numbers against the limits.

Windows client licensing for VDI, briefly

Windows client desktops in virtual machines are licensed under a different set of rules from Windows Server. Microsoft's virtual desktop guidance describes a per-user or per-device Windows VDA subscription for devices not covered by another license, plus per-user options such as Windows 11 Enterprise E3 or E5 and Microsoft 365 E3 for virtual access. Azure Virtual Desktop requires a user license. If the desktops are hosted on Windows Server, Microsoft's guidance gives an example that also needs Windows Server CALs and RDS CALs (confirm in the Product Terms). This calculator does not model client licensing.

Does the operating system or edition change the cost?

Yes, in four ways:

  • Edition: Standard against Datacenter changes how many core licenses you need once you run more than two VMs on a host, and the two have different prices.
  • Edition does not change CALs: the same Windows Server CAL covers both.
  • Guest operating system: Linux VMs need no Windows Server license, while Windows client guests need client licensing, and Windows Server guests count towards the two in Standard.
  • Where it runs: Azure Hybrid Benefit, dual-use rights and pay-as-you-go change what you pay for the same workload in Azure.

Features to check besides licensing

Microsoft's edition comparison for Windows Server 2022 and 2025 lists differences you may care about as much as price. Storage Spaces Direct, Network Controller and Host Guardian Hyper-V support (needed for shielded VMs) are Datacenter-only. Automatic Virtual Machine Activation needs a Datacenter-activated host (Standard appears there only as a guest of one). In Windows Server 2025, GPU partitioning is available in Standard for standalone servers, while clustered GPU partitioning needs Datacenter. Storage Replica is available in Standard with limits, so check the current limits for your volumes. If you rely on any of these, the edition decision is no longer only about the VM count.

Mixed versions and downgrade rights

A license for a newer version can be used to run an older one. Microsoft's guidance says Windows Server 2025 Datacenter can downgrade to 2022 or earlier, to Standard, or to Essentials, and Standard 2025 can downgrade to Standard 2022 or earlier, or to Essentials. Use rights remain those of the edition you acquired. CALs go the other way: a CAL must be the same version as the newest server it accesses, or newer. If you run a 2025 host with 2022 and 2019 guests, a 2025 CAL covers them all.

Which licensing route fits?

There is no single best route. A rough guide, with every point to be confirmed for your country and partner:

  • One or two small servers bought new: an OEM license from the server maker. Essentials is OEM-only. Check transfer rights and whether Software Assurance can be added.
  • Several hosts, and you want new-version rights, step-up or per-VM licensing: volume licensing with Software Assurance, for example an Enterprise Agreement. Software Assurance or a subscription is needed for per-VM licensing and Azure Hybrid Benefit.
  • You prefer a subscription through a partner: Cloud Solution Provider subscription licenses, which the Product Terms say can be assigned per VM. Confirm terms and minimums with the partner.
  • The server runs in Azure: a license-included Azure VM, or Azure Hybrid Benefit if you hold core licenses with Software Assurance or a qualifying subscription.
  • An on-premises server managed through Azure Arc, with varying demand: Windows Server 2025 pay-as-you-go.
  • Azure Local hosts: Microsoft describes a Windows Server subscription add-on billed per physical core, and Azure Hybrid Benefit for Azure Local with Datacenter licenses that have Software Assurance. Confirm the current terms.
  • You rent servers from a hosting provider: the provider licenses the software under its service provider agreement. Ask what is included, and whether you must bring your own CALs.

The Open License program is retired for new purchases, which is why older advice that starts with "buy Open licenses" is out of date.

Common mistakes

  • Licensing only the cores in use, or only the VMs on a host today, instead of every physical core and the most VMs that can run there after a failover.
  • Forgetting the minimums: a small host still needs 16 core licenses, and each processor counts as at least 8 cores.
  • Counting Linux VMs against Standard.
  • Assuming Datacenter pays off at a fixed VM count, instead of working it out from the two prices you are quoted.
  • Scaling CALs with VMs or hosts instead of people or devices.
  • Forgetting RDS CALs for Remote Desktop Services users.
  • Buying CALs older than the newest server version they access.
  • Assuming License Mobility applies to Windows Server.
  • Treating a host that also runs other roles as free: it then uses one of the two Standard OSEs.
  • Treating an online estimate as a quote or a compliance statement.

Questions to ask your reseller

  1. Which agreement and programme are we buying under, and does it offer Software Assurance or subscription licenses?
  2. What are the exact prices for Standard and Datacenter for 16 core licenses and for 2-core packs, and what is the minimum order?
  3. How many core licenses do our hosts need after the minimums, and how many Standard sets or Datacenter licenses does that mean for our VM counts?
  4. If VMs can move between hosts, how should we license the cluster for failover and maintenance, and what are the reassignment limits for our agreement?
  5. Do we qualify to license by virtual machine, and would it be cheaper than licensing the hosts?
  6. Which CALs do we need (user or device), which version, and are any users or servers exempt?
  7. Do we need RDS CALs, and which type?
  8. Do any Microsoft 365 or other subscriptions we hold include CAL rights?
  9. What does Software Assurance give us here, and what does it cost over the term?
  10. If we move workloads to Azure, Azure Local or Azure Arc, which licenses carry over, and what happens when Software Assurance or the subscription ends?
  11. Can you put the license position in writing, including the Product Terms version you relied on?

The calculator has a button that copies these questions and the mistakes list as plain text.

Use the calculator

The Windows Server licensing calculator applies the rules above in your browser: it counts core licenses per host with the minimums, the number of Standard sets, Datacenter against Standard for your VM count, user against device CAL counts, RDS CALs, Essentials limits and a checklist of when a CAL is and is not needed. Its price fields are pre-filled with the Microsoft list prices above, dated and linked on the page, and every one stays editable with a reset button: $1,176 for Standard and $6,771 for Datacenter (16 core licenses), and $264 for a Remote Desktop Services user or device CAL from the Microsoft Store (US). Microsoft publishes no standalone price for the Windows Server CAL or for Essentials (OEM-only), so those are left empty for your quote. From the prices in the fields it computes the one-off licence cost of Standard sets against Datacenter, adds the CALs when you enter a price, and finds the break-even VM count. List prices exclude tax, partner discounts and agreement pricing, so confirm with your reseller. Nothing leaves your browser. It is an estimate, not licensing advice, so confirm the result with a Microsoft licensing specialist or your reseller before buying. If you manage Microsoft 365 seats too, the Microsoft 365 license cost calculator works the same way with dated Microsoft list prices in USD or INR, and the resources hub collects the other tools and guides.

Sources

Rules checked 1 November 2026. Pages can change, so check the date on each before you rely on it: