Windows Server licensing calculator
Work out how many Windows Server core licences a Hyper-V host needs, how many full Standard sets you would stack for your VMs, whether Datacenter is cheaper, and how many CALs and RDS CALs to plan for. Rules for Windows Server 2022 and 2025 were checked against Microsoft sources on 1 November 2026, and the price fields start at Microsoft's published list prices, which you can edit.
This is an estimate, not licensing advice. The price fields are pre-filled with Microsoft's published list prices (dated and linked below the fields) so you can see what the licences are listed at; you can change any of them to your own quote. List prices exclude tax, partner discounts and agreement pricing, and a field is left empty where Microsoft publishes no price. Agreements differ (volume licensing, CSP, OEM, Software Assurance, subscription), so confirm the result with a Microsoft licensing specialist or your reseller before you buy. The calculation runs in this browser and nothing is sent or saved.
1. Your hosts
2. Editions to compare
3. Client access licences
4. Prices Microsoft list prices, editable
Microsoft list prices are filled in when the page loads. Prices left empty have no published Microsoft price: enter your quote.
Break-even between Standard and Datacenter depends only on the ratio of the two prices. You will read that Datacenter pays off at about 7 to 8 VMs per host, or at about a dozen. Which is right depends on the prices you actually pay, so this page computes it from the two 16-core prices in the fields above (Microsoft list prices until you change them) instead of repeating a rule of thumb. CALs cost the same under both editions and do not change the break-even.
5. Software Assurance and Azure optional
The rules this tool applies
- Standard and Datacenter are licensed by physical core, with a minimum of 8 core licences per processor and 16 per server. Core licences are sold in packs of 2.
- Standard covers two operating system environments (OSEs), meaning virtual machines or Hyper-V-isolated containers, per fully licensed host. For more, you license the host again with the same number of core licences for each extra pair (stacking). Datacenter covers any number.
- Windows Server containers without Hyper-V isolation do not count towards the two. A Hyper-V-isolated container counts as one OSE.
- Cluster hosts must each be licensed for the most VMs that can run on them, because licences cannot normally be moved between servers within 90 days.
When you need a CAL
- Every person (user CAL) or device (device CAL) that accesses a Windows Server you license with Standard or Datacenter, including your employees and onsite contractors. Each user or device needs one, however many servers it uses.
- People or devices using Remote Desktop Services also need an RDS CAL in addition to the Windows Server CAL.
- External users (customers, partners) need CALs or an External Connector licence for each physical server they access, unless an exemption below applies.
- The CAL version must be the same as or newer than the server version it accesses (a 2025 CAL covers 2025, 2022 and 2019).
When you do not
- Access by another licensed Windows Server (server-to-server).
- Access to a web workload or an HPC workload (the Product Terms use these terms; check their definitions before relying on this for a site that signs users in).
- Use of the physical host 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 needs no Windows Server CALs for standard functionality (RDS CALs are still needed).
- Servers that do not run Windows Server, such as Linux VMs, do not need Windows Server CALs.
- Microsoft 365 E3 or E5 user subscriptions and the Core CAL Suite count as CAL equivalents for the access they cover; confirm for your plan.
Unclear cases to confirm with Microsoft or your reseller: anonymous internet access to a server that does not sign visitors in (public web workloads are exempt, but the exact definition sits in the Product Terms glossary), indirect access through another application, and any server that issues or manages identities for external users.
Worked examples (core licences, no prices)
| Setup | Core licences per host | VMs licensed per host | Standard sets per host | Standard core licences in total | Datacenter core licences in total |
|---|---|---|---|---|---|
| Small office host: 1 processor with 4 cores, 2 VMs | 16 | 2 | 1 | 16 | 16 |
| 1 processor with 8 cores, 6 VMs | 16 | 6 | 3 | 48 | 16 |
| 1 host, 2 processors with 12 cores each, 10 VMs | 24 | 10 | 5 | 120 | 24 |
| 1 host, 2 processors with 16 cores each, 20 VMs | 32 | 20 | 10 | 320 | 32 |
| 2 hosts, 10 VMs in total (5 per host), VMs stay on their host | 24 | 5 | 3 | 144 | 48 |
| 2 hosts, 15 VMs in total (up to 8 per host), VMs stay on their host | 24 | 8 | 4 | 192 | 48 |
| 2 hosts, 10 VMs on each host (20 in total) | 24 | 10 | 5 | 240 | 48 |
| 2 hosts, 15 VMs on each host (30 in total) | 24 | 15 | 8 | 384 | 48 |
| 2-node cluster, 10 VMs in total that can run on either host | 24 | 10 | 5 | 240 | 48 |
| 2-node cluster, 15 VMs in total that can run on either host | 24 | 15 | 8 | 384 | 48 |
Check: 1 host with 2 x 12 cores is 24 core licences. Ten VMs need 5 sets of Standard, so 5 x 24 = 120 core licences, against 24 for Datacenter. If the same ten VMs live on two hosts and can move between them, each host must be licensed for all ten, so Standard needs 5 x 24 x 2 = 240 core licences, against 48 for Datacenter. If they are pinned, 5 per host needs 3 sets per host, so 144.
Where Datacenter becomes cheaper
| Price ratio | Datacenter cheaper from this many VMs per host | Same cost at |
|---|---|---|
| 4 | 9 | 7 to 8 |
| 5 | 11 | 9 to 10 |
| 5.5 | 11 | none |
| 6 | 13 | 11 to 12 |
| 7 | 15 | 13 to 14 |
Does the edition or version change the cost?
- Standard or Datacenter changes the number of core licences you need once a host runs more than two Windows Server VMs. It does not change the CAL cost.
- Features to check: Storage Spaces Direct, Network Controller and Host Guardian Hyper-V support (shielded VMs) are Datacenter-only in Windows Server 2022 and 2025. Automatic Virtual Machine Activation for guests needs a Datacenter host. Storage Replica is in Standard with limits, so check the current limits.
- Essentials is OEM-only, for up to 25 users and 50 devices, one server with up to 10 cores on a single processor, and one running instance.
- Mixed versions: licences for a newer version can run an older version under downgrade rights, but a CAL must match the newest server it accesses or be newer.
- Linux and other non-Windows guests need no Windows Server licence. Windows client (VDI) guests need client licensing such as Windows VDA or Windows 11 Enterprise subscriptions.
Which licensing route fits?
| Your situation | Route to look at | Watch for |
|---|---|---|
| One or two small servers bought new | OEM licence from the server maker | Essentials is OEM-only. Check transfer rights and whether Software Assurance can be added. |
| Several hosts, 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 licensing per VM and for Azure Hybrid Benefit. |
| You prefer a subscription through a partner | Cloud Solution Provider subscription | Subscription licences can be assigned per VM; confirm the terms and minimums with the partner. |
| The server runs in Azure | License-included Azure VM, or Azure Hybrid Benefit | Hybrid Benefit needs core licences with active Software Assurance or a qualifying subscription. |
| An on-premises server you manage through Azure Arc, with varying need | Windows Server 2025 pay-as-you-go | Billed per core; same rate for both editions; no extra VM rights; RDS CALs still needed. |
| Azure Local hosts | Windows Server subscription add-on, or Azure Hybrid Benefit with Datacenter and Software Assurance | Confirm current Azure Local terms. |
| You rent servers from a hosting provider | The provider licenses it (service provider agreement) | Ask what is included and whether you must bring your own CALs. |
Common mistakes
- Licensing only the cores in use or the VMs on a host today, instead of all physical cores and the most VMs that can run there after a failover.
- Forgetting the minimums: a small host still needs 16 core licences, and each processor counts as at least 8 cores.
- Counting Linux VMs against Standard. Only Windows Server guests use Windows Server virtualization rights.
- Assuming Datacenter always pays off at a fixed VM count. It depends on the two prices you are quoted.
- Thinking CALs depend on the number of VMs or hosts. They depend on the people or devices that access the servers.
- Forgetting RDS CALs when users connect to Remote Desktop Services; they are extra and need Windows Server CALs too.
- Buying CALs older than the server version. The CAL must be the same version as the newest server it accesses, or newer.
- Assuming License Mobility applies to Windows Server. It does not under Software Assurance, according to Microsoft.
- Treating a Hyper-V host that also runs other roles as free. It then uses one of the two Standard OSEs.
- Treating this or any online estimate as a quote or a compliance statement.
Questions to ask your reseller
- Which agreement and programme are we buying under (OEM, volume licensing, Cloud Solution Provider, other), and does it offer Software Assurance or subscription licences?
- What are the exact prices for Standard and Datacenter, for 16 core licences and for 2-core packs, and what is the minimum order?
- How many core licences do our hosts need after the minimums (8 per processor, 16 per server), and how many Standard sets or Datacenter licences does that mean for our VM counts?
- If VMs can move between hosts, how should we licence the cluster for failover and maintenance, and what are the reassignment limits for our agreement?
- Do we qualify to license by virtual machine, and would that be cheaper than licensing the hosts?
- Which CALs do we need (user or device), which version, and are any of our users or servers exempt (external users, web workloads)?
- Do we need RDS CALs, and which type, for our remote desktop or application users?
- Do any Microsoft 365 or other subscriptions we already hold include CAL rights?
- What does Software Assurance give us here (new versions, step-up, disaster recovery, Azure Hybrid Benefit), and what does it cost over the term?
- If we move workloads to Azure, Azure Local or Azure Arc, which licences carry over, and what happens when Software Assurance or the subscription ends?
- Can you put the licence position in writing, including the version of the Product Terms you relied on?
Not covered: pricing for licensing per virtual machine, Windows client and VDI licences (see the guide linked below), SQL Server and other products, Software Assurance prices, partner or hoster licensing, and discounts. Totals are the prices in the fields multiplied, not a quote: Microsoft list prices exclude tax, partner discounts and agreement pricing, so confirm with your reseller.