Rather interesting diagnostic.
Category: Cloud/Hosted Applications
Measure latency to Azure sites, live
article #1238, updated 517 days ago
Recommended DropBox replacement
article #967, updated 1319 days ago
This one’s new and comes recommended, I have not tested it yet:
Proxy exceptions for Office 365 and Related Services
article #779, updated 1835 days ago
These can be very helpful:
*.microsoftonline.com *.microsoftonline-p.com *.sharepoint.com *.outlook.com *.lync.com *.microsoft.com *.office.com *.office365.com
One reference among many: http://support.microsoft.com/kb/2637629
Tools to analyze hosted application performance issues
article #777, updated 1835 days ago
Here are a number of relevant tools:
Network packet studies, including TCP window scaling and much more
- Microsoft Netmon
- Microsoft Message Analyzer
Round-trip performance and path tracing
- PSPING on Windows, paping on Linux
- TraceTCP on Windows, tcptraceroute on Linux
- tracert on Windows, traceroute on Linux
Application-level data study
- Outlook Connection Status
Identify Microsoft data center in use, and GEO DNS
article #778, updated 1835 days ago
The resultant real hostname, will identify the actual data center in use. You will notice how this changes according to the Internet DNS servers being treated as authoritative; Microsoft calls this GEO DNS, meaning geographically-appropriate DNS.
Choosing the DNS servers for your ISP — presuming that your ISP has good DNS — will result in much better performance in Microsoft and many other web-based applications. If the ISP does not have good DNS, sometimes DNS servers of the company upstream from your ISP, will serve well.
The opposite of GEO DNS, is the use of DNS servers from the like of Google (220.127.116.11/18.104.22.168), OpenDNS (22.214.171.124/126.96.36.199), and others. Use of best GEO DNS can mean the difference between unusability (>300 ms ping for Office365) and excellence (50 ms).