Transitioning from Remote Desktop to the Windows App
The countdown has begun for users of Microsoft’s Remote Desktop application, as support will officially cease on May 27. This pivotal date marks the transition to the company’s newly introduced Windows App, a shift that carries both potential benefits and challenges for its user base.
Launched in 2024, the Windows App received a mixed response upon its debut. Microsoft described it as “your secure gateway to connect to Windows across Windows 365, Azure Virtual Desktop, Remote Desktop, Remote Desktop Services, Microsoft Dev Box, and more.” Essentially, it is a reimagined version of the Remote Desktop app, offering “unified access to multiple Windows services, including Cloud PCs and virtual desktops from a single, streamlined interface.”
Despite the promise of a fresh start, reactions have been varied. One user notably criticized the initiative, labeling it “the dumbest rebranding ever.” Such sentiments highlight the skepticism surrounding the transition, as many users grapple with the implications of this change.
As the deadline approaches, the Remote Desktop app will be removed from the Microsoft Store, compelling users to adapt to the Windows App for accessing essential services like Windows 365, Azure Virtual Desktop, and Microsoft Dev Box. There is speculation that future iterations may incorporate the term “Copilot,” hinting at further branding evolutions.
It is crucial to distinguish the Remote Desktop app from the long-established Remote Desktop Connection application, which has been a staple in Windows for decades. Microsoft clarifies that the connection types utilized by Remote Desktop Connection and Remote Desktop Services are not yet compatible with the Windows App.
To utilize the Windows App, users must possess either a school or work account. The app does offer several enhancements, including:
- Customizable home screens
- Support for multi-monitor setups
- Dynamic resolution scaling
- Device redirection
- Optimization for Microsoft Teams
However, it is important to note that certain features are still lacking. For instance, Private Link for connecting to Azure Virtual Desktop is not supported, nor is local Start Menu integration. Additionally, Microsoft has warned that the Windows App may not function in environments where proxy servers require proxy/HTTP authentication, and single sign-on (SSO) with Active Directory Federation Services (AD FS) is also unsupported.
As the May 27 deadline looms, customers currently using the Remote Desktop app must prepare for migration. After this date, connections to Windows 365, Azure Virtual Desktop, and Microsoft Dev Box via the Remote Desktop app will be blocked, marking the end of an era and the beginning of a new chapter in Microsoft’s remote access offerings.
