Microsoft has announced that RDP Multipath with redundant TCP transport paths is now generally available for Azure Virtual Desktop. This marks the completion of a journey that began with a public preview in June 2025, expanded with redundant TCP support in April 2026, and has now reached full GA as of July 2026.

If you’re managing Azure Virtual Desktop environments, this is one of those networking improvements that quietly makes everything better without requiring you to do anything. Here’s what shipped, why it matters, and what you should know.

What RDP Multipath Actually Does

RDP Multipath is Microsoft’s approach to solving one of the most persistent problems in remote desktop services: session disconnects caused by network instability.

Traditionally, RDP connections between a client and a session host rely on a single network path. When that path degrades — whether due to Wi-Fi interference, ISP routing changes, VPN hiccups, or corporate firewall behavior — the session stutters or drops entirely. Users experience frozen screens, reconnect loops, and lost work.

RDP Multipath changes this by maintaining multiple network paths simultaneously between the client and the session host. Using Interactive Connectivity Establishment (ICE), the feature discovers available paths and keeps them on standby. When the active path degrades, the session automatically switches to the best alternative without user intervention.

The Path Types

With the GA release, RDP Multipath can maintain three types of transport paths:

  1. UDP over STUN — Direct UDP connections established through NAT traversal
  2. UDP over Relay (TURN) — UDP connections relayed through Microsoft’s TURN infrastructure (now expanded to 39 Azure regions with dedicated IP range 51.5.0.0/16)
  3. TCP reverse connect over AVD gateways — TCP-based connections that traverse inbound through Azure’s gateway infrastructure, critical for environments where UDP is blocked

The key advancement in this GA release is that TCP-based paths are now first-class citizens in the multipath ecosystem. Previously, RDP Multipath focused on UDP paths. Now, if your network environment blocks UDP (as many corporate and educational networks do), the session can still benefit from multipath redundancy using TCP paths alone.

The Journey to GA

This feature has been through a measured rollout:

  • June 2025: RDP Multipath initially announced as public preview, focusing on UDP path redundancy
  • November 2025: Phased deployment completed across all eligible connections for UDP multipath
  • April 2026: Redundant TCP transport paths added in public preview, expanding multipath to TCP-based connections
  • May 2026: Phased GA rollout begins, starting with validation-ring host pools
  • July 2026: Full general availability — no more validation-ring gating, enabled by default when prerequisites are met

Microsoft’s approach here was deliberate. Rather than flipping a switch, they rolled the feature through validation rings, monitored quality, and expanded gradually. The July 2026 GA announcement means the feature is now broadly enabled without special enrollment.

What This Means for IT Admins

Key Benefits at GA

The July 2026 announcement highlights four specific benefits:

  1. Improved session resiliency across restrictive network environments — The TCP path support means multipath works even where UDP is blocked by firewalls or network policies. This is huge for organizations in regulated industries, education, and sectors with strict network controls.

  2. Automatic failover between available transport paths — When the active path degrades, the session switches automatically. No user action, no help desk ticket, no reconnect dance.

  3. Reduced session interruptions and disconnects — The practical outcome users will notice. Fewer frozen sessions, fewer reconnect loops, fewer support calls about “my remote desktop keeps disconnecting.”

  4. No additional configuration required when prerequisites are met — This is perhaps the most important point for IT teams. If you’re already using RDP Shortpath (which you should be), multipath is enabled automatically. There’s no new GPO to configure, no Intune policy to deploy, no PowerShell script to run.

Prerequisites

To benefit from RDP Multipath GA, your environment needs:

  • RDP Shortpath configured as the primary transport protocol
  • Windows App (latest version recommended) or Remote Desktop client (MSRDC 1.2.6074 or later)
  • Standard AVD host pool requirements
  • At GA, validation-ring enrollment is no longer required — the feature is enabled by default

For the best experience, allow both UDP and TCP outbound to AVD gateway endpoints. If UDP is blocked in your environment, TCP fallback now provides meaningful redundancy that wasn’t available before.

How to Verify It’s Working

Users can check if multipath is active by:

  1. Opening the connection bar in the remote session
  2. Clicking the information icon
  3. Looking for “RDP Multipath: Enabled”

Azure Virtual Desktop Insights also provides diagnostics for connection quality and can help identify whether multipath is being used and whether path switching events are occurring.

Comparison: Before and After

Transport MethodBehaviorLimitation
Traditional RDP (TCP-only)Single TCP path, no failoverSensitive to latency, single point of failure
RDP Shortpath (UDP)Lower-latency UDP pathSingle path, no redundancy, requires UDP availability
RDP Multipath (UDP only)Multiple UDP paths, dynamic selectionUDP-only, requires UDP availability
RDP Multipath GA (UDP + TCP)Multiple UDP + TCP paths, full redundancyNone — works in restrictive networks

The progression here tells a clear story: Microsoft first improved performance (Shortpath), then added resilience (Multipath UDP), then removed the UDP dependency (Multipath TCP), and now made it all work transparently (GA with zero-config).

Considerations and Limitations

While this is a significant improvement, there are a few things to keep in mind:

  • Network middleboxes — Deep packet inspection, traffic hair-pinning, or aggressive middleboxes can affect path quality detection. If you’re seeing unexpected behavior, check whether DPI or traffic optimization appliances are interfering with RDP traffic.

  • Client requirements — Users need a supported client. The Windows App is the recommended client and receives the most updates. Older Remote Desktop client versions may not support all multipath features.

  • Best results with both protocols — While TCP-only multipath provides redundancy, the best experience comes from allowing both UDP and TCP. If you can allow UDP outbound to AVD endpoints, do so.

  • Firewall rules — Verify that AVD gateway IPs are reachable from your client networks. The dedicated IP range for TURN relay is 51.5.0.0/16.

  • Not a silver bullet for all network issues — Multipath improves resilience against transient network problems. It won’t fix fundamentally undersized bandwidth or chronic latency issues between your users and Azure regions.

What You Should Do Now

  1. Verify RDP Shortpath is configured — If you haven’t enabled Shortpath yet, now is the time. Multipath builds on Shortpath, so it’s a prerequisite.

  2. Update client software — Ensure users are on the latest Windows App version. Older clients won’t benefit from the full GA features.

  3. Review firewall rules — Confirm that both UDP and TCP outbound to AVD gateway endpoints are allowed from your user networks. The more paths available, the better the redundancy.

  4. Monitor Azure Virtual Desktop Insights — Watch for changes in connection quality metrics after the GA rollout reaches your users. You should see fewer disconnects and improved session stability.

  5. Update your documentation — If your team has runbooks or user guides that mention RDP connection limitations, update them to reflect that multipath is now GA and provides automatic failover.

The Bigger Picture

RDP Multipath GA is part of a broader trend in Azure Virtual Desktop’s evolution. Microsoft has been systematically addressing the networking challenges that have historically plagued VDI deployments:

  • RDP Shortpath reduced latency by moving from TCP to UDP
  • Private Link support enabled private network paths with GA in February 2026
  • Centralized Shortpath management (January 2026 GA) made configuration scalable through Intune and GPO
  • TURN Relay global expansion (September 2025) improved reachability across 39 Azure regions
  • RDP Multipath GA now ties it all together with automatic path redundancy

The result is an AVD networking stack that is dramatically more resilient than it was 18 months ago. For organizations considering AVD as a primary VDI platform — or those already deployed who have been waiting for networking maturity — this is a meaningful milestone.

Summary

RDP Multipath with redundant TCP transport paths reaching GA is the kind of update that doesn’t make headlines but makes a real difference in day-to-day user experience. Sessions stay connected when networks get flaky. Help desks get fewer “my desktop disconnected” tickets. IT teams don’t need to configure anything new.

If you’re running Azure Virtual Desktop, this is already rolling out to your environment. Make sure your clients are updated, your Shortpath is configured, and your firewall rules allow the necessary outbound traffic. Then let multipath do its job.

Kevin Kaminski is the owner of Big Hat Group Inc., a Microsoft partner focused on AI and cloud technologies. Follow him at https://x.com/kkaminsk for more Azure Virtual Desktop insights.