Published 2026-01-27 by TechNet Team
Microsoft has announced the end of support for its Remote Desktop client applications, pushing users toward the new Windows App. If your organization uses Azure Virtual Desktop, Windows 365, or Microsoft Dev Box, this affects you directly.
Key Dates to Know
- May 27, 2025: Remote Desktop app (Microsoft Store version) reaches end of support and will no longer be available for download
- September 30, 2025: Connections to Windows 365, Azure Virtual Desktop, and Microsoft Dev Box will be blocked when using the old Remote Desktop app
- March 27, 2026: Remote Desktop client (standalone MSI installer) reaches end of support and will no longer be available
What's NOT Affected
Here's the important distinction many people miss: mstsc.exe is not going away. The classic Remote Desktop Connection utility built into Windows (the one you launch by typing "mstsc" in the Run dialog) remains fully supported and will continue working.
However, mstsc.exe doesn't integrate with cloud services like Azure Virtual Desktop, Windows 365, or Dev Box. If you're only using RDP to connect directly to servers or PCs on your network, you can continue using mstsc.exe without any changes.
What Is Windows App?
Windows App is Microsoft's new unified remote desktop client. It's designed to provide a consistent experience across platforms:
- Available on Windows, macOS, iOS, and web browsers
- Android support coming soon
- Connects to Windows 365, Azure Virtual Desktop, and Microsoft Dev Box
- Features customizable home screens, multi-monitor support, and dynamic display resolutions
Current Limitations
Windows App is still maturing. As of early 2025, known limitations include:
- Requires a work or school account (Microsoft Entra ID)
- Does not support traditional RDP connections to servers/PCs (use mstsc.exe for that)
- No Azure Government Cloud connectivity yet
- Limited proxy server and HTTP authentication support
- Azure Private Link support is on the roadmap but not yet available
- Remote apps can't be launched directly from the Windows Start menu
Who Needs to Take Action?
You need to plan for migration if your organization uses:
- Azure Virtual Desktop (AVD): Your users connecting to virtual desktops and apps
- Windows 365 Cloud PCs: Users accessing their Cloud PCs through the Remote Desktop client
- Microsoft Dev Box: Developers using Dev Box environments
If you're only using traditional RDP to connect directly to on-premises servers or workstations, mstsc.exe continues to work and you don't need to do anything immediate.
How to Prepare
- Inventory your usage: Identify who in your organization uses Remote Desktop client for cloud services vs. traditional RDP
- Download Windows App: Available from the Microsoft Store or apps.microsoft.com
- Test before the deadline: Have users test Windows App with their workflows before the September 2025 block date
- Update documentation: Revise any internal guides that reference the old Remote Desktop app
- Plan training: The interface is different enough that users may need guidance
The Bottom Line
This transition is primarily about Microsoft's cloud services consolidation. For organizations heavily invested in Azure Virtual Desktop or Windows 365, the move to Windows App brings a more modern, unified experience. For those using traditional RDP to on-premises resources, the classic mstsc.exe isn't going anywhere.
Don't wait until the deadline to migrate. Start testing Windows App now so you're not scrambling when the old client stops working in September 2025.
Need help planning your migration? Contact TechNet New England for assistance with your Azure Virtual Desktop or Windows 365 environment.