Windows Server 2025 Licensing: Cores, Editions, CALs, Downgrade Rights
Published October 23, 2026 · Updated October 23, 2026
Windows Server 2025 Standard and Datacenter are licensed by physical core: a minimum of 8 core licenses per processor and 16 per server, plus a CAL for every user or device that accesses the server. Standard covers two operating system environments, Datacenter any number; Essentials is the small-business edition for one server with up to 10 cores, 25 users and 50 devices. With downgrade rights you may run an earlier version of the same or a lower edition instead of 2025. This article explains the rules with worked examples and puts the Azure Arc subscription option in context.
Contents
- The three editions at a glance
- Core licensing: 8 per processor, 16 per server
- Standard or Datacenter: the virtualization question
- Access licenses: CAL and RDS CAL
- Downgrade and down-edition rights
- Subscription instead of purchase: pay-as-you-go through Azure Arc
- What is technically new in 2025
- Support dates and upgrade paths
- Used licenses for Windows Server 2025
- Frequently asked questions
The three editions at a glance
Microsoft offers Windows Server 2025 in the editions Standard, Datacenter, Datacenter: Azure Edition and Essentials. Three of them matter when you buy a perpetual license; according to Microsoft, the Azure Edition is available only to customers with Software Assurance, a Windows Server subscription or in the cloud.
| Edition | License model | Virtual environments | Access |
|---|---|---|---|
| Standard | core licenses, at least 16 per server | 2 per fully licensed server | CAL per user or device |
| Datacenter | core licenses, at least 16 per server | unlimited | CAL per user or device |
| Essentials | server license for one processor with up to 10 cores | 1 VM | up to 25 users, 50 devices |
Standard and Datacenter are technically much the same; the difference lies in the use rights, above all for virtualization. According to Microsoft, Essentials is for small businesses with up to 25 users and 50 devices: one server license covers up to 10 cores and one virtual machine on a single-socket server, and the software may be used as one running instance in the physical environment.
Core licensing: 8 per processor, 16 per server
Standard and Datacenter are licensed by the physical cores of the server. Two minimums always apply: at least 8 core licenses per physical processor and at least 16 core licenses per server. The licenses are sold in 2-packs and 16-packs. This gives the numbers for typical servers:
| Server | Physical cores | Core licenses | Reason |
|---|---|---|---|
| 1 processor with 8 cores | 8 | 16 | minimum per server |
| 1 processor with 16 cores | 16 | 16 | one 16-pack |
| 2 processors with 6 cores each | 12 | 16 | minimum per processor and server |
| 2 processors with 12 cores each | 24 | 24 | all cores |
| 2 processors with 32 cores each | 64 | 64 | all cores |
So count the physical cores per processor first, round each processor up to at least 8, and check that the total reaches at least 16. Hyperthreading does not matter; physical cores are what count.
Standard or Datacenter: the virtualization question
The core license is built the same way for both editions; the difference lies in the operating system environments (OSEs) you may run with it. According to Microsoft, Windows Server Standard provides rights to use two operating system environments, physical or virtual. For each additional set of two virtual environments or two Hyper-V containers, the server must be relicensed for the same number of core licenses. Datacenter provides rights to use an unlimited number of operating system environments and Windows containers with Hyper-V isolation.
A worked example for a server with 16 cores:
| Virtual machines on the host | Standard: core licenses | Datacenter: core licenses |
|---|---|---|
| 2 VMs | 16 | 16 |
| 4 VMs | 32 | 16 |
| 6 VMs | 48 | 16 |
| 10 VMs | 80 | 16 |
The rule of thumb follows from the table: with few virtual machines per host, Standard is enough; with many, Datacenter becomes the smaller number of licenses. Where exactly the line falls depends on the price ratio of the editions, which you can clarify in your quote request. According to Microsoft, licensing by virtual machine instead of by host requires subscription licenses or active Software Assurance and is not possible with perpetual licenses alone.
Access licenses: CAL and RDS CAL
Besides the server license, Standard and Datacenter require a Windows Server 2025 CAL (client access license) for every user or device that accesses the server. A user CAL permits one user to access from any device; a device CAL permits one device to be used by any user. For Remote Desktop Services, the RDS CAL comes on top. How to count and which CAL version matches which server is explained in Windows Server CAL: user or device CAL and in RDS CAL explained.
Essentials has no such CAL requirement; the limits of 25 users and 50 devices apply instead. Remote Desktop Services are not licensed for use with Essentials.
Downgrade and down-edition rights
With a Windows Server 2025 license you may, according to Microsoft, also run earlier versions of the same edition or lower editions, provided you have the appropriate media and keys. Microsoft calls these downgrade rights and down-edition rights. Two cases from practice:
- An application requires an older version: you buy Windows Server 2025 Standard and install Windows Server 2019 Standard. The license remains a 2025 license; support for the installed version follows that version's lifecycle.
- Datacenter bought, Standard needed: a Datacenter license may be run as Standard, not the other way around.
The counterpart applies to access licenses: if users access an earlier version installed under downgrade rights, the license terms allow you to use CALs of that earlier version as well. The dates of the older versions are summarized in Planning for Microsoft end of support.
Subscription instead of purchase: pay-as-you-go through Azure Arc
New with Windows Server 2025 is a subscription option that Microsoft describes as an alternative to conventional perpetual licensing: pay-as-you-go through Azure Arc, billed through your Azure subscription. Requirements according to Microsoft: Windows Server 2025 Standard or Datacenter, an Azure Arc-enabled server running the agent version 1.47 or later, and no other activation. Standard and Datacenter are billed at the same rate, with no minimum core count per machine; each virtual machine requires its own license; the first seven days are a free trial.
Two points decide the comparison with a perpetual license. First: with pay-as-you-go, no CALs are required for standard functionality, but RDS CALs still are. Second: a subscription ends when the payments stop; a perpetual license does not. If you run servers for many years and do not want a cloud connection, stay with the perpetual license; if you scale workloads up and down at short notice, run the numbers on the subscription. What separates CSP subscriptions from perpetual licenses is explained in CSP license explained.
What is technically new in 2025
The licensing rules are one reason for 2025, the technology is the other. Microsoft names, among other things:
- Hotpatching: security updates without a restart. For Windows Server 2025 Standard and Datacenter, Hotpatch through Azure Arc is available at no extra cost according to Microsoft's Hotpatch page; the overview of new features still lists it as a preview. For Windows Server 2022, Hotpatch existed only in the Azure Edition.
- Active Directory: an optional 32k database page size instead of 8k, with what Microsoft calls a huge improvement in areas affected by legacy restrictions.
- SMB over QUIC: previously only in the Azure Edition, now in Standard and Datacenter.
- NVMe: optimized storage performance with more IOPS and lower CPU utilization.
- Hyper-V: GPU partitioning, one physical GPU shared by several virtual machines.
Support dates and upgrade paths
Windows Server 2025 follows the Fixed Lifecycle Policy. The lifecycle page gives the start date as November 1, 2024, the end of mainstream support as November 13, 2029 and the end of extended support as November 14, 2034; the page shows the end dates as timestamps at 6:59 AM Pacific Time on the following day.
| Phase | Date |
|---|---|
| Release | Nov 1, 2024 |
| End of mainstream support | Nov 13, 2029 |
| End of extended support | Nov 14, 2034 |
Microsoft has relaxed the upgrade rules: starting with Windows Server 2025, nonclustered systems can upgrade up to four versions at a time, directly from Windows Server 2012 R2, 2016, 2019 and 2022; up to Windows Server 2022 it was two versions. Through Windows Update, the upgrade works from 2019 and 2022. The edition is kept during an upgrade; changing from Standard to Datacenter is allowed, from Datacenter to Standard it is not. And unlike Windows client, each Windows Server upgrade requires a separate license. What the end of support of 2025 and the comparison with 2022 mean for your planning is covered in Windows Server 2025 end of life.
Used licenses for Windows Server 2025
Core licenses and CALs for Windows Server 2025 from volume licensing agreements are perpetual licenses. They may be resold in the EU: under Article 4(2) of Directive 2009/24/EC, the distribution right is exhausted by the first sale of a copy of the program in the Union by the rights holder or with the rights holder's consent, and in case C-128/11 the Court of Justice of the European Union ruled that the rights holder can then no longer oppose the resale, even against contract terms to the contrary. The previous owner must make their copy unusable. Subscriptions such as pay-as-you-go are excluded: they are time-limited and not transferable.
Three documents count when you buy: proof of first sale in the EU or the European Economic Area (EEA), the previous owner's declaration and an unbroken chain of ownership. Together with downgrade rights, a used 2025 license is the most flexible form: it covers 2025 and may run any earlier version. The legal framework is explained in Is used software legal?, the basics of volume licensing in our Microsoft volume licensing guide.
Frequently asked questions
How many core licenses do I need for a server with two processors of 10 cores each?
20. At least 8 apply per processor and at least 16 per server; with 2 times 10 cores both minimums are met, so you license all 20 cores, for example as one 16-pack and two 2-packs.
What is the difference between Windows Server 2025 Standard and Datacenter?
Core licensing is the same. Standard allows two operating system environments per fully licensed server, Datacenter any number. The more virtual machines run on one host, the sooner Datacenter is the smaller number of licenses.
Do I need CALs for Windows Server 2025?
Yes, for Standard and Datacenter, for every user or device that accesses the server; for Remote Desktop Services, RDS CALs come on top. Essentials has the limits of 25 users and 50 devices instead. With pay-as-you-go through Azure Arc, CALs for standard functionality are not required, but RDS CALs remain necessary.
May I install Windows Server 2019 with a 2025 license?
Yes. Downgrade rights allow earlier versions of the same edition or lower editions if you have the media and keys. For access, you may then also use CALs of version 2019.
What is Windows Server 2025 Essentials?
The edition for small businesses: one single-socket server with up to 10 cores, one virtual machine, up to 25 users and 50 devices, without CALs. Remote Desktop Services are not licensed for use with it.
How long will Windows Server 2025 be supported?
Mainstream support until November 13, 2029, extended support until November 14, 2034.
Can I upgrade from Windows Server 2016 directly to 2025?
Yes. Starting with Windows Server 2025, in-place upgrades across up to four versions are possible, from 2012 R2, 2016, 2019 and 2022. Each upgrade requires its own license.
What Lizenzus does for you
We supply used licenses for Windows Server 2025 Standard and Windows Server 2025 Datacenter with the matching CALs, each with the three documents. The overview of all versions is at Windows Server licenses. In your quote request, tell us the number of processors and cores per server, the number of virtual machines and the number of users and devices; we work out the core licenses and CALs from that. Your quote request is non-binding.
Sources
- Microsoft Licensing: Windows Server 2025 licensing guidance, accessed October 23, 2026
- Microsoft Learn: Locks and limits for Windows Server, accessed October 23, 2026
- Microsoft Learn: Windows Server Datacenter: Azure Edition, accessed October 23, 2026
- Microsoft Learn: Windows Server pay-as-you-go, accessed October 23, 2026
- Microsoft Learn: Billing for Windows Server pay-as-you-go, accessed October 23, 2026
- Microsoft Learn: Hotpatch for Windows Server, accessed October 23, 2026
- Microsoft Learn: What's new in Windows Server 2025, accessed October 23, 2026
- Microsoft Learn: Install, upgrade, or migrate to Windows Server, accessed October 23, 2026
- Microsoft Learn: Windows Server 2025 lifecycle, accessed October 23, 2026
- Microsoft: Microsoft License Terms, Windows Server 2025 Datacenter and Standard, sections 3 to 5, accessed October 23, 2026
- Microsoft: Microsoft Customer Agreement, section License transfers, accessed October 23, 2026
- Official Journal of the EU: Directive 2009/24/EC, Article 4(2)
- Court of Justice of the EU, judgment of July 3, 2012, C-128/11 UsedSoft, paragraphs 70 and 77
Where to read on
Three pages answer the questions that most often follow on from this article.
Legal position and evidence
Why trading in used volume licenses is lawful, where the limits lie and which four documents count in a license audit.
Purchasing basics
What a used license is, which forms are transferable and how to recognize an offer that stands up to scrutiny.
Public procurement
The procurement law framework, suggested wording for the specification and the documents for the procurement file.
A question about your specific case?
Describe your situation. You will receive an assessment and, if you wish, a quote.