About this article: AI-assisted writing, reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When a business moves its servers to a hosting provider, one question comes up early and is often answered vaguely: who licenses Windows Server, and how much licensing is needed? The answer depends on whose hardware the servers run on, whether that hardware is shared with other customers, and which licensing agreement applies.
The worked core and operating-system-environment examples below use Microsoft's EA/EAS commercial-licensing Product Terms view as read on 14 November 2026. Those examples must not be applied wholesale to SPLA or Azure Arc Pay-as-you-go, which have separate programme terms. It is a guide to the questions to ask, not legal or licensing advice. Licensing terms change, and your agreement with Microsoft or your provider is what counts.
Why it matters
Licensing mistakes are expensive in both directions. Under-licensing exposes a business to audit findings and back-payments. Over-licensing, such as buying licences for a whole physical server when the provider already includes them, wastes money every year.
There is also a responsibility point that surprises some customers. Microsoft's terms say: Customer is responsible for all of the obligations under its volume licensing agreement regardless of the physical location of the hardware upon which the software is used. Moving servers to a provider does not move your licensing obligations to the provider unless the provider is supplying the licences.
How it works
Licences are counted by physical cores
Windows Server Standard and Datacenter are licensed per core. Microsoft's Product Terms set the count: The number of Licenses required equals the number of Physical Cores on the Licensed Server, subject to a minimum of 8 Licenses per Physical Processor and a minimum of 16 Licenses per Server.
Some worked examples of that rule:
| Physical server | Cores | Core licences needed |
|---|---|---|
| One processor, 6 cores | 6 | 16 (server minimum) |
| One processor, 12 cores | 12 | 16 (server minimum) |
| Two processors, 6 cores each | 12 | 16 (server minimum) |
| Two processors, 16 cores each | 32 | 32 |
Note what is counted: the cores of the physical server, not the virtual processors given to a virtual machine.
Standard and Datacenter differ in how many virtual machines they cover
Licensing every core of a server with Datacenter covers all the Windows Server virtual machines on it. The terms say: Datacenter edition permits use of the server software in any number of OSEs on the Licensed Server. An OSE, or operating system environment, is in practice a physical or virtual installation of the operating system.
Under that physical-core model, licensing every core with Standard covers two operating system environments. The terms allow an additional Windows physical-host instance alongside two virtual OSEs only if the physical OSE is used solely to host and manage those virtual OSEs. If the physical Windows host also runs business workloads, it consumes one of the two OSE entitlements. Additional full core-licence sets grant further pairs of OSEs; verify the host workload and total OSE count before doing the arithmetic.
So for a server running two Windows virtual machines, Standard is usually cheaper. For a server running many, Datacenter usually is. Where the break-even point lies depends on current prices, which this article does not quote.
Licensing a single virtual machine
There is a second model designed for virtual machines. Under the heading Licensing by Individual Virtual OSE, the terms allow licensing one virtual machine by its own virtual cores, subject to a minimum of 8 Licenses per Virtual OSE.
This model has a condition. Microsoft says it is Available for subscription licenses or licenses with active Software Assurance only. A one-off perpetual licence without Software Assurance does not qualify. The individual-virtual-OSE clause also requires each CAL used for access to be a subscription or have active Software Assurance. Check both server and applicable access licences; meeting the server condition alone is insufficient.
Access licences are separate
Core licences cover the server software. People and devices that use the server generally need client access licences as well, with some exceptions in the terms, such as web workloads. Remote Desktop access generally needs its own access licences on top; check the current Product Terms for the conditions. Check access licences separately during a migration.
Who supplies the licence on a hosted server
First identify who supplies the licence and which programme grants the rights. The EA/EAS worked examples above do not establish the complete counting or access rules under other programmes. Three arrangements to investigate are listed below.
1. The provider supplies Windows Server
Some hosting providers include Windows Server in the monthly price. They license it through Microsoft's Services Provider License Agreement (SPLA), under which providers license eligible Microsoft products on a monthly basis, during a three-year agreement term, to host software services and applications for their customers.
SPLA product rights come from the applicable Services Provider Use Rights (SPUR), not from the EA/EAS examples above. Confirm the provider's counting, reporting and access-entitlement obligations under that programme. Where the provider includes Windows Server, you usually do not separately buy customer core licences for the same covered instances. Ask the provider to confirm in writing that Windows Server is included, which edition, and whether access licences such as Remote Desktop access are included or extra.
2. You bring your own licences
If you already own Windows Server licences, the rules depend on whether the provider's hardware is dedicated to you.
On hardware dedicated to you, Microsoft's terms allow use on devices managed by an Authorized Outsourcer, provided all such devices are and remain fully dedicated to Customer’s use.
On shared hardware, the Flexible Virtualization Benefit in the cited terms allows use on shared servers managed by an Authorized Outsourcer for qualifying subscription licences or licences with active Software Assurance, including the applicable CALs. Check the access licences as well as the server licences before relying on that benefit.
In both cases the provider must qualify. Microsoft defines an Authorized Outsourcer as any third party service provider that is not a Listed Provider and is not using Listed Provider as a Data Center Provider as part of the outsourcing service. The Listed Providers are named by Microsoft at aka.ms/listedproviders and include the largest public cloud companies. Different rules apply there.
3. Pay-as-you-go through Azure Arc
For Windows Server 2025, Microsoft also offers a subscription billed through Azure, for servers outside Azure. Microsoft describes it as an alternative to the conventional perpetual licensing for Windows Server 2025. It works per machine: Each VM requires its own separate license, regardless of the host server. It requires Windows Server 2025 and the Azure connected machine agent, with the documented activation and connectivity prerequisites. Unlike the ordinary commercial-licensing access model, Microsoft says Arc Pay-as-you-go does not require CALs for standard functionality, but RDS CALs remain required. Its per-device rights do not grant extra guest-VM rights merely because the host is licensed. Whether it suits a hosted server depends on your provider, product terms and agreement.
What to choose and why
Start with three questions to the provider
- Is Windows Server included in your price for my servers, and if so, under which programme?
- Are my servers on hardware dedicated to me, or on shared hardware?
- Are you a Listed Provider, or using one as your data centre provider?
The answers decide which of the three arrangements is even available.
Then check what you already own
List any Windows Server licences you hold, whether they have active Software Assurance or are subscriptions, and which agreement they are under. Licences without Software Assurance generally cannot be used on a provider's shared hardware.
Avoid paying twice
If the provider includes Windows Server, existing licences you own may not be needed for those servers. If you bring your own, make sure the provider is not also charging for Windows Server.
Keep the evidence
Keep the provider's written confirmation, your licence records and a list of servers with their edition and core counts. That is what an audit will ask for.
Risks and limits
- This is not licensing advice. Product Terms are long and change; confirm your situation with your licensing partner, provider or Microsoft.
- Terms quoted here are from the Windows Server 2025 Product Terms entry as published on 14 November 2026. Earlier versions and other agreements may differ.
- Licence reassignment has limits. Microsoft's terms generally do not allow reassigning a licence to another device within 90 days of the last reassignment, with listed exceptions; plan moves accordingly.
- No prices are given. Prices vary by agreement, region and provider.
- Other software has its own rules. SQL Server, in particular, is licensed separately and differently.
Sources
Opened 14 November 2026.
- Microsoft Product Terms: Windows Server Standard, Datacenter, and Essentials, as published 14 November 2026.
- Microsoft Product Terms: Universal License Terms for all software, as published 14 November 2026.
- Microsoft Product Terms: Glossary, as published 14 November 2026.
- Microsoft Volume Licensing: Licensing options for service providers, page undated.
- Microsoft Learn: Configure Windows Server Pay-as-you-go with Azure Arc.
Related service: Managed support.
Related future topics
- SQL Server licensing on hosted virtual machines.
- Remote Desktop access licences for hosted applications.
- Preparing licence records before a server migration.
Learning notes
- In the EA/EAS physical-core model described here, license every physical core, with at least 8 per processor and 16 per server. Other programmes need their own terms checked.
- Under that model Datacenter permits unlimited OSEs; Standard permits two, plus a Windows physical host only when it solely hosts and manages the virtual OSEs.
- Individual-VM licensing has an 8-core minimum and requires qualifying server subscriptions or active Software Assurance; the applicable CALs must also be subscriptions or have active Software Assurance.
- Some providers include Windows Server in their monthly price through SPLA.
- Bringing your own licences depends on dedicated or shared hardware, Software Assurance and the provider's status.
This article was originally published on .