-
Print
-
DarkLight
-
PDF
Microsoft Teams Scout
-
Print
-
DarkLight
-
PDF
If you want to try the beta version of the Microsoft Teams Scout, sign up here!
The Microsoft Teams Scout requires Custom Hive version 1190 or higher.
The Microsoft Teams Scout lets you test the connection to Microsoft Teams servers to ensure that users in your network are able to access Teams and have a high call quality.
For example, you can use this Scout to be alerted whenever Teams servers are unavailable from your network, or when the call quality drops below an acceptable threshold.
How it Works
The Scout sends an HTTPS request to the Teams network edge from the location running the Scout. Connection to the Teams network edge is required to use the Teams application and initiate calls.
The Scout also sends simulated call data to the Teams relay server and measures the packet loss, jitter, and latency from the location running the Scout. A good connection to the relay server is required to have a high quality Teams call.
You can configure the Scout's failure and alert conditions based on the results of these network tests.
Create a Microsoft Teams Scout
-
In the Scoutbees top bar, click Create Scout to open the Add New Scout window.
-
From the Applications tab, select Microsoft Teams as the Scout Type.
-
Select the locations (Hives) from which you want to test the connection to Teams.
-
Enter a Name for the Scout.
-
Select how often you want the Scout to test Teams using the Run Every slider.
-
Optionally, attach Labels to your Scout. Labels are key-value pairs which can be used to organize your Scouts. To learn more about labels, visit Scout Labels.
-
Optionally, click Show Additional Parameters to configure the following:
- Teams Edge Address. If you don't want to use the default edge address, then you can enter a different address. It is unlikely that you have to change this parameter.
- Teams Relay Server Address. If you don't want to use the default relay server address, then you can enter a different address. It is unlikely that you have to change this parameter.
- Successful If Packet Loss Is. Sets the maximum packet loss percentage to the Teams relay server. A higher packet loss percentage indicates a worse call quality.
- Failure Conditions. Sets the conditions that cause the Scout to return a failed test result:
All means that the Scout fails if it can't connect to the network edge AND the relay server is either unavailable or the packet loss to the relay server is greater than the allowable maximum.
HTTPS means that the Scout fails only if it can't access the network edge.
Quality means that the Scout fails only if it can't access the relay server or the packet loss to the relay server is greater than the allowable maximum.
-
Click Next: Alert Policy to set up alerts and notifications on the Scout before saving it. For more information, visit Alert Policies.
Test Results
The test results show you information about the connection to the Teams network edge, and call quality performance.
To see the results of an individual test, click View All Tests and select a Scout to see a graphical summary of its results.
To see more detailed results from individual tests runs, click View All Tests and select which metrics you want to display in the Columns picker. You can use these additional metrics to help troubleshoot a connection problem.