Network - OneDrive & SharePoint Online Status

Monitoring Benefit
The OneDrive & SharePoint Online network status tests verify that each endpoint can be reached, and that the latency is within an acceptable range.

How do we verify the monitoring test results?
From the ENow web server, open PowerShell and measure the request:

$StartTime = $(get-date)
Invoke-WebRequest -Uri "https://admin.onedrive.com" -UseBasicParsing
Write-Output ("{0}" -f ($(get-date)-$StartTime))

The -Uri value must include the https:// scheme. Without it, Invoke-WebRequest fails with an invalid URI error rather than attempting the request.

Reference: Invoke-WebRequest examples (Microsoft Learn)

To trace the network path to the same endpoint:

tracert admin.onedrive.com

tracert takes a host name rather than a URL, so no scheme is used here.

Reference: How to use tracert to troubleshoot TCP/IP problems in Windows (Microsoft Support)

Common warning or error result(s) and potential solutions to resolve the issue(s).

Adjust the Network Latency threshold settings by opening the ENow Admin Console and selecting one of the following, depending on which probe reported the result:

• Server > Monitoring Policy > Thresholds > Microsoft 365 > Network > Microsoft 365
• Server > Monitoring Policy > Thresholds > Microsoft 365 > Network > Remote Probes
• Server > Monitoring Policy > Thresholds > Microsoft 365 > Network > ECloud-Internet

If the endpoint responds quickly when tested by hand but the dashboard still reports high latency, check which of the three paths above the alert came from — each measures from a different vantage point, and they will not agree.

Please also refer to the following for troubleshooting network issues:

• Microsoft 365 URLs and IP address ranges — SharePoint Online and OneDrive for Business (Microsoft Learn)
• Configuring a firewall that requires IP addresses rather than URLs (Microsoft Learn)
• Connection to endpoint service failed error (Microsoft Learn)