Prepare for End of Support: Remote Desktop Client for Windows (March 27, 2026)

On 27 March 2026, Microsoft will retire the Remote Desktop client for Windows (MSRDC). Organisations relying on this client to access Azure Virtual Desktop (AVD) must migrate to the new Windows App to maintain service continuity and avoid functionality loss.

🧭 What’s Changing?

The Remote Desktop client for Windows, available at
🔗 aka.ms/RemoteDesktopClient, will:

• No longer be available for download
• No longer receive security patches or feature updates
• Lose official Microsoft support

🚫 Microsoft will not update or support MSRDC after 27 March 2026.

✅ What Should You Do?

Microsoft recommends migrating all users to the Windows App as the future-supported client for AVD, Windows 365, and Microsoft Dev Box.

🔗 Download Windows App

The Windows App provides:

• 🌐 Unified access across AVD, Windows 365, Microsoft Dev Box
• 🖥️ Multi-monitor and dynamic display resolution support
• ⚙️ Customisable layout options, Teams optimisations, and device redirection
• 🔒 Continuous feature and security updates from Microsoft

🔍 Known Limitations in the Windows App

While Microsoft is working towards full feature parity, the Windows App still has known limitations compared to the legacy Remote Desktop client.

🔗 View official Microsoft limitations

Some limitations as of 2025 include:

• Smart card redirection in certain use cases
• Specific FSLogix integration gaps
• Drive redirection restrictions
• Incomplete support for unsigned plugins and legacy apps

✅ FABS Tip: Always test your redirection, session policies, and third-party integrations in a controlled pilot before large-scale rollout.

🔐 What’s Not Changing?

The classic Remote Desktop Connection (mstsc.exe) is unaffected and will remain available and supported.

🛠️ How to Migrate to Windows App — 4 Key Steps

1. Assess
   Use Azure Virtual Desktop Insights to identify users still connecting via the legacy Remote Desktop client.
2. Plan
   Audit your redirection policies, session configs, and integrations. Identify critical apps requiring testing in the new Windows App.
3. Deploy
   Roll out the Windows App via Intune, GPO, or your endpoint management solution of choice.
4. Support
   Provide end-user training and monitor connection telemetry to catch issues early.

🔗 Useful Resources

• Official Microsoft Retirement Announcement
• Download Windows App
• Known Limitations in Windows App
• Azure Virtual Desktop Insights