Windows Server licensing on a cloud VM is not just a product-key question. The correct path depends on who owns the license, where the VM runs, whether the workload is production, and whether users need Remote Desktop Services or Microsoft 365 Apps.
Raff supports Windows Server workloads through Microsoft service-provider licensing and customer-managed licensing scenarios. Microsoft’s Product Terms and your own agreement ultimately control your rights, so treat this page as practical infrastructure guidance rather than a substitute for your Microsoft licensing agreement.
In short
For most Raff Windows VM users, the choices are straightforward: use the 180-day Windows Server evaluation for short-term testing, use Raff-provided SPLA licensing for production when you do not want to bring Microsoft licenses, or evaluate BYOL under Microsoft outsourcing rights / Flexible Virtualization Benefit when your organization already owns eligible subscription licenses or licenses with active Software Assurance. Windows Server BYOL is not the same as License Mobility through Software Assurance.
The three Windows Server licensing paths are different
| Licensing path | Best fit | Key requirement | Production use |
|---|---|---|---|
| Windows Server evaluation | Labs, testing, migration checks | Evaluation edition expires after 180 days | Do not treat it as the production licensing path |
| Raff-provided SPLA | Most hosted production VMs | Raff licenses the hosted Windows Server workload under SPLA | Yes, when configured under the applicable SPLA terms |
| Customer BYOL | Organizations with eligible Microsoft licenses | Rights depend on the license program, Software Assurance/subscription status, and outsourcing model | Yes, when the customer’s Microsoft terms permit it |
The biggest mistake is treating these paths as interchangeable. They are governed by different Microsoft licensing rules.
Windows Server evaluation lasts 180 days
Microsoft provides Windows Server 2025 as a 180-day evaluation. Microsoft also states that the evaluation edition must be activated over the internet within the first 10 days to avoid automatic shutdown.
Use an evaluation VM for tasks such as:
- application compatibility testing;
- proof-of-concept deployments;
- migration rehearsals;
- learning Windows Server roles;
- short-lived development and lab environments.
Do not build a production licensing plan around repeated evaluation extensions or rearm commands. If the workload is becoming business-critical, move it to a properly licensed production path.
Microsoft supports converting eligible Windows Server evaluation installations to retail editions, subject to the edition-conversion rules for the installed version. Always check the target editions first before assuming an in-place conversion is available.
SPLA is Raff’s service-provider licensing path
Microsoft’s Services Provider License Agreement (SPLA) is designed for service providers that offer hosted Microsoft software to customers. Raff is a Microsoft SPLA partner and can provide Windows Server licensing for eligible hosted workloads through this model.
Under SPLA, Windows Server is licensed under the service-provider use rights rather than by transferring a retail key to the VM.
Microsoft’s current SPLA guidance describes Windows Server as a Per Core (OS) product. Per-core SPLA licensing generally permits users to access the licensed server software without separate Windows Server SALs, although certain Windows Server functionality requires additional SALs.
That distinction is important for Remote Desktop Services.
SPLA does not make RDS free
If a workload uses Windows Server Remote Desktop Services functionality to provide graphical user sessions, Microsoft’s current SPLA use rights list a Windows Server Remote Desktop Services SAL for each user who is authorized to use that functionality.
So the practical model is:
Windows Server under Raff SPLA + RDS SALs when users consume RDS functionality
Do not assume that the Windows Server SPLA license automatically covers multi-user RDS access.
For a deeper explanation, see RDS CAL Licensing on Windows Server.
BYOL for Windows Server uses outsourcing rights, not License Mobility
This is the most important correction to older Windows Server licensing advice.
Windows Server is not covered by License Mobility through Software Assurance. Microsoft explicitly distinguishes Windows Server from server applications such as SQL Server that can use License Mobility.
For Windows Server on a shared cloud environment operated by an eligible outsourcer, the relevant modern Microsoft path is generally the Flexible Virtualization Benefit.
Microsoft introduced the Flexible Virtualization Benefit in October 2022. It allows customers with qualifying subscription licenses or licenses with active Software Assurance to deploy eligible Microsoft software on shared or dedicated servers operated by an Authorized Outsourcer.
Microsoft specifically notes that this benefit applies to products that are not covered by License Mobility, including Windows Server.
A License Mobility verification form is not the Windows Server path
Do not use the SQL Server License Mobility workflow as a template for Windows Server.
Microsoft’s Flexible Virtualization Benefit guidance says the benefit does not require the License Mobility verification form used for License Mobility through Software Assurance.
Your Microsoft agreement, license type, Software Assurance/subscription status, and the hosting arrangement still need to qualify.
If you want to bring your own Windows Server licenses to Raff, confirm the exact entitlement with your Microsoft licensing reseller or licensing specialist before deployment.
BYOL can be licensed by VM when the eligibility rules are met
Microsoft’s current Windows Server licensing guidance allows Standard and Datacenter to be licensed either by physical cores or, for eligible customers, by virtual machine.
The per-VM option is available when the licenses are subscription licenses or have active Software Assurance.
When licensing Windows Server by VM:
- license the virtual cores allocated to the VM;
- apply a minimum of 8 core licenses per VM;
- maintain the qualifying subscription or active Software Assurance rights required for the per-VM model;
- obtain the Windows Server access licenses required by your Microsoft agreement for users/devices that access the server.
When licensing Windows Server based on physical cores, Microsoft continues to apply a minimum of 8 core licenses per physical processor and 16 core licenses per server.
This is why a 4-vCPU VM does not necessarily mean “four Windows Server core licenses” in a BYOL calculation.
Standard and Datacenter have different virtualization rights
Windows Server Standard and Datacenter use the same core-based licensing framework, but the virtualization rights differ when licensing physical servers.
At a high level:
- Standard grants rights for a limited number of Windows Server operating system environments per fully licensed physical server and can be stacked for additional OSEs.
- Datacenter permits any number of Windows Server OSEs on the properly licensed physical server.
For an individual customer VM licensed using the eligible per-VM model, the VM licensing rules are usually the more relevant calculation than host-wide virtualization rights.
Access licenses still matter under customer BYOL
Microsoft’s standard Windows Server commercial licensing model is Per Core/CAL.
That means customer-owned Windows Server licenses normally require the applicable access licenses for users or devices accessing the server software. If Remote Desktop Services is used, the separate RDS access-license requirements also apply.
This differs from the SPLA service-provider model, where Microsoft uses the SPLA licensing models and service-provider use rights instead of the customer’s normal CAL model.
Keep these models separate:
Customer BYOL → Windows Server core licenses + applicable CALs + RDS CALs if needed Raff SPLA → SPLA Windows Server licensing + RDS SALs if RDS functionality is used
RDS licensing depends on who provides the Windows license
The infrastructure can look identical while the licensing documents are different.
| Windows licensing model | Multi-user RDS access |
|---|---|
| Customer-owned Windows Server | RDS CALs under the customer’s Microsoft licensing terms |
| Raff-provided SPLA Windows Server | RDS SALs under SPLA for authorized RDS users |
| Two administrative RDP sessions | Intended for server administration, not as a substitute for an RDS user environment |
For normal employees using a shared Windows desktop to run accounting software, ERP software, Office apps, or other line-of-business tools, design the environment as an RDS workload rather than trying to use the two administrative sessions as a multi-user licensing workaround.
SQL Server follows different BYOL rules
Do not copy Windows Server BYOL rules directly to SQL Server.
SQL Server is one of the server applications that Microsoft identifies as eligible for License Mobility through Software Assurance when the applicable requirements are met. SQL Server can also be deployed under the Flexible Virtualization Benefit in eligible Authorized Outsourcer scenarios.
For SQL Server licensed by VM under the per-core model, Microsoft applies a minimum of four core licenses per VM.
Raff can also license eligible Microsoft server products under the applicable service-provider licensing model where offered.
For production SQL Server licensing, confirm the exact edition and licensing route separately from the Windows Server OS license.
Microsoft 365 Apps needs Shared Computer Activation for multi-user servers
If several users sign in to the same Windows Server and use Microsoft 365 Apps, Microsoft requires Shared Computer Activation (SCA) for that shared-computer scenario.
Microsoft currently lists SCA support for plans including:
- plans with Microsoft 365 Apps for enterprise, such as Office 365 E3 or Microsoft 365 E5;
- Microsoft 365 Business Premium;
- eligible subscription Project and Visio desktop plans.
Microsoft states that Microsoft 365 Business Standard does not include Shared Computer Activation support.
Each user still needs their own qualifying Microsoft 365 license. One user activating Office does not activate Microsoft 365 Apps for every user on the RDS server.
Current Windows Server support dates for Microsoft 365 Apps
As of August 2026:
- Windows Server 2025: Microsoft 365 Apps is supported while Server 2025 remains in Mainstream Support, currently through October 2029.
- Windows Server 2022: mainstream support for Microsoft 365 Apps on Server 2022 ends in October 2026; Microsoft says security updates for Microsoft 365 desktop apps on Server 2022 continue through October 10, 2028, with feature updates stopping at Version 2608.
- Windows Server 2019 and 2016: Microsoft 365 Apps support ended October 14, 2025, although Microsoft provides a limited security-update runway through October 10, 2028 for those existing configurations.
If Microsoft 365 Apps is central to a new RDS deployment, Windows Server 2025 has the cleaner current support horizon.
Azure Hybrid Benefit is an Azure benefit
Azure Hybrid Benefit is a Microsoft Azure-specific benefit. It does not become a generic discount mechanism simply because the same organization owns Windows Server licenses with Software Assurance.
Outside Azure, evaluate the customer’s standard outsourcing rights, Flexible Virtualization Benefit, or the hosting provider’s own service-provider licensing model instead.
OEM licenses are not a normal cloud BYOL path
OEM Windows Server licenses are associated with the hardware on which they were originally supplied. Do not assume an OEM license purchased with an office server can be reassigned to a Raff VM.
For cloud BYOL, focus on qualifying Microsoft commercial subscription licenses or licenses with the appropriate active Software Assurance / outsourcing rights.
Raff recommends choosing the licensing model before production
From an operational perspective, licensing becomes much easier when it is decided before the VM becomes business-critical.
Use this decision framework:
| Situation | Starting direction |
|---|---|
| Short-term lab or compatibility test | Windows Server evaluation |
| Production VM with no existing Microsoft entitlement | Raff-provided SPLA |
| Existing qualifying Microsoft subscription / active SA | Review BYOL under Flexible Virtualization / outsourcing rights |
| Multi-user Windows desktop under Raff SPLA | Windows SPLA + appropriate RDS SALs |
| Multi-user Windows desktop under customer BYOL | Windows Server licenses + applicable CALs + RDS CALs |
| Microsoft 365 Apps for multiple RDS users | Qualifying Microsoft 365 licenses + Shared Computer Activation |
The cheapest-looking option is not always the simplest option. BYOL can make sense for organizations that already maintain Microsoft commercial licensing, while SPLA is usually simpler when the goal is a hosted Windows VM without managing transferable license entitlements.