Skip to content

Commit 8dfe1c0

Browse files
Merge pull request #28129 from MicrosoftDocs/main
Publish main to live, 04/03, 11:00 AM IST
2 parents 56605fe + df643e3 commit 8dfe1c0

7 files changed

Lines changed: 38 additions & 13 deletions

File tree

microsoft-365/commerce/licenses/e3-extra-features-licenses.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ f1.keywords:
55
author: cmcatee-MSFT
66
ms.author: cmcatee
77
manager: scotv
8-
ms.reviewer: paprud, marketing
8+
ms.reviewer: sinakassaw, nicholak
99
audience: Admin
1010
ms.topic: concept-article
1111
ms.service: microsoft-365-business
@@ -17,7 +17,7 @@ ms.collection:
1717
- Adm_o365
1818
ms.custom:
1919
- commerce_licensing
20-
- empty
20+
- original owners paprud, marketing
2121
search.appverid: MET150
2222
description: "Learn about Microsoft 365 E3 and E5 Extra Features and how to assign licenses for it to your users."
2323
ms.date: 11/04/2024

microsoft-365/commerce/subscriptions/self-service-purchase-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
author: cmcatee-MSFT
77
ms.author: cmcatee
88
manager: scotv
9-
ms.reviewer: sijoshi, socheng
9+
ms.reviewer: sinakassaw, nicholak
1010
audience: Admin
1111
ms.topic: faq
1212
ms.service: microsoft-365-business
81.6 KB
Loading
42.9 KB
Loading
48 KB
Loading
87.7 KB
Loading

microsoft-365/enterprise/office-365-network-mac-perf-onboarding-tool.md

Lines changed: 35 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,13 @@ title: "Microsoft 365 network connectivity test tool"
33
ms.author: kvice
44
author: kelleyvice-msft
55
manager: scotv
6-
ms.date: 12/04/2024
6+
ms.date: 04/02/2025
77
audience: Admin
88
ms.topic: article
99
ms.service: microsoft-365-enterprise
1010
ms.subservice: network
1111
ms.localizationpriority: medium
12+
ms.reviewer: roshanp
1213
search.appverid:
1314
- MET150
1415
ms.collection:
@@ -21,12 +22,12 @@ description: "Microsoft 365 network connectivity test tool"
2122

2223
# Microsoft 365 network connectivity test tool
2324

24-
The Microsoft 365 network connectivity test tool is located at <https://connectivity.m365.cloud.microsoft>. It's an adjunct tool to the network assessment and network insights available in the Microsoft 365 admin center under the **Health | Connectivity** menu.
25+
The Microsoft 365 network connectivity test tool is located at <https://connectivity.m365.cloud.microsoft>. It's an adjunct tool to the network assessment and network insights available in the Microsoft 365 admin center under the **Health | Connectivity** menu. [https://admin.cloud.microsoft/#/networkperformance](https://admin.cloud.microsoft/#/networkperformance)
2526

2627
> [!NOTE]
27-
> This document mentions the URL (<https://connectivity.m365.cloud.microsoft>) for the Global version of this tool. For other versions, please refer to the table below for the corresponding URLs.
28+
> This document refers to the URL (<https://connectivity.m365.cloud.microsoft>), the global version of this tool. For other versions, please refer to the table below for the corresponding URLs.
2829
29-
|Feature|Global service <br /><https://connectivity.m365.cloud.microsoft>|US Government (GCC) <br /><https://connectivity.m365.cloud.microsoft>| China operated by 21Vianet <br /><https://connectivity.sovcloud.cn>|
30+
|Feature|Global service <br/><https://connectivity.m365.cloud.microsoft>|US Government (GCC) <br/><https://connectivity.m365.cloud.microsoft>| China operated by 21Vianet <br/><https://connectivity.sovcloud.cn>|
3031
|:--|:--|:--|:--|
3132
|Anonymous test||||
3233
|Print report ||||
@@ -48,27 +49,51 @@ The Microsoft 365 network connectivity test tool is located at <https://connecti
4849
> [!div class="mx-imgBorder"]
4950
> ![Connectivity test tool.](../media/m365-mac-perf/m365-mac-perf-test-tool-page.png)
5051
51-
Network insights in the Microsoft 365 Admin Center are based on regular in-product measurements for your Microsoft 365 tenant, aggregated each day. In comparison, network insights from the Microsoft 365 network connectivity test are run locally in the tool.
52+
Network insights in the Microsoft 365 admin center [https://admin.cloud.microsoft/#/networkperformance](https://admin.cloud.microsoft/#/networkperformance) are based on regular in-product measurements for your Microsoft 365 tenant, aggregated each day. In comparison, network insights from the Microsoft 365 network connectivity test tool [https://connectivity.m365.cloud.microsoft](https://connectivity.m365.cloud.microsoft/)are run locally in the tool.
5253

53-
In-product testing is limited, and running tests local to the user collects more data resulting in deeper insights. Network insights in the Microsoft 365 Admin Center show that there's a networking problem at a specific office location. The Microsoft 365 connectivity test can help to identify the root cause of that problem and provide a targeted performance improvement action.
54+
In-product testing is limited, and running tests local to the user collects more data resulting in deeper insights. Network insights in the Microsoft 365 admin center show that there's a networking problem at a specific office location. When you use the Microsoft 365 connectivity test tool at a specific office location it can help to identify the root cause of that networking problem reported in the admin center and provide a targeted performance improvement action.
5455

55-
We recommend that these insights be used together where networking quality status can be assessed for each office location in the Microsoft 365 Admin Center. More specifics can be found after deployment of testing based on the Microsoft 365 connectivity test.
56+
We recommend that these insights be used together where networking quality status can be assessed for each office location in the Microsoft 365 admin center.
57+
58+
## When should I use this tool
59+
60+
Here are some example scenarios for using the Microsoft 365 network connectivity test tool.
61+
62+
#### Scenario 1
63+
64+
A user complains about being unable to access Microsoft 365 Copilot, and you suspect WebSocket protocol may be blocked for the user. You need to quickly validate if the WebSocket connection is successful for the user. You can ask the user to go to [the network connectivity test tool](https://connectivity.m365.cloud.microsoft/) and select **Run test**. This triggers a set of basic tests including a WebSocket connection test for Copilot, and the user will find the results of the test in the details pane. If WebSocket was blocked for the user, you wouldn't see a green tick but instead a warning to show that the WebSocket connection is blocked.
65+
66+
![Connectivity test - web socket pass](media/office-365-network-mac-perf-onboarding-tool/websocketpass.jpg)
67+
68+
![Connectivity test - WSS fail](media/office-365-network-mac-perf-onboarding-tool/wssfail.jpg)
69+
70+
#### Scenario 2
71+
72+
You receive complaints from users in a branch office that they experience slow connection to Microsoft 365 services. You suspect this could be due to some recent network infrastructure changes at the branch office that results in higher network latency for the users. You can ask the users at the branch office to go to [the network connectivity test tool](https://connectivity.m365.cloud.microsoft/) and select **Run test**. This triggers a set of basic tests including tests to show the distance to network egress and network latency experienced by the user for Exchange online service. In the following screenshot you will notice that the user is based in Washington state and the network egress is in Arizona. This increases the network latency for the user and the result also shows that 33% of users in Washington state have better a network connection.
73+
74+
![Connectivity test - network egress far away](media/office-365-network-mac-perf-onboarding-tool/networkegressfaraway.jpg)
75+
76+
#### Scenario 3
77+
78+
You receive complaints from users in an office location that they experience broken page load while visiting SharePoint sites or Outlook web access or Microsoft admin center web pages. You suspect this could be due to some recent network infrastructure changes at the office location that results in blocked network connections to unified domains like `*.static.microsoft` or `*.usercontent.microsoft` domains. You can ask the users at the branch office to go to [the network connectivity test tool](https://connectivity.m365.cloud.microsoft/) and run the advanced diagnostics test by downloading and running the exe. The results will show you if there are any network connections blocked for the required Microsoft 365 domains published in the article [Microsoft 365 URLs and IP address ranges](https://aka.ms/m365endpoints).
79+
80+
![Connectivity test - unified domains blocked](media/office-365-network-mac-perf-onboarding-tool/unifieddomainsblocked.jpg)
5681

5782
## What happens at each test step
5883

5984
### Office location identification
6085

61-
When you select the *Run test* button, we show the running test page and identify the office location. You can type in your location by city, state, and country/region or choose to have it detected for you. If you detect the office location, the tool requests the latitude and longitude from the web browser and limits the accuracy to 300 meters by 300 meters before use. It's not necessary to identify the location more accurately than the building to measure network performance.
86+
When you select the **Run test** button, we show the running test page and identify the office location. You can type in your location by city, state, and country/region, or choose to have it detected for you. If you detect the office location, the tool requests the latitude and longitude from the web browser and limits the accuracy to 300 meters by 300 meters. It's not necessary to identify the location more accurately than the building to measure network performance.
6287

6388
### JavaScript tests
6489

65-
After office location identification, we run a TCP latency test in JavaScript and we request data from the service about in-use and recommended Microsoft 365 service front door servers. When these tests are completed, we show them on the map and in the details tab where they can be viewed before the next step.
90+
After office location identification, we run a TCP latency test in JavaScript and request data from the service about in-use and recommended Microsoft 365 service front door servers. When these tests are completed, we show them on the map and in the details tab where they can be viewed before the next step.
6691

6792
### Download the advanced tests client application
6893

6994
Next, we start the download of the advanced tests client application. We rely on the user to launch the client application and they must also have .NET 6.0 Runtime installed.
7095

71-
There are two parts to the Microsoft 365 network connectivity test: the web site <https://connectivity.m365.cloud.microsoft> and a downloadable Windows client application that runs advanced network connectivity tests. Most of the tests require the application to be run. It populates results back into the web page as it runs.
96+
There are two parts to the Microsoft 365 network connectivity test: the web site <https://connectivity.m365.cloud.microsoft> and a downloadable Windows client application that runs advanced network connectivity tests. Most of the tests require the application to be run, which populates results back into the web page as it runs.
7297

7398
You'll be prompted to download the advanced client test application from the web site after the web browser tests have completed. Open and run the file when prompted.
7499

0 commit comments

Comments
 (0)