Your offshore team in India works inside virtual desktops hosted in a US data centre, because that is where your applications and data live. Typing lags, screens redraw slowly, video calls from inside the desktop stutter, and productivity reports blame “the internet.” Your IT team has upgraded bandwidth twice and nothing changed much.
That is because the main problem is distance, not bandwidth. Round-trip time between India and the US has a hard physical floor, and remote desktop protocols feel that delay on every keystroke and screen update. You cannot buy your way past physics, but you can reduce the pain: host desktops closer to the users where data rules allow, keep the desktop near the applications while optimising the display protocol, use UDP-based transports, avoid backhauling traffic through distant VPNs, and move latency-sensitive tasks such as calls out of the virtual desktop.
Why more bandwidth does not fix it
Light in optical fibre travels at roughly two-thirds of its speed in a vacuum, about 200,000 kilometres per second. A US to India path covers well over 10,000 kilometres each way, and real cable routes and network hops add distance and delay. The result is a round-trip time that no bandwidth upgrade can remove.
Remote desktop sessions are interactive: every key press travels to the server and the screen update travels back. Latency, jitter and packet loss matter more than raw throughput.
Options, from least to most change
| Option | Effect | Trade-off |
|---|---|---|
| Enable UDP-based transport (for example RDP Shortpath in Azure Virtual Desktop) | Better throughput and responsiveness on lossy long-distance links | Requires network and firewall configuration |
| Remove VPN backhaul and hairpinning | Traffic takes a direct path to the desktop service | Needs security design for direct access |
| Tune display settings | Lower colour depth, disable animations and wallpapers, optimise codecs | Slightly less visual fidelity |
| Offload calls and video | Use local clients or media optimisation for Teams and similar tools | Policy and configuration work |
| Host desktops in an Indian region, keep data in the US | Desktop feels local; application traffic crosses the ocean instead | Chatty applications may get slower; data residency review needed |
| Host desktops and applications near users | Best experience | Data residency, compliance and architecture changes |
What Microsoft’s guidance points to
For Azure Virtual Desktop, Microsoft’s Cloud Adoption Framework recommends measuring round-trip time from client locations and placing session hosts in the region closest to end users with the lowest RTT. It also documents RDP Shortpath, which establishes a UDP-based transport between the client and session host, using a rate control protocol designed for low delay and loss, and falls back to TCP if UDP is unavailable. Similar principles apply to other VDI platforms.
Where should the desktop live?
The key question is which link is more latency sensitive: user to desktop, or desktop to application.
- Browser-based SaaS apps: host the desktop near users; SaaS traffic is usually tolerant.
- Thick-client apps talking constantly to a US database: keep the desktop near the database and optimise the display link.
- Compliance requires data to stay in the US: keep desktops in the US and focus on transport, display and call optimisation, or consider whether the work can use data minimisation.
Measure before redesigning
- Measure RTT, jitter and packet loss from each office and home location to each candidate region.
- Record user experience for key tasks: data entry, screen navigation, calls.
- Identify whether traffic is routed via a US VPN concentrator or security proxy.
- Test one pilot group with UDP transport and tuned settings before larger changes.
A hypothetical example: a US insurance services firm with 80 staff in Pune moves them from TCP-only connections through a US VPN to direct UDP-based desktop connections, disables visual effects and runs calls on local clients. Complaints drop sharply without moving any data out of the US.
Security still matters as much as speed. For how to think about offshore access risk, see modelling the access, not the geography.
Offshore desktops that feel usable
Fixing long-distance virtual desktop performance takes network, platform and application knowledge together. AB7 Solutions’ cloud and DevOps and managed services teams assess VDI performance from user locations, configure Azure Virtual Desktop and similar platforms, optimise transport and display settings, redesign routing and security access, and plan region and data residency options. If tuning alone will solve most of the problem, we will start there.
Tell us where your users are, where desktops and applications are hosted, and what tasks feel slow, and we will suggest the first changes to test.
Email: ab@ab7solutions.com | director@ab7solutions.com
Phone: +91 9878067778 | +1 321 341 7733
Website: www.ab7solutions.com
Sources: Microsoft Learn, Azure Virtual Desktop network topology and connectivity; Microsoft Learn, RDP Shortpath.
[…] your remote team sits far from where desktops are hosted, see how to reduce latency for offshore users on US virtual desktops, and for risk framing, modelling the access, not the […]