Windows 365 RDP Multipath with Redundant TCP Now Generally Available

Microsoft has officially declared RDP Multipath with redundant TCP transport paths generally available for Windows 365 Cloud PC, appearing in the Week of July 6, 2026 update to the Windows 365 What’s New documentation. This marks the completion of a rollout that began in May and represents a significant step forward in connection reliability for Cloud PC users.

What RDP Multipath with Redundant TCP Does

RDP Multipath isn’t new — the core feature has been generally available since 2025, using Interactive Connectivity Establishment (ICE) to discover and manage multiple network paths for Remote Desktop Protocol connections. What’s new is the redundant TCP transport paths layer.

Until now, RDP Multipath primarily relied on UDP-based paths:

UDP over STUN (Session Traversal Utilities for NAT) — the fastest, lowest-latency path
UDP over TURN (Traversal Using Relays around NAT) — a relay-based fallback

The problem? Not all networks allow UDP. Corporate firewalls, proxy environments, and restrictive network policies often block UDP traffic entirely. In those scenarios, RDP Multipath had limited value — connections fell back to a single TCP path with no redundancy.

Redundant TCP transport paths solve this by adding multiple TCP-based reverse connect transport paths through Azure Virtual Desktop gateways. The system can now maintain a mix of UDP and TCP standby paths simultaneously, with automatic, transparent failover when any active path degrades.

Key Benefits

Microsoft’s July 6 announcement highlights four primary benefits:

Improved session resiliency across restrictive network environments — TCP redundancy works where UDP is blocked, giving organizations failover options in corporate and locked-down networks
Automatic failover between available transport paths — no user or admin intervention required; the system switches paths transparently
Reduced session interruptions and disconnects — standby paths are pre-established, so failover is near-instantaneous
No additional configuration required — if prerequisites are met, the feature activates automatically

The Timeline

This has been a multi-stage rollout:

April 21, 2026 — Microsoft announced public preview of redundant TCP support for RDP Multipath on the Azure Virtual Desktop Tech Community blog
May 11, 2026 — GA rollout begins for Windows 365, with a phased, quality-driven approach documented on the What’s New page
July 6, 2026 — Full general availability confirmed with expanded benefits documentation

The phased rollout approach means Microsoft has been gradually enabling the feature across host pools worldwide, monitoring quality metrics before expanding to the next batch. The July 6 announcement signals that this process is now complete.

Prerequisites

To take advantage of redundant TCP transport paths, ensure the following:

Windows App version 2.0.1069.0 or later on the client device — earlier versions support UDP-only Multipath but not TCP redundancy
RDP Shortpath configured as the primary transport — Multipath depends on it even for TCP fallback
Outbound UDP allowed for STUN and TURN (for UDP paths to function)
TCP connections allowed for reverse connect through AVD gateways
Avoid traffic hair-pinning through centralized appliances or applying deep packet inspection — reshaping or delaying TCP streams can cause false failovers and reduce Multipath effectiveness

Platform Support

Important limitation: redundant TCP transport paths are currently supported only on Windows devices using Windows App on Windows client. Non-Windows clients (macOS, iOS, Android, Linux) do not currently support TCP redundancy. UDP-only Multipath works on a broader client set, but the TCP fallback is Windows-only at this time.

If your organization has users connecting from macOS or mobile devices, they’ll still benefit from UDP-based Multipath but won’t get the TCP redundancy layer.

How to Verify It’s Working

Users can check the connection status bar in Windows App during a remote session — it indicates whether RDP Multipath is active. For deeper diagnostics, AVD Insights provides detailed connection telemetry showing which transport paths are in use and when failovers occur.

Manual Enable/Disable

While the feature is designed to activate automatically when prerequisites are met, admins can manually control it via registry key on the Cloud PC:

Enable:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RdpCloudStackSettings" /v SmilesV3ActivationThreshold /t REG_DWORD /d 100 /f

Disable:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RdpCloudStackSettings" /v SmilesV3ActivationThreshold /t REG_DWORD /d 0 /f

After changing the registry key, users must disconnect and reconnect for the change to take effect.

What This Means for IT Admins

For Network-Restricted Environments

If your users operate behind corporate firewalls that block UDP, this is a meaningful improvement. Previously, those users had a single TCP path with no redundancy — any network hiccup could disconnect their session. Now they get multiple TCP paths with automatic failover, dramatically improving session stability.

For BYOD Scenarios

Bring-your-own-device users connecting from home networks, coffee shops, or hotels often encounter unpredictable network conditions. Redundant TCP paths provide a safety net that UDP-only Multipath couldn’t deliver in those environments.

For Support Teams

Expect fewer helpdesk tickets related to “my Cloud PC disconnected.” The automatic failover is transparent to users — they may not even notice a path switch occurred. But if you’re troubleshooting connection issues, be aware that the connection path may change mid-session, which could affect diagnostic approaches.

No Action Required — Mostly

The best news for busy IT teams: no configuration changes are needed if your environment already supports RDP Shortpath. The feature activates automatically. The main action item is ensuring users are on Windows App 2.0.1069.0 or later.

Action Items

Verify Windows App versions across your user base — ensure everyone is on 2.0.1069.0 or later
Review firewall rules to ensure TCP connections to AVD gateways are allowed (most environments already do this)
Monitor connection telemetry in AVD Insights to confirm TCP redundancy is activating in your environment
Update network documentation if you previously noted UDP-only limitations for RDP Multipath
Inform support teams about the new failover behavior so they’re aware during connection troubleshooting

The Bigger Picture

This update is part of Microsoft’s broader investment in Windows 365 connection reliability. The journey so far:

RDP Shortpath (managed networks) → RDP Shortpath (public networks) → RDP Multipath (UDP) → RDP Multipath with redundant TCP

Each layer adds resiliency for a broader set of network conditions. The redundant TCP layer is particularly important because it addresses the last major gap: environments where UDP simply isn’t an option.

Combined with other recent Windows 365 updates — including context-based redirections for BYOD scenarios, Cloud PC Monitoring for admin visibility, and the ongoing expansion of Flex shared regions — Microsoft is steadily closing the gap between Cloud PC connectivity and local desktop reliability.

Big Hat Group helps organizations deploy and optimize Windows 365 and Microsoft Intune environments. Need help improving your Cloud PC connectivity strategy? Get in touch.