Windows Server Licensing: SPLA, BYOL, CALs & RDS (2026)

In short

For most production Raff Windows VM buyers, there are two practical Windows Server licensing paths: Raff-provided SPLA licensing or eligible customer BYOL. Raff currently charges $15/month per Windows Server Standard instance under its hosted SPLA model. If users need Remote Desktop Services, Raff-hosted SPLA uses RDS User SALs at $8 per authorized user per month. Customer BYOL follows Microsoft's own licensing, CAL, and outsourcing rules instead.

Windows Server BYOL is not based on License Mobility through Software Assurance. For eligible hosted scenarios, Microsoft's Flexible Virtualization Benefit and associated outsourcing rights are the relevant path.

At Raff, we treat Windows licensing as a separate deployment decision from VM sizing because the same compute plan can use Raff-provided SPLA licensing or eligible customer BYOL.

Windows Server licensing on Raff at a glance

The key question is not simply whether you own a Windows Server key. It is which Microsoft licensing model applies to this hosted workload.

Raff Windows Server licensing costs $15 per instance

Raff currently prices Windows Server Standard licensing at $15/month per instance when Raff supplies the operating-system licence through its SPLA model. That amount is separate from compute.

If the workload also uses Remote Desktop Services, add the applicable RDS licensing separately. SQL Server, Microsoft 365 Apps, backup storage, additional volumes, and third-party software are separate where applicable.

For the infrastructure breakdown, see Windows VPS Pricing.

SPLA is the simplest production path for many Raff customers

Microsoft's Services Provider License Agreement (SPLA) is the service-provider licensing framework Raff uses to provide hosted Microsoft software to customers.

Under Raff's hosted model, the Windows Server licence is supplied by Raff rather than transferred from the customer into the VM.

The practical model is:

Raff Windows VM compute
+
Windows Server Standard SPLA: $15/month per instance
+
RDS User SALs if Remote Desktop Services is used

Do not confuse this with buying or transferring a retail product key. SPLA is a service-provider licensing model.

SPLA Windows Server does not automatically include RDS

Windows Server licensing and Remote Desktop Services licensing are separate layers.

Administrative Remote Desktop connections used to manage the server are different from employees using the server as a daily shared Windows desktop or RemoteApp platform.

Under Raff's hosted SPLA model, RDS functionality uses RDS User SALs at $8 per authorized user per month.

Example for five hosted RDS users:

4 vCPU / 8 GB VM                 $40.99
Windows Server Standard SPLA     $15.00
5 RDS User SALs                  $40.00
---------------------------------------
Starting monthly total           $95.99

This does not include Microsoft 365 Apps, SQL Server, backup storage, or third-party application licensing.

For RDS-specific rules, see RDS CAL Licensing Guide.

Customer BYOL uses Microsoft's outsourcing rights

Some organizations already own eligible Windows Server licences and want to use them on hosted infrastructure.

For Windows Server, do not use License Mobility through Software Assurance as the default BYOL explanation. Windows Server is not a standard License Mobility product in the way SQL Server and certain server applications can be.

For qualifying subscription licences or licences with active Software Assurance, Microsoft's Flexible Virtualization Benefit extends outsourcing rights to eligible Authorized Outsourcer scenarios, including shared infrastructure where the Microsoft conditions are met.

Raff supports eligible customer BYOL, but the customer's Microsoft agreement, licence status, access rights, and the current Product Terms determine final eligibility.

Windows Server BYOL can use per-VM licensing when eligible

Microsoft permits eligible Windows Server Standard and Datacenter licences to be licensed by virtual machine when the customer has qualifying subscription licences or active Software Assurance.

Under that model:

• license the virtual cores allocated to the VM;
• apply at least 8 core licences per VM;
• maintain at least 16 qualifying core licences per customer;
• maintain the qualifying subscription or active Software Assurance rights;
• license users or devices that access Windows Server where CALs are required.

A 4-vCPU Windows VM therefore does not automatically mean four Windows Server core licences.

The minimums are one reason provider-supplied SPLA can be simpler for smaller hosted VMs.

Shared Authorized Outsourcer BYOL also affects access rights

When a customer uses the Flexible Virtualization Benefit in an eligible outsourcing scenario, Windows Server access rights must be reviewed alongside the server-core licences.

For workloads where CALs are required, verify that the customer has the appropriate Windows Server CAL rights and that the subscription or Software Assurance conditions required by the applicable outsourcing model are satisfied.

Do not validate only the server-core licences and ignore user or device access rights.

For a dedicated CAL explanation, see Windows Server CALs: User vs Device.

Windows Server CALs and RDS CALs are separate under BYOL

Customer-owned Windows Server licensing normally follows Microsoft's server plus access-licence model.

Windows Server core licences
+
Windows Server CALs where required
+
RDS CALs if users consume RDS functionality

An RDS CAL does not replace the base Windows Server CAL when that base CAL is required.

That differs from Raff-hosted SPLA:

Raff SPLA Windows Server
+
RDS User SALs if RDS functionality is used

Identifying who supplies the Windows Server licence should happen before counting access licences.

Two administrative RDP sessions are not a multi-user licensing model

Windows Server includes limited Remote Desktop rights for server administration. Those connections are intended for administrators maintaining the server.

They are not a substitute for a production RDS deployment used by staff for daily desktops or RemoteApp.

If employees need shared Windows sessions, plan the RD Session Host role, the correct RDS licensing model, user profiles, capacity, secure remote access, and backup/recovery.

See Multi-User RDP vs RDS Session Host.

Standard vs Datacenter does not change the first licensing decision for most Raff VMs

Windows Server Standard and Datacenter differ in virtualization and feature rights, but most Raff Windows VM buyers should first answer:

1. Is Raff supplying the Windows Server licence under SPLA?
2. Or is the customer using eligible BYOL rights?
3. Does the workload need RDS?
4. Are Windows Server CALs required under the customer's licensing model?
5. Is another Microsoft product such as SQL Server or Microsoft 365 Apps involved?

For the edition feature comparison, see Windows Server Standard vs Datacenter.

SQL Server licensing follows different rules

Do not copy Windows Server licensing rules directly to SQL Server.

SQL Server is a separate Microsoft product with its own licensing models. Depending on the scenario, SQL Server can involve Per Core licensing, Server + CAL licensing, License Mobility through Software Assurance, Flexible Virtualization Benefit, or provider-supplied licensing where available.

Use SQL Server 2025 Licensing Guide for the database layer.

Microsoft 365 Apps requires Shared Computer Activation in multi-user environments

If several users sign in to the same Windows Server and use Microsoft 365 Apps, each user needs a qualifying Microsoft 365 licence and the deployment must use Shared Computer Activation (SCA) where Microsoft requires it.

Microsoft currently lists Microsoft 365 Business Premium as the business plan that supports SCA, while plans containing Microsoft 365 Apps for enterprise also support SCA. Microsoft 365 Business Standard does not include SCA rights.

For setup and licensing details, see Shared Computer Activation for Microsoft 365 Apps on RDS.

Azure Hybrid Benefit is specific to Azure

Azure Hybrid Benefit is a Microsoft Azure benefit. It should not be used as a generic explanation for bringing Windows Server licences to any cloud provider.

Outside Azure, evaluate Microsoft's applicable outsourcing rights, Flexible Virtualization Benefit, or the provider's service-provider licensing model.

OEM licences are not a normal cloud BYOL path

An OEM Windows Server licence supplied with physical hardware is normally tied to that hardware licensing context. Do not assume an OEM licence from an old office server can simply be moved to a Raff VM.

For BYOL, focus on Microsoft's qualifying commercial subscription or active Software Assurance rights and the exact outsourcing entitlement.

Which Windows Server licensing model fits your deployment?

For smaller hosted Windows deployments, provider-supplied SPLA removes the need to prove customer BYOL entitlement. BYOL is relevant when an organization already has qualifying Microsoft commercial licensing and its deployment meets the applicable outsourcing terms.

Raff supports 3,000+ customers, 15,000+ VMs, and a 99.9% SLA. Licensing should still be validated for the customer's exact Microsoft agreement before production deployment.

What's next

• Raff Windows VM
• Windows VPS Pricing
• RDS CAL Licensing Guide
• Windows Server CALs: User vs Device
• Multi-User RDP vs RDS Session Host
• SQL Server 2025 Licensing Guide

Sources

• Microsoft Licensing — Windows Server 2025 Licensing Guidance
• Microsoft Licensing — Windows Server licensing
• Microsoft Licensing — Flexible Virtualization Benefit
• Microsoft Licensing — SPLA Licensing Guidance
• Microsoft Learn — License Remote Desktop Services with CALs
• Microsoft Learn — Shared Computer Activation for Microsoft 365 Apps
• Sources revalidated: 2026-09-17

Microsoft licensing terms vary by agreement, program, product version, geography, and deployment model. Microsoft Product Terms and the customer's executed Microsoft agreement control if they conflict with this guide.