At a Glance
RDS (Remote Desktop Services) licensing in 2026 keeps its familiar model of Windows Server licences and RDS CALs (Client Access Licences), but brings tighter version compatibility requirements and notable changes to how SPLA can be used in public cloud environments.
Organisations must reassess their hosting models, CAL strategy, and compliance processes to avoid disruption, manage costs, and remain aligned with Microsoft’s updated licensing framework. Uncomplicate RDS with BlackBox Hosting’s managed RDS.
Contact us today to find out more.
RDS Licensing in 2026
Remote desktops are powered by RDS (Remote Desktop Services), a suite of services that allow users to access applications and desktops remotely from anywhere. This widely used technology is part of Microsoft Windows, and its cost is included in the price of Windows Server licenses.
However, things become more complex with RDS licensing in 2026 as Microsoft introduces changes. These changes deal with continuity and how organisations need to approach compliance, especially with newer Windows Server versions and public clouds.
In this guide, we explain how RDS licensing works, what’s changed and what remains unchanged as of 2026, how to optimise the costs of licensing, and when to seek help from RDS experts like BlackBox Hosting.
How Does the Microsoft RDS Licensing Model Work?
Microsoft RDS licensing is important because it supports the setup and maintenance of your RDS environment.
The core components of Microsoft RDS licensing include:
- Windows Server Licenses
- Client Access Licenses (CALs)
- Remote Desktop Licensing Server
Windows Server Licenses
A Windows Server licence is the foundation of your RDS setup. Each of your Windows servers with the RDS role must have a license. From Windows Server 2016 to Windows Server 2025, the operating system is licensed either on a per-core or on a Server + CAL basis, depending on the edition.
Client Access Licenses (CALs)
You need RDS Client Access Licenses (CALs) to enable remote access sessions to a server.
Windows Server CALs
Required for every user or device accessing the Windows Server OS, for tasks such as file sharing or remote sessions.
RDS CALs
Required in addition to Windows Server CALs. Every user or device accessing RDS must have an RDS CAL issued and tracked by the Remote Desktop Licensing server.
Further, there are two types of RDS CALs
- Per User CALs: Ideal for individual users connecting from multiple devices.
- Per Device CALs: Ideal for multiple users sharing specific workstations.
So when a user or device connects to an RDS host, the session host checks with the licensing server to issue an RDS CAL.
Remote Desktop Licensing Server
Installing and distributing RDS CALs requires a dedicated license server role. Until server activation and CAL installation, Remote Desktop Services operates during a 120-day grace period. After this, it will need to be licensed, otherwise, licensed connections are blocked.
What’s Changed in RDS Licensing in 2026
The fundamental RDS licensing model remains the same in 2026, but it brings key changes.
Cloud Hosting and SPLA Restrictions
In late 2025, Microsoft updated the licensing rules, impacting how RDS is licensed in public clouds. Earlier providers could use SPLA (Service Provider License Agreement) licenses for Windows Server and RDS in hosted environments. But from October 2025, SPLA licenses are no longer compliant for use on public cloud platforms.
Instead, businesses need to use either licence-included services or images with the Windows Server/RDS rights or their own licences in dedicated hosts with appropriate volume licensing rights.
This has changed the way managed service providers and hosted RDS deployments plan costs and compliance.
Version Compatibility for CALs
The 2026 changes to RDS licensing introduce more rigid version compatibility rules for RDS CALs. Older CALs can’t access newer Windows versions, and the newer RDS CALs, like the Windows Server 2025 RDS CALs, are backwards compatible with older session hosts.
This means organisations planning to adopt Windows Server 2025 for RDS need to carefully plan CAL upgrades to remain compliant across mixed environments.
Licensing Management & Reporting Tools
Moving away from older licensing consoles, Microsoft has been migrating licensing configuration and reporting functions towards admin portals. Though functional capabilities remain the same, teams may find themselves overreliant on licensing, reporting, and key activation of cloud-linked portals.
What Has Stayed the Same
Although RDS licensing in 2026 introduces key changes, some core elements remain unchanged.
RDS CALs Still Required in Azure
If you run Windows Server with RDS in Azure, you’ll still need CALs for users and devices accessing server functions. Even though Azure includes the base Windows Server license, you still require RDS CAL.
RDS Licensing Mode Must Be Configured
You still need to define the licensing mode per user or per device on the session host for each CAL type on the licensing server. Not doing so may result in access issues or compliance warnings.
Grace Period Still Applies
Post adding the RDS role, servers still offer a 120-day grace period while you configure licensing. Once the period expires, your connections will be denied till CALs are installed.
Optimising RDS Licensing Costs
Given the changes in RDS licensing in 2026, here are some strategies to license RDS effectively:
- Choose the right CAL model: Per-user CALs work best for remote workers who access multiple devices, whereas per-device CALs are ideal for shift-based or shared-terminal environments.
- Avoid over-licensing: Many organisations make the mistake of purchasing excess CALs, failing to claim unused licences, and overprovisioning cores. These errors can escalate your RDS licensing budget.
- Reevaluate your hosting location: With the SPLA restrictions in public cloud RDS environments, your business may want to consider moving to compliant hosting providers to maintain RDS flexibility and control.
If your organisation depends on the SPLA-public cloud model today, you’ll need to transition to a supported alternative.
How BlackBox Hosting Supports Businesses Amid RDS Licensing Changes
BlackBox Hosting is a UK-based hosting provider specialising in private and managed hosting services. We are the UK’s largest RDS service provider with over 10,000 daily RDP users.
If your business is already a part of the Microsoft ecosystem, here’s how we keep your Microsoft 365 data secure.
We help businesses manage the changes brought by RDS licensing with the following:
- Compliant hosted RDS environments: If your business is affected by the public cloud SPLA restrictions, we provide compliant hosting environments to support RDS deployment without licensing complexity.
- Migration upgrade & support: If you’re upgrading to Windows Server 2025 or changing your infrastructure, we can support you in planning for version compatibility, CAL transition, and secure migration.
- Ongoing licence management: You get continuous monitoring and usage-based optimisation to manage risks and control costs.
Partner with us to ensure your RDS environment remains secure, compliant, and efficient. Call +44 02037 407840 to talk to our team today.
