Why your typing speed depends on the network now
If you type on a Windows 365 Cloud PC, the “feel” of every keypress depends on how quickly your input reaches the remote session and how fast the screen refresh comes back. Classic HCI studies show we start to notice input‑to‑feedback delays around the 50–100 ms range; beyond ~100 ms, echo feels laggy and people slow down or make more corrections. That makes end‑to‑end latency (network + rendering) the new limiter for WPM when you’re remoting. (hci.rwth-aachen.de)
In 2026, Microsoft’s cloud‑first RDP stack for Windows 365 is purpose‑built to reduce those delays by favoring UDP where possible (RDP Shortpath), falling back cleanly when it can’t (TURN relays), and even keeping multiple paths ready at once (RDP Multipath). (learn.microsoft.com)
The pipeline: separating network from rendering delay
A remote keystroke travels this path: keyboard → client → network → Cloud PC input stack → app renders a new frame → encoder → network → client decoder → display. To reason about your WPM, separate two buckets:
- Network and transport: round‑trip time (RTT), jitter, loss, and how the protocol handles them (TCP vs reliable UDP). (learn.microsoft.com)
- Rendering and encode/decode: the desktop compositor and codec pipeline that add a few to tens of milliseconds depending on load and settings. (Prior work on interactive pipelines and cloud rendering highlights how each stage contributes its own slice.) (arxiv.org)
RDP in 2026: what changed for typists
- Modern RDP for Windows 365 uses outbound TCP 443 (reverse connect) for control and can upgrade to UDP for media over port 3478. No inbound ports are required. That design avoids brittle perimeter holes while enabling low‑latency paths. (learn.microsoft.com)
- RDP Shortpath tries direct UDP (STUN/ICE) first; if your enterprise NAT, CGN, or proxies block it, the client and Cloud PC will automatically use Microsoft’s globally distributed TURN relays over UDP 3478. Either way, your keystrokes ride UDP with reliability layered on top, avoiding TCP’s head‑of‑line blocking. (learn.microsoft.com)
- TURN relay endpoints now sit on a dedicated Microsoft subnet (51.5.0.0/16) for Windows 365 and AVD, which makes firewall and SWG/VPN bypass rules simpler—and often faster. (learn.microsoft.com)
- RDP Multipath keeps multiple candidate paths warm (e.g., STUN and TURN over UDP, plus redundant TCP) and can switch without dropping your session if a path degrades. That improves consistency during typing drills and live work. (learn.microsoft.com)
Why UDP helps for typing: RDP’s reliable‑UDP transport and URCP rate control adapt to loss and congestion without incurring TCP’s retransmit delays across the entire stream, so characters echo sooner and more consistently under the same RTT and loss. (learn.microsoft.com)
Practical setup that measurably reduces key‑to‑echo time
These changes only help if the traffic takes the right path. Here’s a checklist teams can apply:
1) Bypass inspection and tunnels for RDP endpoints
- Disable TLS inspection for RDP; Windows 365 uses nested TLS, and inspection adds latency/jitter without security benefit. (learn.microsoft.com)
- Force local breakout for RDP so traffic hits Microsoft’s nearest gateway or TURN relay instead of hair‑pinning through distant VPN/SWG points. This cuts RTT and stabilizes echo. (learn.microsoft.com)
2) Allow and prefer UDP
- Permit outbound UDP/3478 to Microsoft’s TURN subnet 51.5.0.0/16 on both client and Cloud PC sides. This enables relayed Shortpath almost everywhere. (learn.microsoft.com)
- If you use an Azure Network Connection (ANC) VNet and want private‑network Shortpath, allow the UDP listener (default 3390) and plan for NAT port scale. Direct private UDP often wins the “first‑found” race and lowers latency. (learn.microsoft.com)
3) Verify the path you’re actually using
- In the Windows App/Remote Desktop client, open Connection information during a session to see the transport (e.g., UDP via STUN, UDP via TURN, or TCP). If it says TCP, you’re leaving WPM on the table. (learn.microsoft.com)
- Use Microsoft’s guidance on “Understanding RDP Traffic” to confirm the right ports and subnets are bypassed on proxies, SWGs, and VPNs. (learn.microsoft.com)
4) Enable RDP Multipath and up‑to‑date clients
- Multipath requires current clients (Windows App 2.0.559.0+; MSRDC 1.2.6353+), and as of May 2026 Microsoft is rolling out redundant TCP paths as a phased GA. Even when you’re on TCP, that resiliency smooths hiccups that feel like “sticky keys.” (learn.microsoft.com)
How to measure your real‑world typing latency (no special tools)
You don’t need lab gear to separate network from rendering delay:
- Camera method (fast and simple)
- Put your phone in 240 fps slow‑motion facing both your hands and the screen.
- Press a single key repeatedly in Notepad on the Cloud PC; count frames between finger‑down and the first pixel change of the character. Repeat 20× and average. Then compare with a local Notepad window to estimate added remote overhead. Now switch conditions: on a corporate VPN (TCP), off VPN (TURN), and on a managed/private path if available. (learn.microsoft.com)
- Client telemetry method
- While connected, open Connection information to record the transport and RTT/jitter. Correlate the median RTT with your camera‑measured key‑to‑echo; you’ll typically see that better paths (UDP Shortpath) shave a noticeable fraction of the round‑trip. (learn.microsoft.com)
What to expect: Direct STUN often fails in enterprise networks due to symmetric NAT or double NAT; in those cases the TURN path is the reliable winner, especially once it’s locally broken out. Optimization guidance explicitly calls out that local egress to the nearest Microsoft edge/relay reduces RTT and improves responsiveness. (learn.microsoft.com)
Windows 365 Switch: faster context changes during drills
When you’re practicing typing or bouncing between a local tool and a Cloud PC IDE, Windows 365 Switch lets you jump between desktops via Windows 11 Task view (Win+Tab) and even pin a Cloud PC there. That eliminates the “hunt the client window” dance and reduces mental context‑switch costs during speed tests. Setup is quick: add one Cloud PC to Task view from the Windows 365 app. (support.microsoft.com)
Quick tips for typists and admins
- If the client shows TCP, check your SWG/VPN bypass rules for *.wvd.microsoft.com (TCP 443) and 51.5.0.0/16 (UDP 3478). Aim for local egress on both sides. (learn.microsoft.com)
- Prefer wired or strong Wi‑Fi 6/6E on the client; packet loss makes any protocol feel sticky, but reliable‑UDP copes better under the same loss than TCP. (learn.microsoft.com)
- Keep the Windows App current and enable Multipath; per Microsoft, a single user can light up to five outbound transport paths (three UDP, two TCP) for resilience—useful in real offices with variable Wi‑Fi. (learn.microsoft.com)
- For ANC/private scenarios, consider enabling Shortpath’s UDP listener (default 3390) and plan NAT capacity so many concurrent typists don’t run out of ports. (learn.microsoft.com)
The bottom line
If your Cloud PC still “feels” behind your fingers, it’s probably the path, not the PC. Favor UDP Shortpath, make sure TURN relays are reachable on 51.5.0.0/16 with local breakout, and let Multipath keep a standby. Then verify in the client, measure with a quick camera test, and enjoy a snappier echo that helps your WPM—without changing keyboards. (learn.microsoft.com)
