Use DS Multipath to improve connection reliability to Azure Virtual Desktop

Direct Stream (DS) Multipath improves session stability by continuously monitoring multiple network paths and dynamically selecting the most reliable one. This intelligent switching mechanism helps reduce the likelihood of disconnections and contributes to a smoother and more consistent user experience across different network conditions.

It offers several key benefits:

  • Seamless integration: No configuration changes are needed beyond ensuring your environment supports DS Shortpath.

  • Intelligent path management: ICE discovers and evaluates multiple Direct Stream (DS) Shortpath routes using User Datagram Protocol (UDP) over STUN (Simple Traversal Underneath NAT) and TURN (Traversal Using Relays around NAT) protocols.

  • Enhanced reliability: Backup paths remain on standby. If the active path becomes unstable or fails, DS Multipath automatically switches to the next best path, reducing session drops and interruptions.

DS Multipath uses multiple network paths to improve connection reliability. These paths can include combinations of UDP-based STUN or TURN connections when UDP connectivity is available, along with redundant TCP-based Reverse Connect paths established using Rendezvous. If the main transport path becomes degraded or fails, the system automatically switches to a backup available UDP or TCP transport path. If all paths are lost—such as during a network outage—the system attempts to reconnect once network connectivity is restored. 

The following diagram illustrates how DS Multipath works with Azure Virtual Desktop. In this user scenario, the primary active transport path is UDP via STUN, supplemented by redundant UDP connections through a TURN server.

When UDP‑based DS Shortpath connectivity is available, UDP remains the preferred transport protocol for optimal performance and reliability. In addition to maintaining redundant UDP paths, Azure Virtual Desktop can establish redundant TCP standby transport paths to improve overall session resiliency.

Diagram that shows RDP Multipath network paths.

Availability

DS Multipath capabilities are available across the following Azure environments:

Environment Multiple UDP transport paths Redundant TCP transport paths
Azure public cloud Generally available Generally available
Azure Government Generally available Generally available

Prerequisites

DS Multipath works automatically when the following prerequisites are met:

  • Microsoft recommends configuring DS Shortpath as the primary transport protocol to maximize the resiliency benefits of DS Multipath. For more information, see Configure DS Shortpath.

  • Windows App for Windows:

    • Connections must be from a local Windows device using Windows App, version 2.0.559.0 or later, which is the minimum supported version for DS Multipath. This version enables DS Multipath with multiple UDP transport paths.

    • To take advantage of the latest DS Multipath enhancements, including support for multiple UDP transport paths and redundant TCP transport paths, connections must use Windows App Version 2.0.1069.0 or later

  • Windows App for macOS Beta: DS Multipath with multiple UDP transport paths is supported with Windows App for macOS Beta version 11.3.8 (3048).

  • Other platforms aren't currently supported.

Required network endpoints for DS transport

To support DS connectivity using UDP-based DS Shortpath and DS Multipath, as well as TCP-based connections over Reverse Connect, ensure outbound connectivity to the following endpoints:

# DS method FQDN IP address Protocol/port Description
1 TCP-based DS *.wvd.microsoft.com 40.64.144.0/20 TCP 443 TCP-based DS connection. The initial connection to every session host or Cloud PC uses this connection.
2 UDP-based DS via TURN N/A 51.5.0.0/16 UDP 3478 Relayed UDP-based DS connection using TURN servers. This method works when direct connectivity isn't possible.
3 UDP-based DS using STUN N/A 51.5.0.0/16 UDP 1024-65535
Default: 49152-65535
Direct one-to-one UDP connection between the user device and the session host or Cloud PC.