Azure Virtual Desktop and Remote Desktop Services both deliver Windows desktops and applications to users who are not sitting at the machine. The difference is who runs the plumbing.
Remote Desktop Services is a Windows Server role set you install, patch, secure, and scale yourself. Azure Virtual Desktop is a Microsoft-managed connection service that removes the gateway and broker from your plate but leaves the desktops themselves your responsibility.
Most organizations reading this already run RDS. The question is usually not “which should we pick” but “do we have to move, and when.” This year, for a lot of Windows Server 2016 and 2019 shops, the answer is yes and soon.
The short answer
Choose Azure Virtual Desktop if you want Microsoft to run the connection infrastructure, you need Windows 11 Enterprise multi-session, you are already licensed through Microsoft 365 E3 or E5, or your Windows Server version is running out of road.
Stay on Remote Desktop Services if your workloads depend on local hardware, your internet connectivity cannot support a cloud-hosted session, you have recently invested in Windows Server 2022 or 2025 infrastructure, or regulation keeps the data on premises.
Look at Windows 365 instead of both if you want a fixed per-user monthly cost and a dedicated desktop per person, and you do not want to manage Azure consumption at all.
What Azure Virtual Desktop is
Azure Virtual Desktop is Microsoft’s desktop and app virtualization service running on Azure. It was called Windows Virtual Desktop until Microsoft renamed it in 2021, and Microsoft’s own documentation still carries the “formerly Windows Virtual Desktop” note.
It delivers full desktops or individual published apps from session hosts running in Azure. Supported session host operating systems are Windows 11 Enterprise, Windows 11 Enterprise multi-session, Windows 10 Enterprise, Windows 10 Enterprise multi-session, and Windows Server 2016 through 2025.
The capability people actually move for is multi-session Windows 11. It lets several users share one virtual machine while each gets a full client Windows desktop. That combination exists only inside the Azure Virtual Desktop service and Windows 365.
What Microsoft runs: the web service, the connection broker, the gateway, the resource directory, and the connection database.
What you run: the session host virtual machines, the OS image, the applications on it, the virtual network, identity, and the backup and recovery of those session hosts.
That split matters more than any feature comparison, and it is the thing most comparison articles get wrong.
What Remote Desktop Services is
Remote Desktop Services is the Windows Server role set that has delivered session-based desktops since Terminal Services. It is still fully supported in Windows Server 2025.
It is built from five roles, and you deploy and maintain all of them:
- RD Session Host holds the shared desktops and apps. It is multi-session by design.
- RD Connection Broker routes incoming connections, balances load, and reconnects dropped sessions.
- RD Gateway lets users on public networks reach internal desktops over SSL.
- RD Web Access publishes desktops and apps through a browser portal.
- RD Licensing issues the client access licenses that make the whole thing legal.
Nothing here is deprecated. RDS is a supported, current product. The argument for moving off it is rarely that it stopped working. It is that you are carrying five server roles Microsoft would otherwise carry for you.
Azure Virtual Desktop vs. Remote Desktop Services at a glance
| Azure Virtual Desktop | Remote Desktop Services | |
|---|---|---|
| Where it runs | Azure, or on Azure Local for hybrid | Your servers, or IaaS VMs you manage |
| Who runs the broker and gateway | Microsoft | You |
| Who runs the desktops | You | You |
| Session host OS | Windows 11 and 10 Enterprise, single or multi-session, plus Windows Server 2016 to 2025 | Windows Server only |
| Multi-session client Windows | Yes | No |
| Licensing | Microsoft 365 E3/E5/A3/A5/F3/Business Premium/Student Use Benefit, Windows Enterprise E3/E5, Windows Education A3/A5, or Windows VDA per user. Windows Server session hosts need RDS CALs with Software Assurance or RDS User Subscription Licenses. | RDS CALs, per user or per device, plus Windows Server licensing |
| Cost model | Azure consumption for compute, storage, and networking. No separate service fee when the user carries a qualifying internal-use license. Streaming apps to users outside your organization is priced separately. | Capital or hosting cost for the servers, plus CALs, plus your own labor |
| Inbound firewall ports | None required for the connection service | RD Gateway needs inbound TCP 443 and UDP 3391 |
| Scaling | Autoscale by schedule or demand, breadth and depth load balancing | Farm sizing and load balancing you configure |
| Client app | Windows App, on every platform | Windows App on macOS, iOS, iPadOS, and Android. On Windows, the Remote Desktop Connection client. |
Licensing entitlements and supported operating systems are taken from Microsoft’s Azure Virtual Desktop prerequisites documentation. Role descriptions are from Microsoft’s Remote Desktop Services documentation.
The 2026 dates that force this decision
This is the part that is missing from most comparisons, and it is usually the reason a migration gets funded.
| What | Date | Status |
|---|---|---|
| Windows 10 end of support | October 14, 2025 | Passed |
| Microsoft 365 Apps support on Windows Server 2016 and 2019 | October 14, 2025 | Passed. Security updates only, until October 10, 2028. |
| Remote Desktop client for Windows and the Remote Desktop web client, public cloud | March 27, 2026 | Passed. Windows App is the replacement. |
| Same clients on Azure Government, Azure operated by 21Vianet, and AVD Classic | September 28, 2026 | Imminent |
| Windows Server 2022 mainstream support ends | October 14, 2026 | Weeks away |
| Windows Server 2016 extended support ends | January 13, 2027 | |
| Windows Server 2019 extended support ends | January 10, 2029 | |
| Windows Server 2025 mainstream support ends | November 14, 2029 |
Two of these change the math immediately.
If your RDS session hosts run Windows Server 2016 or 2019 and your users open Office on them, Microsoft 365 Apps is already past support on that platform. It keeps receiving security updates until October 10, 2028, but it stopped receiving features. Microsoft’s own guidance for this situation names Windows 365 and Azure Virtual Desktop as the recommended destinations.
If your users still connect through the old Remote Desktop client, that client and the Remote Desktop web client reached end of support on March 27, 2026 in the public cloud. Azure Government, Azure operated by 21Vianet, and AVD Classic have until September 28, 2026. Windows App replaced them and connects to Azure Virtual Desktop, Windows 365, Microsoft Dev Box, remote PCs, and, depending on the platform you are connecting from, Remote Desktop Services. Moving to Windows App is worth doing whether or not you move off RDS.
One more that runs in Azure Virtual Desktop’s favor. Windows 10 session hosts inside Azure Virtual Desktop, single or multi-session, are eligible for Extended Security Updates at no additional license cost and with no activation key to buy. The same VM in your own datacenter is not. One caveat that matters operationally: eligibility is not the same as delivery. Your administrator still has to turn on the ESU policy, through Microsoft Intune or a registry configuration, before those hosts start receiving the updates. Confirm that step has been done rather than assuming the entitlement covers it.
How the costs actually differ
Neither model is reliably cheaper. They fail in different directions.
Remote Desktop Services costs are mostly fixed and mostly up front. Server hardware or reserved IaaS capacity, Windows Server licensing, RDS CALs, and the engineering time to maintain five roles. You pay for peak capacity whether or not anyone is logged in, and an under-used farm is money sitting idle.
Azure Virtual Desktop costs are mostly variable. You pay Azure rates for the compute, storage, and networking your session hosts consume. There is no separate service fee for the platform itself when the user carries a qualifying license. Autoscale can shut hosts down outside business hours, which is where the savings usually come from, and multi-session lets you fit more users onto fewer machines.
The failure mode is a lift-and-shift: moving an RDS farm into Azure at the same always-on sizing, with no autoscale and no multi-session consolidation. That costs more than the servers it replaced, every time.
Model your own numbers against the Azure Virtual Desktop pricing page rather than any third-party estimate, including this one. Compute rates vary by region and VM family.
Where Windows 365 fits
Windows 365 belongs in this comparison because it is frequently the right answer and it is usually left out.
Windows 365 provisions a Cloud PC per user, managed through Microsoft Intune, billed at a fixed per-user per-month rate. Underneath, it uses Azure Virtual Desktop for the remote connection. It is Azure Virtual Desktop with the Azure management removed and the cost made predictable.
- Windows 365 suits organizations that want a dedicated desktop per person, a predictable line item, and no Azure administration.
- Azure Virtual Desktop suits organizations that want multi-session density, custom images, and the ability to tune cost against consumption. We cover these in more detail in five advantages of Azure Virtual Desktop.
- Remote Desktop Services suits organizations that need the workload to stay where it is.
Many environments end up running two of the three. A dedicated Cloud PC for the finance team and a pooled multi-session host pool for the call center is a normal outcome, not a compromise.
When Remote Desktop Services is still the right answer
RDS is not a legacy platform to be apologized for. It is the better choice when:
- A line-of-business application depends on local hardware or a local device. Scanners, scales, badge printers, and licensing dongles do not always travel to the cloud gracefully.
- Site connectivity cannot carry the sessions. A remote office on a thin or unreliable link will have a worse day on a cloud-hosted desktop than on a server in the closet.
- The data has to stay put. Some contractual and regulatory positions are simpler to defend on premises.
- You just bought the infrastructure. If your Server 2022 or 2025 farm is two years old, the depreciation argument beats the architecture argument.
- Latency to the application tier matters more than latency to the user. If the database is on premises, putting the desktop in Azure moves the session close to the user and far from the data.
Where a mixed estate is the outcome, co-managed IT services let your internal team keep the workloads that have to stay put while someone else carries the rest.
Planning an RDS to Azure Virtual Desktop migration
If the dates above have made the decision for you, the sequence looks like this.
- Inventory the applications. Every app on the RDS farm, with its owner, its licensing model, and whether it needs a local device. This step decides the whole project and it is the one most often skipped.
- Profile actual usage. Concurrent sessions by hour, by day. This sizes the host pool and sets the autoscale schedule. Guessing here is what produces the lift-and-shift cost blowout.
- Confirm licensing. Check what your users already carry. Microsoft 365 E3 and E5 include the entitlement for Windows 11 and 10 Enterprise. Windows Server session hosts still need RDS CALs with Software Assurance or RDS User Subscription Licenses.
- Decide pooled or personal. Pooled multi-session for task workers. Personal desktops for users who install their own software or run persistent workloads.
- Build the image. Golden image with the applications, then the FSLogix profile container configuration so user profiles follow the session.
- Pilot with one department. A real one, with real work, for a real fortnight. Not IT testing IT.
- Cut over in waves, and keep the RDS farm running behind you until the last wave is stable.
- Turn on autoscale and then look at the bill. The savings are not automatic. They come from the schedule. Ongoing cloud managed services are what keep that schedule tuned after the project team leaves.
Budget for the image and the profile work. Those two items consume more of the project than the deployment itself.
Frequently asked questions
Is Windows Virtual Desktop the same as Azure Virtual Desktop?
Yes. Microsoft renamed Windows Virtual Desktop to Azure Virtual Desktop in 2021. It is the same service with a new name and several years of added capability, and Microsoft’s documentation still carries the former name for reference. If a vendor is still selling you “WVD,” their material is out of date.
Is Remote Desktop Services being discontinued?
No. Remote Desktop Services is a supported role set in Windows Server 2025 and Microsoft continues to document it. What ended is the old Remote Desktop client for Windows, on March 27, 2026 in the public cloud, replaced by Windows App. The server roles are unaffected.
Do I need RDS CALs for Azure Virtual Desktop?
Only for Windows Server session hosts. If your session hosts run Windows 11 or Windows 10 Enterprise, a qualifying license such as Microsoft 365 E3, E5, F3, or Business Premium covers the user. If they run Windows Server, you need RDS CALs with Software Assurance or RDS User Subscription Licenses on top. Windows Server session hosts are also not covered by the per-user access pricing Microsoft offers for streaming to users outside your organization.
Does Microsoft back up my Azure Virtual Desktop session hosts?
No. Microsoft manages the control plane, meaning the broker, the gateway, and the connection service. Backup, recovery, patching, and resilience of the session host virtual machines are your responsibility. This is the single most common misunderstanding about the service and it is worth confirming in writing with whoever runs your environment.
Can I run Microsoft 365 Apps on a Windows Server session host?
On Windows Server 2022 and 2025, yes. On Windows Server 2016 and 2019, support ended October 14, 2025. Those devices continue to receive security updates until October 10, 2028 but no new features. Microsoft’s guidance for organizations in that position is to move to Windows 365 or Azure Virtual Desktop.
Is Azure Virtual Desktop cheaper than Remote Desktop Services?
It can be, and it is not automatically. Azure Virtual Desktop converts a fixed infrastructure cost into a variable consumption cost. That saves money when you use autoscale and multi-session to shrink capacity outside business hours. Moving an always-on RDS farm into Azure at the same sizing typically costs more than the servers it replaced.
Still running RDS on Windows Server 2016 or 2019?
Microsoft 365 Apps is already past support on that platform, and Server 2016 extended support ends in January 2027. We can map your current farm, your application dependencies, and what a move would actually cost before you commit to one.
Schedule a Conversation | FL (954) 474-2204 | NY (516) 536-5006
