Monitoring Benefit
The Microsoft Teams 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 time a request to the endpoint:
$StartTime = $(get-date)
Invoke-WebRequest -Uri "https://teams.microsoft.com" -UseBasicParsing
Write-Output ("{0}" -f ($(get-date)-$StartTime))
Include the https:// scheme in the URI. 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 teams.microsoft.com
Reference: How to use TRACERT to troubleshoot TCP/IP problems in Windows | Microsoft Support
Common warning or error results, and potential solutions
Adjust the Network Latency threshold settings by opening the ENow Admin Console and selecting:
Server > Monitoring Policy > Thresholds > Microsoft 365 > Network > Microsoft 365
or
Server > Monitoring Policy > Thresholds > Microsoft 365 > Network > Remote Probes
or
Server > Monitoring Policy > Thresholds > Microsoft 365 > Network > ECloud-Internet
Please also refer to the following for troubleshooting network issues:
Microsoft 365 URLs and IP address ranges — Microsoft Teams | Microsoft Learn
Connection to endpoint service failed error | Microsoft Learn
Comments
0 comments
Article is closed for comments.