Microsoft Teams Scout

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

On each test run, the Scout performs two different tests of Microsoft Teams servers:

• An HTTPS request to the Teams network edge (https://teams.microsoft.com). The network edge test is successful if it returns the HTTP status code 200. A connection to the Teams network edge is required to use the Teams application and initiate calls.
• A call quality test to the Teams relay server (worldaz.tr.teams.microsoft.com) to measure the packet loss, jitter, and latency. The relay server test is successful if the packet loss is less than the percentage that you set in the Scout configuration. A lower packet loss from the relay server indicates a higher quality Teams call. The Scout first connects to the relay server using UDP over port 3478. If no packets are received using UDP, then the Scout connects using TCP over port 443.

By default, the Scout fails if either the edge test or the relay server test fails. Change the Scout fails if parameter if you want the Scout to fail only when both the edge test and relay server test fail.

Create a Microsoft Teams Scout

1. In the Scoutbees top bar, click Create Scout to open the Add New Scout window.

2. From the Applications tab, select Microsoft Teams as the Scout Type.

3. Select the locations (Hives) from which you want to test the connection to Teams.

4. Enter a Name for the Scout.

5. Select how often you want the Scout to run a test using the Run Every slider.

6. Optionally, attach Labels to your Scout. Labels are key-value pairs which can be used to organize your Scouts. Learn more about Scout Labels.

7. 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.
   • Relay server test is successful if packet loss is - Sets the required packet loss to the relay server for the relay server test to succeed. A lower packet loss percentage indicates a better call quality.
   • Scout fails if - Sets which network tests to Teams servers can cause the Scout to fail a test run. By default, the Scout fails a test run if either the edge test or the relay server test fails. Change this parameter to Edge test fails AND relay server test fails if you want the Scout to fail a test run only if both Teams server tests fail.

8. Click Next: Alert Policy to set up alerts and notifications on the Scout before saving it. See the table below for a full list of the metrics that the Scout collects. Some of those metrics can be used as conditions when configuring an alert policy. Learn more about alert policies.

Test Results

The test results show you information about the connection to the Teams network edge and relay server.

Metrics

The metrics below are saved on each Scout test run.