This proof of concept (POC) tool runs tests that allow providing specific guidance about networking connectivity improvements that can be made between a user location to Office 365. Please try the tests and give us your feedback about how we could improve the tool to support networking connectivity to Office 365.
Several factors influence the quality of your Office 365 experience, including your network egress architecture, your Internet Service Provider (ISP), and the network path used to connect into Office 365 service front doors. This tool tests these elements and provides recommendations to improve your Office 365 performance.
Please wait while testing is in progress.
Please open this website in Microsoft Edge on a Windows PC to run the advanced tests.
We found specific recommended actions you can take to improve network performance for Office 365.
We did not find any specific actions you can take to improve network performance for Office 365.
|You are here||
Your DNS Server Location
(requires advanced tests)
|Your egress location||
Your Proxy Server location
(requires advanced tests)
|Your Optimal Front door location||Sub-optimal front door connection|
This table shows customers near you grouped by relative performance and shows you where your performance ranks with them. It aggregates customer diagnostic data by city or who are near a common metro area.
During the POC we are asking for your perception of Office 365 performance to help us evaluate this table. Clicking the appropriate button will share your perception along side the performance we selected with Microsoft.
|Customers near you||Performance||Your perception|
|Network egress location|
|User to network egress distance||
|Office 365 Exchange Online service front door location||
|Optimal Office 365 Exchange Online service front door(s) for user location|
|Customers in your metro area with better performance||
|User's default gateway||
|Client DNS Server|
|Client DNS Recursive Resolver||
|Exchange Online DNS server|
|SharePoint Online DNS server|
|Proxy server identification||
|Media connectivity check||
|Media quality packet loss|
|Media quality latency|
|Media quality jitter|
|Media quality packet reorder|
User location - This is the location of the user who performed the test. Also shown is whether they used their web browser location detection, or if they typed in a location.
Network egress location - This is the location of the user's NAT IP Address as detected as the source IP Address by our web server. The location is looked up and the database used may not have the correct location for a specific IP Address. This IP Address could also be the location of a CASB or cloud proxy server that intercepts the customers network traffic.
User to network egress distance - We calculate direct distance from the user's identified location to the identified network egress location. We are using the threshold of 500 miles (800 kilometers) as estimated as 25ms of latency and any longer distance is expected to cause performance issues as indicated by a red mark. A green check indicates we did not find that.
Office 365 Exchange Online service front door location - This is identified by the test in the same way that the Outlook desktop client locates the Office 365 Exchange Online service front door. On the map we show the location of the city where the service front door is located. It is not an exact location. A red mark indicates that this service front door location is not in the list of optimal service front door locations. If an optimal service front door is not in use, we show the predicted improvement in latency if changes are made to connect to an optimal service front door. This predicted improvement may not be achieved exactly. We run this test 25 times and show the lowest latency recorded. The lowest latency is used to avoid any transitory latency increase caused by network congestion.
Optimal Office 365 Exchange Online service front door(s) - For the user's identified location this list shows the optimal Office 365 Exchange Online service front door locations. Microsoft continues to expand service front door locations and the best action to improve performance where a more optimal service front door is identified is to improve local and direct egress.
Customers in your metro area with better performance - On the user page we show a table of bucketed latencies to the Office 365 Exchange Online service front door for customers in the same metro area as the test user. If there are 10% of customers who have better latency than the test result, then we would expect the test user to be also able to achieve a better latency.
User's default gateway (requires advanced tests) - We identified the default route IP Address for the router that the client is connected to. We test latency to this router and the test fails if it is greater than 25ms away.
Client DNS server (requires advanced tests) - We measure the time that the client takes to make a DNS request on their LAN environment. If this is greater than 25ms then the test fails.
Client DNS Recursive Resolver (requires advanced tests) - The recursive resolver DNS server is the DNS server which actually connects to an Exchange Online name server. We identify this name server and measure the distance to it. If this is greater than 500 miles or the latency is greater than 25ms then the test fails.
Exchange Online DNS server (requires advanced tests) - This shows the result when looking up the Exchange Online service front door in the DNS. It can be used for further analysis of network performance.
SharePoint Online DNS server (requires advanced tests) - This shows the result when looking up the SharePoint Online service front door in the DNS. It can be used for further analysis of network performance.
Proxy server identification (requires advanced tests) - This identifies if a proxy server is configured on the test client machine. If a proxy server is configured and it is more than 500 miles away from the user or the measured latency is more than 25 ms then the test fails.
Media connectivity check (requires advanced tests) - We use the Skype for Business Network Assessment Tool to test UDP connectivity to media relays.
Media quality (requires advanced tests) - We use the Skype for Business Network Assessment Tool to test media quality across four measurements.
Connectivity tests (requires advanced tests) - We have two types of connectivity tests. First is TCP/IP connectivity to all required Office 365 FQDNs and also example FQDNs for required URL wildcards. Any required endpoints that cannot be connected to are listed. Second is testing for SSL encryption interception. Office 365 requires that Optimize and Allow category endpoints not be SSL intercepted and we test for interception on each of those.
Network path diagnostics (requires advanced tests) - Traceroute to each of the Office 365 primary service front doors are listed. These can be used for further analysis of network performance.
Here are the answers to some of our frequently asked questions.
It is currently a proof of concept and we plan to provide updates regularly until we reach general availability release status with support from Microsoft. Please provide feedback to help us improve. We are planning to publish a more detailed Office 365 Network Onboarding guide as part of this tool which is customized for the organization by its test results.
The Office 365 service front door is an entry point on Microsoft's global network where Office clients and services terminate their network connection. For an optimal network connection to Office 365, it is recommended that your network connection is terminated into the closest Office 365 front door in your city or metro.
Note: Office 365 service front door has no direct relationship to the “Azure Front Door Service” product available in the Azure marketplace.
An optimal Office 365 service front door is one that is closest to your network egress, generally in your city or metro area. Use the Office 365 network performance tool to determine location of your in-use Office 365 service front door and optimal service front door. If the tool determines your in-use front door is optimal, then you are optimally connecting into Microsoft's global network.
The internet egress Location is the location where your network traffic exits your enterprise network and connects to the Internet. This is also identified as the location where you have a Network Address Translation (NAT) device and usually where you connect with an Internet Service Provider (ISP). If you see a long distance between your location and your internet egress Location, then this may identify a significant WAN backhaul.