Learn Editor: Update rdp-shortpath.md

Author: ridalwan

articles/virtual-desktop/rdp-shortpath.md

@@ -190,23 +190,7 @@ The following sections contain the source, destination and protocol requirements
 > [!NOTE]
 > For a relayed connection with TURN, the IP subnet **`20.202.0.0/16`** is shared with Azure Communication Services. However, **Azure Virtual Desktop and Windows 365 will transition to the dedicated IP range `51.5.0.0/16`**, which is exclusively reserved for these services.
 > **What to expect:** Starting **June 15**, Microsoft will begin rolling out the new TURN relay IP range **`51.5.0.0/16`** across **40 Azure regions**. This upgrade enhances **RDP Shortpath for public networks (via TURN/Relay)** connectivity, delivering faster, more reliable performance for Azure Virtual Desktop (AVD) and Windows 365 (W365) users.
-> **What admins should do:** To ensure uninterrupted service and optimal performance, administrators should:
-> - **Ensure accessibility**: Make sure the `51.5.0.0/16` subnet is accessible from all networks used for AVD and W365 connectivity, both on-premises and in the cloud.
-> - **Use the `WindowsVirtualDesktop` service tag**: This tag includes the new subnet, simplifying firewall and network rule configuration.
-> - **Optimize traffic flow**:
->   - Avoid TLS inspection on this traffic, as it is already encrypted and inspection can degrade performance.
->   - Ensure traffic is **locally egressed**—routed directly to Microsoft’s infrastructure without unnecessary detours.
->   - **Bypass VPNs, proxies, and Secure Web Gateways (SWGs)** for this traffic to reduce latency and improve reliability.
->   - Use **User Defined Routes (UDRs)** in Azure to direct traffic to the internet instead of through virtual firewalls when needed.
-> **Supported Regions:** The new TURN relay infrastructure is being deployed in 40 regions, including:
->
-> - **North America**: South Central US, East US, East US 2, East US2 EUAP, West Central US, West US, West US 2, West US 3, Central US, North Central US, Canada Central, Canada East, Mexico Central
-> - **South America**: Brazil South
-> - **Europe**: UK South, UK West, West Europe, North Europe, France Central, Germany West Central, Switzerland North, Norway East, Italy North, Poland Central, Sweden Central, Spain Central
-> - **Asia**: South India, Central India, UAE North, UAE Central, South East Asia, Korea Central, Korea South, Taiwan North, Israel Central, Japan East, Japan West
-> - **Oceania**: Australia East, Australia Southeast
-> - **Africa**: South Africa North, South Africa West
->
+
 #### Session host virtual network
 
 The following table details the source, destination and protocol requirements for RDP Shortpath for your session host virtual network.
@@ -227,6 +211,9 @@ The following table details the source, destination and protocol requirements fo
 | STUN infrastructure/TURN relay | Client network | Any | `20.202.0.0/16` | 3478 | UDP | Allow |
 | TURN relay | Client network | Any | `51.5.0.0/16` | 3478 | UDP | Allow |
 
+> [!NOTE]
+> From June 15th, the traffic will progressively __redirected__ from the current Azure Communication Service(ACS) TURN Relay range (**`20.202.0.0/16`**) to a newly designated subnet (**`51.5.0.0/16`**). While this shift is designed to be seamless, it’s essential that customers __preemptively configure bypass rules__ for the new range to maintain uninterrupted service. With both IP ranges properly bypassed, end users will not experience any connectivity issues
+
 ### Teredo support
 
 While not required for RDP Shortpath, Teredo adds extra NAT traversal candidates and increases the chance of the successful RDP Shortpath connection in IPv4-only networks. To learn how to enable Teredo on session hosts and clients, see [Enable Teredo support](configure-rdp-shortpath.md#optional-enable-teredo-support).