Windows App Migration Plan: Replacing Deprecated Remote Desktop Clients in Commercial Cloud

From March 27, 2026, Microsoft no longer supports two legacy remote access clients in commercial cloud environments:

• Remote Desktop client for Windows (MSI) — the traditional MSTSC-based installer
• Remote Desktop web client — browser-based RD Web Access

Microsoft's direction is the Windows App as the unified client for Azure Virtual Desktop, Windows 365 Cloud PC, and Remote Desktop Services in commercial cloud scenarios. The March 2026 Windows App update also adds keyboard input protection and reliability fixes.

This guide is an admin cutover plan: inventory who still uses legacy clients, deploy Windows App through Intune, validate session scenarios, and update helpdesk documentation before users hit a dead client.

See the Intune hub, Intune vs SCCM comparison, and Conditional Access policy map for related deployment context.

Who Needs To Act

If you only manage corporate laptops and nobody uses AVD, Windows 365, or RDS through the MSI client, impact may be limited. Still run inventory — shadow IT remote access is common.

Phase 1: Inventory Legacy Client Usage

What to find

PowerShell inventory example (local audit script)

$UninstallKeys = @(
    'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*',
    'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'
)

Get-ItemProperty $UninstallKeys -ErrorAction SilentlyContinue |
    Where-Object { $_.DisplayName -match 'Remote Desktop' } |
    Select-Object DisplayName, DisplayVersion, Publisher, InstallDate

Expected output shape: zero or more Remote Desktop MSI entries with version and install date.

User population segmentation

Build three groups:

1. AVD users — full desktop or RemoteApp via feed
2. Windows 365 users — Cloud PC connections
3. RDS gateway / RD Web users — web client or MSI to on-premises or cloud-hosted collections

Each group may need different feed URLs, MFA behaviour, and test cases.

Phase 2: Deploy Windows App Through Intune

Preferred distribution paths

In Intune:

1. Apps > Windows > Microsoft Store app (new)
2. Search for Windows App
3. Assign as Required to pilot group, then production remote-access groups
4. Confirm install status in Devices > Monitor > App install status

Coexistence during pilot

Do not remove the MSI client until Windows App is validated for each scenario. Run both briefly in pilot if policy allows, so users can fall back during testing.

Phase 3: Pilot Test Matrix

Test every scenario your users actually run — not just "can I connect."

Record build versions of Windows App tested and the session host image versions they connected to.

Phase 4: User And Helpdesk Cutover

Helpdesk script update

Replace references to:

• "Open Remote Desktop" MSI shortcut
• RD Web portal URL as primary path

With:

• Windows App from Start menu or pinned taskbar
• Your organisation's published feed URL or Windows 365 entry point

Communication template

What is changing: The old Remote Desktop (MSI) app and browser web client are no longer supported for connecting to <AVD / Windows 365 / RDS>.

What to do: Use Windows App on your managed device. It is installed automatically. Sign in with your work account and open your usual desktop or app.

If connection fails: Contact the service desk and include the time of failure and whether you are on office or home network.

Conditional Access check

If CA policies target the legacy client or generic "Microsoft Remote Desktop" app IDs, update policies to include Windows App where Microsoft documents the new application identifier. Test sign-in from pilot users before broad removal of legacy client.

Phase 5: Remove Legacy Client

After pilot sign-off:

1. Create Intune Uninstall assignment for the MSI Remote Desktop package where you previously deployed it
2. Block legacy client reinstall via App Control or software restriction policy if needed
3. Retire RD Web portal bookmarks from the intranet landing page — redirect to Windows App guidance
4. Monitor helpdesk volume for two weeks

Rollback

Prevention Checks

• Add Windows App version to standard desktop build image going forward
• Include remote access client in new-starter onboarding checklist
• Review Microsoft release notes quarterly for Windows App breaking changes
• Keep AVD and Windows 365 feed URLs in a single internally owned configuration document

Related Resources

• Microsoft Intune hub
• Intune vs SCCM/MECM
• Conditional Access Microsoft 365 Policy Map
• Microsoft Graph PowerShell migration

Source

This operational migration plan is based on the official Windows IT Pro Blog post published by Microsoft on March 30, 2026, extended with enterprise inventory, Intune deployment, and cutover steps for EUC administrators.