Skip to content

Commit 6edb7dc

Browse files
committed
Learn Editor: Update rdp-shortpath.md
1 parent 8155373 commit 6edb7dc

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/virtual-desktop/rdp-shortpath.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -197,8 +197,8 @@ The following table details the source, destination and protocol requirements fo
197197
| Name | Source | Source Port | Destination | Destination Port | Protocol | Action |
198198
|---|---|:---:|---|:---:|:---:|:---:|
199199
| STUN direct connection | VM subnet | Any | Any | 1024-65535<br />(*default 49152-65535*) | UDP | Allow |
200-
| STUN infrastructure/TURN | VM subnet | Any | `20.202.0.0/16` | 3478 | UDP | Allow |
201-
| TURN relay | VM subnet | Any | `51.5.0.0/16` | 3478 | UDP | Allow |
200+
| STUN/TURN relay| VM subnet | Any | `20.202.0.0/16` | 3478 | UDP | Allow |
201+
| STUN/TURN Relay | VM subnet | Any | `51.5.0.0/16` | 3478 | UDP | Allow |
202202

203203
#### Client network
204204

@@ -207,8 +207,8 @@ The following table details the source, destination and protocol requirements fo
207207
| Name | Source | Source Port | Destination | Destination Port | Protocol | Action |
208208
|---|---|:---:|---|:---:|:---:|:---:|
209209
| STUN direct connection | Client network | Any | Public IP addresses assigned to NAT Gateway or Azure Firewall (provided by the STUN endpoint) | 1024-65535<br />(*default 49152-65535*) | UDP | Allow |
210-
| STUN infrastructure/TURN relay | Client network | Any | `20.202.0.0/16` | 3478 | UDP | Allow |
211-
| TURN relay | Client network | Any | `51.5.0.0/16` | 3478 | UDP | Allow |
210+
| STUN/TURN relay | Client network | Any | `20.202.0.0/16` | 3478 | UDP | Allow |
211+
| STUN/TURN relay | Client network | Any | `51.5.0.0/16` | 3478 | UDP | Allow |
212212

213213
> [!NOTE]
214214
> From June 15th, the traffic will progressively be redirected from the current Azure Communication Service (ACS) TURN Relay range (`20.202.0.0/16`) to the 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 shouldn't experience any connectivity issues.

0 commit comments

Comments
 (0)