Teams monitoring requirements
Microsoft Teams includes the following actions:
Teams Voice provides network performance and network connectivity tests using the same real-time media technology as a Microsoft Teams and Skype for Business Online client.
The tool reports on specific thresholds:
Packet Loss Rate
Round Trip Latency
Packet Reorder Ratio
Mean Opinion Score (MOS)
The results help to determine if a network connection meets the targets (further information here https://docs.microsoft.com/en-us/SkypeForBusiness/optimizing-your-network/media-quality-and-network-connectivity-performance?ui=en-US&rs=en-US&ad=US)
The addresses and ports are described here: https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_teams
These tests are performed using UDP and TCP transport protocol.
Requirements for Skype for Business Online systems are described here: https://products.office.com/en-US/office-system-requirements#subscription-plans-section
For Windows Server edition, ensure the Desktop Experience feature is enabled by entering:
For Windows N or KN versions, ensure the Media Feature pack is installed: https://www.microsoft.com/en-us/download/details.aspx?id=49919
A DNS resolution is required for “world.tr.teams.microsoft.com” (18.104.22.168) when scanning Teams Voice.
A DNS resolution is required for “global.tr.skype.com” (22.214.171.124) when scanning Skype Voice.
Microsoft Teams Advanced includes the following actions:
And new actions from GSX Gizmo version 1.9:
Create a channel
Post a message to a channel
Upload file to a channel
Download file from a channel
Search a user
Send Instant Message
Those actions require a second monitoring user in order to perform end to end scenario between 2 users (like sending an instant message for example).
As those actions are throttled by Microsoft we typically see performance or availability issues when too many robots are leveraging the same accounts. Therefore we recommend Gizmo clients to use the same Teams accounts for up to 5 Robot Managers maximum.
This limitation only applies to the new actions, therefore we have provided 2 different templates and dashboards in order for existing clients to transition.
Below is a typical scenario for an existing deployment with more than 5 Robot Managers.
At this time one “Teams Configuration” is deployed to x Robot Managers (more than 5).
After deploying the 1.9.0 version, if you wish to benefit from the additional capabilities you can start deploying the “Teams Advanced” configuration to 1 Robot. For that you will need to ensure there is a new monitoring user configured for the “Office 365 Echo User“.
The “Teams Advanced” dashboard will need to be enabled (check with your GSX contact for enabling it).
Remove the “Teams configuration” from a robot manager and deploy the “Teams Advanced configuration”. Make sure it is scanning successfully by checking the “Teams Advanced dashboard”.
Slowly replace on each robot the existing “Teams configuration” by the “Teams Advanced configuration”.
Every 5 robot managers, make sure to create a new “Teams Advanced Configuration” that leverages 2 new monitoring users. Repeat the operations until all Robot Managers are using the new “Teams Advanced configuration”.
Hide the “Teams” dashboard as the new “Teams Advanced“ dashboard can now be used
Update any dashboard leveraging the “Teams” status, so that it displays the “Teams Advanced” status (e.g. “Office 365 Operations”).
To scan Teams Advanced, you need:
Two user accounts.
Accounts should be licensed for Teams.
Accounts should belong to same tenant.
A Private team is automatically created at the first scan of a robot so the teamName parameter is optional and it is useless to set it in most cases. But if user accounts has not enough right to create private teams, it is possible to set the parameter teamName with a team that must be manually created. Used user accounts must be set as admin of this team.
Concurrency: a unique configuration (with unique two user accounts) must not be deployed onto more than 5 to 12 robots. This maximum number of allowed deployed robots by config may vary but we observed that when more than 5 Robots are deployed with the same configuration, it starts to impact some actions execution time (like the “Upload file to Channel” one).
When more than 12 Robots are deployed with the same configuration, actions execution time are even more impacted and some (429) Too Many Requests or (403) Forbidden errors often occur.
If more robots are needed to be deployed to scan Teams Advanced from many locations, then different configurations are needed using different user accounts.
To scan Teams Video, you need:
Two user accounts for a caller and a callee.
Accounts should be cloud-only (ADFS is not supported).
Account should be licensed for Teams.
Accounts should belong to same tenant.
Concurrency: a unique configuration (with unique two user accounts) must not be deployed onto more than one robot. If two robots are needed to be deployed to scan Teams Video from different locations, then two different configurations are needed.
Screen sharing (which can be configured by a parameter, false by default) does not work simultaneously with camera streaming in Teams web application.