User Profile
PaulAndrew
MicrosoftJoined 9 years ago
User Widgets
Recent Discussions
Microsoft 365 network connectivity test tool comes to Microsoft Support and Recovery Assistant
The Microsoft Support and Recovery Assistant tool (SaRA) now includes running network connectivity testing using the Microsoft 365 network connectivity test tool. Read about SaRA here. We have documented the integration of SaRA with Microsoft 365 network connectivity test tools here. Let us know what you think of this and how your network connectivity tests are going? Regards, Paul Andrew Microsoft 365 network connectivityJust released stand-alone test client for Microsoft 365 network connectivity test tool
The Microsoft 365 network connectivity test tool has just been updated with a stand-alone EXE added for more flexibility in testing. The stand-alone EXE allows you to run the same tests without having to load the web site. This will be useful if you want to automate the tests and you can deploy the EXE to the client machines using your software distribution tools. The output of the tests is saved to a JSON file on the local hard drive rather than showing up on the web page or in the Microsoft 365 Admin Center. You can read the help and download the stand-alone EXE here: https://docs.microsoft.com/Microsoft-365/Enterprise/office-365-network-mac-perf-onboarding-tool#testing-from-the-command-line We also updated both the stand-alone EXE and the original test tool to .NET 6.0 and this means if you have run the tool from the web site before and run it again you will be prompted to update. https://connectivity.office.com Please try out the new stand-alone EXE and let us know your feedback here.Asking for help. Connectivity.office.com survey on network location office or residence
We have a survey on https://connectivity.office.comthat we would like to get some support completing. The survey asks you what type of location you are running the test from and we will also capture a few anonymous network measurements that help detect if this is a residential network or an office network. We would appreciate if you could sign-in to the tool before starting since we will rely on those survey results by priority over the anonymous ones. However, your identity information is not associated with the result. Hope you will take a lookUpdate to the Microsoft 365 Network connectivity test tool connectivity.office.com
This update includes: SharePoint service front doors now appear on the network perimeter map. These identify the city where the service front door is and not the precise location Separated the SharePoint download and the Teams call tests so that they do not run in parallel with other tests to avoid any conflictUpdated testing at connectivity.office.com published
We just updated the Microsoft 365 Network connectivity test tool. Improvements are: If a user is signed in to their tenant, we don't ask for the name of the tenant for testing since we already know it. The peer comparisons are now aligned with the M365 Admin center network connectivity view. Improving the proxy server detection we now test all Optimize and Allow category Office 365 network endpoints through the client PAC file for proxy use. This also increases the total number of tests counted in the user interface. Some more detail was added to the connectivity test failure scenarios where we can point to a specific issue causing the failure related to DNS or proxy authentication. Please continue sharing your feedback about this tool Regards, PaulOffice 365 network connectivity office hours - online edition - Wednesday Sept 23
On Wednesday September 23, 2020 the Office 365 network connectivity team participated in an office hours online call. If you are interested us setting up a future AMA type call focused on Office 365 network connectivity, please comment here.Microsoft 365 network connectivity test tool now with report sharing is released to preview
We’re excited to announce a new preview release of the Microsoft 365 network connectivity test tool at https://connectivity.office.com today. This update builds on the existing features (network connection map, 20+ network connectivity tests) and adds a connection to your Microsoft 365 tenant so you can submit your test report to your administrator in the Microsoft 365 Admin Center. The update also features a new, streamlined user interface and updated documentation. The tool shows elements detected from your network perimeter in a map: We are maintaining all the existing tests we currently run: Network backhaul distance from the user to the network egress In use Exchange Online service front door Comparative performance of Microsoft 365 customers near you Time to make a DNS request on your network Distance to your DNS recursive resolver Distance to y our proxy server if one is detected Your VPN if one is detected and evaluation of whether you are following split tunnel guidance Exchange Online service front door network latency Best Exchange Online service front doors for your location The in-use Exchange Online DNS entry SharePoint Online service front door latency SharePoint and OneDrive download speed Buffer bloat while under download load SharePoint Online service front door DNS entry Microsoft Teams media connectivity UDP Packet loss UDP latency UDP jitter TCP Connectivity tests to all required Microsoft 365 URLs Detection of any SSL break and inspect intermediary devices on Microsoft 365 URLs Traceroute details for each service front door for Exchange Online, SharePoint Online, and Microsoft Teams Documentation for the tool and each of the tests can be found here: https://docs.microsoft.com/microsoft-365/enterprise/office-365-network-mac-perf-onboarding-tool NEW: Connection to your Microsoft 365 tenant and ability to submit test reports to the Microsoft 365 Admin Center. You do not need to sign in to run the tests and see results, but if you sign in you are then able to share test reports with your administrators, your account team at Microsoft, your coworkers, and with anyone using a deep link URL. Sharing with coworkers and with a deep link URL are controlled by the tenant administrator. By default, the deep link URL sharing is disabled in connectivity.office.com but an Administrator can enable it. Coworker sharing is enabled by default for connectivity.office.com but can be disabled by an administrator. Once you have shared the report, send the other user(s) a link to https://connectivity.office.com/reports and ask them to sign-in. You can review test reports that you previously ran while signed in by selecting the Reports node. There is also a page showing the status of Microsoft’s global network and any issues impacting Microsoft 365. Tenant administrators with the Report Reader role can view the network test reports under Health -> Network Connectivity (preview).connectivity.office.com partial data outage that we're investigating
If you are using https://connectivity.office.comI wanted to let you know we are aware of a data feed outage and are investigating. The following tests are impacted: Network egress location on the map. It will always show as latitude 0, longitude 0 Distance to the network egress and a red X is shown as this is often a long way away Proxy server will not show on the map and distance to the proxy server will only work by latency DNS recursive resolver will not show on the map and distance to the DNS recursive resolver will not show Other tests are not affected and work as designed. Sorry for the inconvenience. I will update this post as soon as we have resolved the issue.Simplifying Office 365 URL publishing by FQDN deduplication for proxy servers
Office 365 publishes IP Addresses and Fully Qualified Domain Names (FQDNs) so that customers can configure firewalls and proxy servers to allow appropriate access by users. These are published to http://aka.ms/o365ipand there is a web service which makes them available along with change tracking and 30 days notice for additions at http://aka.ms/ipurlws. We publish updates at the end of each month and included in todays publishing is a new method for deduplicating FQDNs which would be already allowed by a published wildcard URL. This new method has two implications for customers: 1) There is a new change impact description in our changes web service calledRemovedDuplicateIpOrUrl. This will be included any time we remove an FQDN because it is not necessary due to it matching a wildcard URL. When you see these changes, it means that an FQDN was removed from publishing, but that the FQDN is still in use by Office 365. The FQDN is covered by a wildcard URL which is also published. For example: connectivity to *.office.com is required for Office 365. Proxy servers do not need to additional have config.office.com allowed since access to that is already permitted by the *.office.com entry. 2) There are fewer entries published now that need to be listed on a proxy server. The changes to the Office 365 worldwide instance are published here, show 52 fewer FQDN/URL entries than yesterday. Note that the changes URL shows all changes since June 28, 2020 and will show additional changes in the future. This should help simplify proxy server configuration for Office 365.
