Editorial photograph of an enterprise data center hosting Windows session host workloads
Article · Microsoft · RDS

Azure RDS licensing. Decoded for 2026.

Remote Desktop Services on Azure has three licensing routes. RDS CALs with Software Assurance for session hosts, Azure Virtual Desktop per user, and BYOL into Azure. The metric, the math, the mobility rules, and the framework procurement teams use to control RDS cost in 2026.

Read the Framework Microsoft Hub
3 routesRDS, AVD, BYOL
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Microsoft offers three primary routes to license Remote Desktop Services on Azure. Each route carries different metrics, different costs, and different mobility rules. The right route depends on user count, session pattern, existing license assets, and the strategic direction.

The wrong route is expensive. A small mistake on the metric drives a 30 to 60 percent overrun on the RDS spend across a three year term.

This article gives the buyer side framework. Pair it with the Microsoft hub, the Azure cost optimization guide, the EA renewal playbook, and the M365 license optimizer.

Key Takeaways

What a CIO needs to know in 90 seconds

  • Three routes. RDS CALs with SA, Azure Virtual Desktop per user, BYOL into Azure under mobility.
  • RDS CALs land cheaper at scale. The per device or per user CAL with SA covers the session host RDS rights.
  • AVD per user runs roughly 132 dollars per user per year. The flat rate covers the AVD rights inside the M365 stack.
  • M365 E3 and E5 include AVD per user. The bundle gives the AVD rights at no incremental cost on the AVD line.
  • BYOL into Azure requires License Mobility. The on prem RDS CALs with active SA can be deployed in Azure under the listed Authorized Outsourcer rules.
  • Multi tenant hosting is a separate license. RDS SAL via SPLA is the route for hosting third party users.
  • Per user is one way. The shift from per device to per user is permitted at SA renewal only.

RDS CALs and Software Assurance

The classic Microsoft route is RDS CALs purchased per device or per user, with Software Assurance for upgrade rights and version mobility. The CAL covers the right to access RDS session hosts.

Per device versus per user

DimensionRDS Device CALRDS User CAL
Counting unitEach accessing deviceEach accessing user
Best forShared kiosks, manufacturing floor, contact centersMobile workforce, BYOD, multi device users
List per CALRoughly 102 dollars perpetual plus 25 dollars per year SARoughly 152 dollars perpetual plus 38 dollars per year SA
Mobility into AzureAllowed with SA, License MobilityAllowed with SA, License Mobility
Switching directionPer device to per user at SA renewalPer user to per device at SA renewal
External user useExternal Connector requiredExternal Connector required

The SA renewal switch

The choice between per device and per user is reversible at SA renewal only. The wrong choice locks the customer into the wrong metric for the SA term. The buyer side audit identifies the right metric before the SA anchor.

Azure Virtual Desktop per user

Azure Virtual Desktop replaced the prior Windows Virtual Desktop branding. AVD provides multi session Windows 10 and 11 inside Azure with full virtualization rights and session host management.

Rights included

  • Multi session Windows 10 and 11 Enterprise. Available only on AVD on Azure.
  • FSLogix profile container. Persistent user profiles across non persistent session hosts.
  • Image management. Azure Compute Gallery and Shared Image Gallery integration.
  • Session host management plane. Host pool, application group, workspace constructs.
  • RDP Shortpath. Direct connectivity option for low latency sessions.

AVD per user list

AVD per user external runs roughly 11 dollars per user per month. The license covers AVD access rights for users not licensed via M365 E3 or E5.

BYOL into Azure under license mobility

License Mobility through Software Assurance permits the deployment of certain on prem licenses on a third party authorized outsourcer including Azure. The route applies to RDS CALs and to certain Microsoft server products.

License Mobility rules

  1. Active Software Assurance required. The mobility right exists only while SA is active.
  2. Authorized Outsourcer only. Azure and other listed cloud providers qualify.
  3. Verification required. Microsoft requires a verification form on first BYOL deployment.
  4. Reassignment after 90 days. The license cannot be reassigned more than once every 90 days.
  5. Listed Server applies. SQL Server, BizTalk, SharePoint, and several others sit on the Listed Server schedule.

Windows Server is not License Mobility

Windows Server itself is not on the License Mobility list. Windows Server in Azure is Azure Hybrid Benefit. The two programs solve different problems and follow different rules. Mixing them is the most common BYOL mistake.

Cost comparison worked

The three routes price out differently on the same workload. The example below assumes 1,000 users on persistent RDS session hosts inside Azure.

Three year cost on 1,000 users

RouteLicense unitThree year cost band
RDS User CAL plus SA1,000 RDS User CALs plus SA240,000 to 300,000
AVD per user external1,000 users at 132 per year396,000
AVD via M365 E3If E3 already ownedIncluded in E3
BYOL existing CALs into AzureExisting CALs with active SASA only, roughly 75,000 to 114,000

The decision logic

If the customer already owns RDS CALs with SA, BYOL into Azure is the cheapest route. RDS User CALs plus SA is the cheapest fresh license path on a three year horizon.

AVD per user external is the right path only when the workload is consumed by users not already licensed via M365 E3 or E5.

Mobility rules and the gotchas

The mobility rules are restrictive. Three areas trip up most procurement teams.

The three traps

  • Multi tenant hosting on RDS CALs. Not permitted. Multi tenant hosting requires SPLA via RDS SAL.
  • Per device CAL with cloud session. Per device counts the connecting device. Cloud RDP from any device requires per user.
  • Lapsed SA in mid term. Mobility rights end the day SA lapses. The license reverts to on prem use only.

What to do next

The seven step checklist below runs the buyer side process. The work fits inside a 90 day window before the next M365 or EA renewal anchor.

  1. Inventory the RDS estate. Identify session hosts, user counts, persistent versus non persistent, AVD versus on prem.
  2. Map users to license source. M365 E3 or E5, RDS CAL with SA, external AVD per user, contractor.
  3. Identify mobility candidates. RDS CALs with active SA can move into Azure under License Mobility.
  4. Identify reclassification candidates. Per device users on cloud RDP need per user.
  5. Model the three routes. RDS CAL plus SA, AVD per user, BYOL into Azure.
  6. Negotiate at the SA anchor. Switch direction is permitted only at SA renewal.
  7. Document the position. The mobility verification form and the License Mobility statement filed.

Frequently asked questions

Does AVD require a separate license if we have M365 E3?

No. M365 E3 and E5 include AVD user rights. The user can access AVD without an additional per user AVD license. Only AVD compute, storage, and networking on Azure are billed separately. The per user external AVD license applies only to users not on M365 E3 or E5.

Can we use RDS CALs in Azure?

Yes via License Mobility through Software Assurance. The RDS CALs must have active SA. Azure is an Authorized Outsourcer. The verification form is required on first BYOL deployment. The license cannot be reassigned more than once every 90 days.

What is the difference between per device and per user RDS CALs?

Per device counts the accessing device and is best for shared workstations and kiosks. Per user counts the accessing user and is best for mobile and BYOD workforces. The choice is reversible only at SA renewal. Cloud RDP from any device requires per user.

Is Windows Server in Azure covered by License Mobility?

No. Windows Server in Azure runs under Azure Hybrid Benefit. License Mobility does not apply to Windows Server. Azure Hybrid Benefit allows on prem Windows Server licenses with active SA to be used on Azure VMs at the discounted Linux base rate.

Can we host third party users on RDS CALs?

No. Multi tenant hosting of third party users requires SPLA via RDS SAL. The retail RDS CALs are for users of the customer organization only. The RDS External Connector is an alternative for known external users on a single CALs population.

What is the cheapest RDS route on Azure for 1,000 users?

BYOL existing RDS CALs with active SA into Azure is the cheapest route if the licenses already exist. RDS User CALs plus SA is the cheapest fresh license route. AVD per user external is the right path only when the users are not licensed via M365 E3 or E5.

How Redress engages on Microsoft RDS and AVD

Redress runs the RDS estate review, the License Mobility verification, and the route selection on the buyer side. The deliverable is a defended RDS position, a defended AVD position, and a defended Azure Hybrid Benefit posture across the SA term.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Right size the M365 stack including AVD entitlements in under five minutes.
Open the Microsoft 365 License Optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

A buyer side framework for the next Microsoft EA or MCA E renewal. Includes the AVD versus RDS decision matrix, the License Mobility checklist, the BYOL verification map, and the discount benchmark used on every Microsoft engagement.

Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for enterprise customers running Microsoft at scale against the published commercial models.

Microsoft EA Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
3 routes
RDS, AVD, BYOL
132 per user
AVD external annual
90 days
Mobility reassignment rule
500+
Enterprise clients
100%
Buyer side

We mapped the 1,200 user RDS estate, found 380 persistent CALs eligible for License Mobility into Azure, switched 220 contractors to AVD per user external, and used the rebuilt position to land the EA renewal at 23 percent below the original Microsoft ask on the RDS line.

Director Workplace Services
North American manufacturing group
More Reading

More from this practice.

Microsoft Hub →
Microsoft Azure Cost Optimization 2026
Microsoft · Pillar
Microsoft Azure Cost Optimization 2026
The Azure cost playbook for 2026.
26 min read
Microsoft 365 E3 vs E5 Comparison
Microsoft · Article
Microsoft 365 E3 vs E5 Comparison
The E3 to E5 lift decision tree.
20 min read
Microsoft EA Renewal Playbook
Microsoft · Landing
Microsoft EA Renewal Playbook
The complete EA renewal playbook.
20 min read
Microsoft 365 License Optimizer
Microsoft · Tool
Microsoft 365 License Optimizer
Right size the M365 stack.
12 min read
Microsoft Vendor Management Toolkit
Microsoft · Article
Microsoft Vendor Management Toolkit
End to end Microsoft vendor management.
18 min read
Editorial photograph of enterprise contract negotiation strategy

Your Microsoft RDS envelope is your envelope.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Microsoft licensing intelligence, monthly.

RDS CAL pricing movements, AVD per user shifts, License Mobility updates, and Microsoft commercial behavior across every renewal cycle.