Traveling users will sometimes complain about the performance of Outlook Web Access (OWA), especially if they’ve traveled to another continent. This is usually related more to network latency than to network bandwidth issues (Eritrea being a notable exception). For example, N. American users who travel to Europe can expect to see additional quarter- to half-second delays as their HTTP requests and replies travel across the Atlantic in both directions.
Satellite hops make the situation worse. That’s why most transoceanic Internet traffic uses fast cables, but the speed of light is still an absolute upper bound on how fast IP packets can move.
Mysteriously, the situation can often be worse in the case of people who have moved to another country but use OWA while traveling. Take the example of Jane, a U.S. employee who has relocated to Europe. Her IT department moved her mailbox to a European server, so she gets fast performance when she’s in the office. But when she travels within Europe, she uses OWA, which seems to run incredibly slowly.
What’s going on here? The problem is that she’s using the Web address that the U.S. IT department told her to use. It connects to a gateway (e.g., a Microsoft ISA server, reverse proxy, or VPN server) in North America. This was fine when she was based in North America, but now each request causes not two, but four unnecessary transatlantic hops:
- Web browser to U.S. gateway
- U.S. gateway to European OWA server
- European OWA server to U.S. gateway
- U.S. gateway to Web browser
One solution is for IT to replace the well-known OWA locations with a standard front page telling people which link to use, encouraging employees to use the gateway closest to them. For example:
- Click the location closest to your current location: