Skip to Content

MC1216260: Remote Desktop client for Windows end of support on March 27, 2026

Summary

  • Remote Desktop client for Windows will no longer be supported after March 27, 2026, including no further downloads or updates.
  • Users must transition to the Windows App to maintain access to Windows 365, Azure Virtual Desktop, and Microsoft Dev Box.
  • An in-app banner will notify users of the upcoming change approximately 60 days prior to end of support.
  • Resources, including a usage reporting API and a migration script, are available to assist in the transition to Windows App.
  • Remote Desktop Connection (MSTSC) will continue to be supported and is not affected by this change.

Admin Impact: High
User Impact: High
Release Start: 27 Mar 2026
Release End: 27 Mar 2026
Services: Windows
Category: Plan for change
Tags: User Adoption, Admin Action, Retirement

History

1/9/2026 Item Added to Message Center

Microsoft Message

Introduction

Remote Desktop client for Windows will reach end of support on March 27, 2026. It is a standalone installer for the purpose of connecting to Windows 365, Azure Virtual Desktop, and Microsoft Dev Box. Remote Desktop client will continue to receive all security updates until end of support on March 27, 2026.

When this will happen

End of support date: March 27, 2026.

How this affects your organization

Who is affected: Organizations using the Remote Desktop client for Windows to connect to Windows 365, Azure Virtual Desktop, or Microsoft Dev Box.

What will happen:

  • After March 27, 2026, the Remote Desktop client for Windows will no longer be available for download and will not receive security or feature updates.
  • Security updates will continue until March 27, 2026.
  • Users will need to migrate to Windows App to maintain access to Windows 365 Cloud PCs.

Approximately 60 days before end of support, users will see an in-app banner notifying them of the upcoming change. This banner is designed to raise awareness and help organizations prepare for timely migration. Admins can disable this banner by configuring the following registry key:

Path:HKEY_LOCAL_MACHINE\Software\Microsoft\MSRDC
Key: SuppressEndOfServiceBannerMessage
Type: DWORD
Value: 1

Two new resources are available to support migration:

  • Windows 365 Remote Desktop Usage Reporting API: This API enables you to programmatically report on Remote Desktop client usage to identify users who still rely on the legacy client.
  • Remote Desktop Client Migration Script for Windows App: A supported migration script is available to help organizations move users from the Remote Desktop client to Windows App at scale.

We’re working to ensure Windows App reaches feature parity with the Remote Desktop client for Windows to ease this migration. Windows App also provides:

  • Unified access to Windows 365, Azure Virtual Desktop, and Microsoft Dev Box.
  • Customizable home screens, multimonitor support, and dynamic display resolutions.
  • Enhanced remote work experiences with device redirection, Microsoft Teams optimizations, and easy account switching.

What you can do to prepare

  • To avoid disruptions to users’ access to their remote resources, inform them of the change and migrate them to Windows App as soon as possible before March 27, 2026.
  • You may also use the Remote Desktop Usage Reporting API to identify users still on the legacy client and the migration script to transition those users to Windows App more efficiently.
  • Update internal documentation and helpdesk guidance as needed.

Note: Remote Desktop Connection, also known as Microsoft Terminal Services Client (MSTSC), has no plans for retirement or removal. Remote Desktop Connection is used to make RDP connections to another computer and is out of scope for this notification.

Additional resources:

  • Windows App Documentation
  • Accessing Cloud PCs
  • Windows 365 resources for IT pros
  • cloudPcReport: retrieveCloudPcClientAppUsageReport