We are pleased to announce the public preview of symmetric NAT support for RDP Shortpath. This feature is the extension of the GA RDP Shortpath feature that allows us to establish a UDP connection indirectly using relay with the TURN (Traversal Using Relays around NAT) protocol for symmetric NAT.
What is TURN?
TURN is a popular standard for device-to-device networking that is now available for low latency, high-throughput data transmission with Azure Communication Services. It allows developers to quickly bootstrap to a high-performance, redundant, and globally scaled set of networking services that are often themselves complex and expensive to deploy. These services can power real-time communication between web or mobile applications built with open-source WebRTC clients, even when endpoints are behind NAT or firewalls that may prevent direct peer-to-peer connections. Developers can use the low-level standards-compliant TURN service for raw high-performance data transmission or layer voice or video communication experiences on top of this data channel.
How can I use it?
The feature is available in validation host pools and enabled for all connections. There is no additional configuration needed to enable the feature.
Since outbound connectivity is required between the session hosts and client to function as intended, we recommend allowing outbound UDP connectivity to the Internet. IT Admins can limit the port range used to listen to the incoming UDP flow.
The feature is currently available in 14 regions, and we are planning to extend it to other regions in the future. The connection initiated across regions will use UDP established through TURN where available. Otherwise, the connection will revert to the existing mechanism.
To learn more about the feature and configuration details, please check out Azure Virtual Desktop RDP Shortpath for public networks.
Further reading resources: