Windows Server licensing in 2026. Cores, editions, CALs and cloud rights.

Windows Server is licensed per physical core, with 16 cores minimum per server, plus a CAL for every user or device. The edition you pick per host, and the cloud rights you keep through SA, decide most of the cost.

How is Windows Server licensed in 2026?

Windows Server Standard and Datacenter are licensed per physical core, with a minimum of 16 core licenses per server and 8 per processor. Every user or device that reaches the server also needs a Client Access License (CAL). Essentials, the small business edition, is the exception: it is sold per server and needs no CALs.

The edition then sets how many virtual machines each licensed host may run. Most cost errors come from counting one of these layers against the wrong rule. For the wider Microsoft picture, see our Microsoft knowledge hub.

The core counting rules

• 16 cores per server minimum. An 8 or 12 core server still needs 16 core licenses.
• 8 cores per processor minimum. A 4 core processor still needs 8 core licenses.
• Packs of 2 and 16. Core licenses are sold in 2 core packs and 16 core packs.
• Every physical core counts. Microsoft requires one core license per physical core, and disabling cores does not reduce the requirement.
• Hyperthreading is ignored. Only physical cores are counted.

What core counting looks like on real servers

The prices are Microsoft's suggested list prices for 16 core licenses: $1,176 for Standard and $6,771 for Datacenter. Your Enterprise Agreement or CSP price will differ. At list, Datacenter costs about 5.8 times Standard for the same cores, and that ratio in your own price sheet decides the edition question.

The three deployment paths

• On premises. Perpetual core licenses, usually with Software Assurance (SA) under an Enterprise Agreement, or bought through CSP.
• Azure. Pay for Windows inside the VM rate, or bring licenses with active SA under Azure Hybrid Benefit.
• Other public clouds. AWS, Google Cloud and Alibaba include Windows Server in the instance price, and bringing your own license is heavily restricted.

Windows Server 2025 also added pay as you go billing through Azure Arc for servers you run yourself, at $33.58 per core per month. A full year costs $402.96 per core, close to the $423 per core of a perpetual Datacenter license at list, without the unlimited virtualization right.

Which Windows Server edition do you need: Standard, Datacenter or Essentials?

Pick by virtual machine density per host. Standard fits physical servers and lightly virtualized hosts, Datacenter fits dense virtualization hosts, and Essentials fits one small office server. The 2022 and 2025 releases follow the same structure.

Standard edition

Once every physical core is licensed, Standard allows 2 operating system environments (OSEs), meaning 2 VMs or 2 Hyper-V isolated containers, plus the Hyper-V host itself if it only hosts and manages those VMs. More VMs on the same host require licensing all the cores again, which is called stacking.

Datacenter edition

Datacenter allows unlimited OSEs and unlimited Hyper-V containers on a fully licensed host. It also carries Storage Spaces Direct, Network Controller for software defined networking, and Host Guardian support for shielded VMs. If you run hyperconverged storage on Windows, you need Datacenter whatever the VM count.

Essentials edition

Essentials is sold only through server manufacturers (OEM). It is licensed per server for single processor machines of up to 10 cores, allows one running instance, physical or virtual, and needs no CALs. The hard limits are 25 users and 50 devices.

When is Datacenter cheaper than stacking Standard licenses?

At 2025 list prices, Datacenter becomes cheaper once a host runs 11 or more VMs. Below that, stacked Standard licenses cost less. The break even is the same on any core count, because both editions are priced per core.

Many guides, including an earlier version of this page, put the break even at 6 to 8 VMs per host. That only holds if your Datacenter price sits much closer to Standard than list, or if the cluster effect below applies.

How license stacking on Standard works

Each time you license all the physical cores in a host with Standard, you gain 2 more VMs. A host with 4 VMs needs 2 sets, and a host with 6 VMs needs 3 sets. On a 32 core host one set is 32 core licenses, so each pair of VMs costs $2,352 at list.

Why clusters change the answer

Windows Server licenses are assigned to one physical server and can be reassigned only once every 90 days, unless the hardware fails permanently. Where VMs fail over or live migrate freely, each host must be licensed for the most VMs it could ever run. That pushes busy clusters toward Datacenter well before the 11 VM mark.

Why we do not put Datacenter on every host by default

Resellers and data center teams often advise licensing every virtualization host with Datacenter, so compliance never depends on where a VM lands. We disagree for hosts that run few VMs. A host running 2 VMs costs about 83 percent less on Standard at list, and the gap repeats every year through SA.

Split the hosts instead. Keep Datacenter on dense cluster nodes, and put appliances, branch domain controllers and database servers tied to one host on Standard hosts with affinity rules that keep them there. Write the rules down, because an auditor will ask how you prevent drift.

Worked example: right sizing a 10 host cluster

Say you run 10 hosts, each with two 16 core processors, all on Datacenter. Seven hosts run between 18 and 30 VMs each. Three hosts, held apart by affinity rules, run 4 VMs each.

SA is priced as a share of the license, so the annual SA line falls in roughly the same proportion. The saving holds only while those three hosts stay at 4 VMs. Our server licensing calculator runs the same comparison on your own host list.

Which Client Access Licenses does Windows Server need?

Every user or device that accesses Windows Server Standard or Datacenter needs a Windows Server CAL, bought separately from the core licenses. You choose user CALs, device CALs or a mix. Remote Desktop and Rights Management access need extra CALs on top.

User CALs or device CALs?

1. User CAL. Covers one named person on any number of devices. It suits staff who work from a laptop, a phone and a home PC.
2. Device CAL. Covers one device, whoever uses it. It suits shift work on shared workstations, kiosks and terminals.

CALs must match the server version or be later, so upgrading hosts to Windows Server 2025 without SA on your CALs means buying CALs too. Microsoft 365 E3 and E5 carry Windows Server CAL equivalent rights for their licensed users, so separate CALs for those users are duplicate spend.

Extra CALs that often hide in the EA

• Remote Desktop Services CAL. Required on top of the base CAL for anyone using RDS to reach a Windows Server desktop or published app. Microsoft 365 does not include it.
• AD RMS CAL. Required on top of the base CAL to open content protected by Active Directory Rights Management Services.
• External Connector License. One per physical server, replacing CALs for external users such as customers and partners. Employees and onsite contractors never count as external.
• Public web workloads. Visitors who reach the server over the internet without signing in or being identified need no CALs, so anonymous traffic to a public site never calls for an External Connector.

How do Azure Hybrid Benefit and License Mobility apply to Windows Server?

Azure Hybrid Benefit allows Windows Server licenses with active SA or subscription to run in Azure. License Mobility through SA covers authorized third party clouds, but Windows Server is not an eligible product. On AWS, Google Cloud and Alibaba you normally pay for Windows Server in the instance price.

Azure Hybrid Benefit for Windows Server

• Active SA or subscription is required. If coverage lapses, you renew, switch the VM to the pay as you go rate, or remove it.
• Licenses map to virtual cores. 16 core licenses cover up to 16 virtual cores, with a minimum of 8 per VM, for Standard and Datacenter alike.
• Standard runs in one place. Standard licenses run on premises or in Azure, apart from a one time 180 day migration window.
• Datacenter runs in both. Datacenter licenses can cover on premises hosts and shared Azure VMs at the same time, with no time limit.
• Unlimited VMs need a dedicated host. Datacenter covers unlimited Azure VMs only on an Azure Dedicated Host with all physical cores licensed, and there dual use on premises ends after 180 days.

Removing the Windows charge typically lowers the Azure VM cost by 30 to 40 percent, and Microsoft quotes up to 80 percent when combined with reserved instances. Our Azure Hybrid Benefit guide covers the SQL Server side.

Windows Server on AWS, Google Cloud and Alibaba

Microsoft excludes Windows Server from License Mobility through SA. Since October 1, 2019, AWS, Google, Alibaba and Microsoft are Listed Providers, and licenses bought after that date cannot be brought to their dedicated hosts. Older licenses, for versions released before that date, can still run there, and the Flexible Virtualization Benefit excludes Listed Providers.

What SA adds through Azure Arc

SA or a subscription license also brings Windows Server Management enabled by Azure Arc at no extra license cost, including Azure Update Manager, Change Tracking and Inventory, and Windows Admin Center. Price SA against the rights you will use, as set out in our Software Assurance guide.

What have we seen in Windows Server licensing reviews?

The largest avoidable cost is Datacenter on hosts where Standard would do. Many enterprises license every host with Datacenter because the data center team standardized on it years ago. Auditing density and moving the low density hosts to Standard typically saves 15 to 25 percent on the Windows Server line.

The second pattern is CAL drift: RDS CALs counted across both user and device categories, and base CALs renewed for people who have left. These are the ranges our reviews typically return.

Our Microsoft advisory practice runs these reviews from the offices on our locations page, and our about us page sets out who we are and why we take no vendor fees.

Windows Server cost follows the edition mix, the CAL count and the cloud rights you actually use, so count all three from your own inventory before the renewal quote arrives.

What will Microsoft say at renewal, and how should you answer?

Expect the account team or reseller to steer toward more Datacenter, full SA coverage and more Azure. These lines come up most often.

• "Datacenter on every host is the only safe way to cover live migration." It is the simplest way, and on dense clusters the cheapest. Show the density sheet and affinity rules for low density hosts, and ask for both editions to be priced.
• "You need SA on everything to keep Hybrid Benefit." Under the Server and Cloud Enrollment, SA covers the whole installed base of a component in return for a discount. Outside it, SA is needed only on licenses used in Azure, so price both routes.
• "Your CAL count should equal headcount." Active Directory sign in counts as access, so most employees need coverage. Exclude Microsoft 365 E3 or E5 users and shift workers on device CALs.
• "Pay as you go through Azure Arc is simpler." It suits short projects and bursts. For a server that runs all year, you pay roughly the perpetual Datacenter price per core again every year, and unlimited virtualization is not included.

Contract terms to ask for in the Server and Cloud Enrollment

• Price hold for the term. Fix core license and SA prices for all three years, including licenses added at true up.
• Divestiture clause. Allow the license count and SA to fall when you sell a business unit, with rights to transfer licenses to the buyer.
• Edition exchange at renewal. Ask for the right to swap Datacenter for Standard when host density falls, without losing the enrollment discount.
• Hybrid Benefit records. Record which licenses are assigned to Azure and their SA end dates, so a lapse cannot become a back charge.

For discount comparisons across Enterprise Agreements, see our benchmarking service and the Microsoft EA renewal guide.

How do you check your own Windows Server licensing position?

Build the count from your own systems before Microsoft or a reseller runs a tool on your network. You need four figures per host: physical cores, installed edition, peak VM count and who accesses it.

• Physical cores. Run Get-CimInstance Win32_Processor in PowerShell and read NumberOfCores, or export host hardware from vCenter or System Center Virtual Machine Manager.
• VMs per host. Run Get-VM on each Hyper-V host, or export placement from vCenter, and take the peak across 90 days.
• Entitlements. Download your license summary from the Microsoft 365 admin center, which replaced the Volume Licensing Service Center.
• RDS CALs. Use RD Licensing Manager to produce per user CAL usage reports and list the per device CALs issued.
• Azure Hybrid Benefit. Check the licenseType value on each Azure VM and match every VM marked Windows_Server to a license with active SA.

What to do next

1. Inventory every host. Pull the server count, physical cores and peak VM count per host.
2. Classify edition use. Compare Standard and Datacenter against actual density and the break even table.
3. Audit CAL deployment. Match user, device and RDS CALs and Microsoft 365 rights against the workforce.
4. Activate Azure Hybrid Benefit. Apply eligible licenses to Azure VMs and confirm SA covers them for the term.
5. Sort cloud eligibility. Use License Mobility for SQL Server on AWS or Google Cloud, and price Windows Server there as license included.
6. Reclaim idle licenses. Decommission retired workloads and drop them from the SA count before the anniversary.
7. Negotiate the Server and Cloud Enrollment. Lock the term pricing, with our Renewal Program or Benchmark Program for an outside view of the quote.
8. Document divestiture protection. Write the reduction right into the enrollment, then keep the position current through Vendor Shield or a Software Spend Assessment, or contact us to scope a review.

Frequently asked questions