Step 1: Network assessment and client deployment
In order to make a problem visible, a Microsoft Teams performance monitoring is essential. So it is advisable to do a network assessment with Rimscout. This involves selecting users at representative locations within the organization that are affected by acute Microsoft Teams performance problems. Rimscout clients are distributed to these locations and installed on the users’ devices. There, they collect various connection data in the background and test the performance at these locations. The collected data is continuously transferred to the Rimscout portal, where it can be viewed and analyzed. On the one hand, this makes it possible to determine whether some PCs are performing noticeably worse than others. On the other hand, possible causes can be investigated and ruled out so that the Microsoft Teams performance can be optimized.
Step 2: Monitor bandwidth utilization
Before going into further detail with the analysis of the test results, it should be clarified at the beginning if there is enough bandwidth available. Microsoft Teams needs a relatively large bandwidth for excellent performance. For stable audio or video connections, 100 kBit or 2 MBit are required. Compared to the bandwidth required by Outlook (4-8 kBit), Microsoft Teams needs up to 200 times as much continuous load for a good performance.
Step 3: Monitor UDP traffic
The most important indicator of good Microsoft Teams performance in Rimscout is the UDP test. This test determines the latency of UDP traffic to the Teams Media Relay. As specified in Microsoft’s terms and conditions, the measured latency should ideally be less than 100 ms. If the measured values deviate, the cause of the performance problems can usually be found in the network. The causes for this are numerous, but the following steps will help you to narrow them down step by step.