Usage guide: Microsoft Teams - Stability and compliance
Introduction
This dashboard is designed to monitor and remediate issues with the 'new' Microsoft Teams client. To check the stability and compliance of MS Teams classic clients, please refer to the dedicated pack "MS Teams (classic) - Stability and compliance" and it's documentation.
This library pack will help you monitor, manage, and enhance the MS Teams experience across your landscape to ensure employees can access all their Teams functionalities and collaborate effectively without frustration. This page will guide you through the structure of the content and how it can be used.
Please keep in mind this is a guide and represents just some of the potential insight and actions you can take. There are many use cases and specific troubleshooting scenarios that you might uncover in your environment.
Ensure your library pack is properly configured by following the steps highlighted in its configuration guide
Configuration guide: MS Teams - Stability and Compliance
Pack structure
Visibility
The "MS Teams - Stability and compliance" live dashboard acts as the starting point of this library pack. It provides visibility into your Teams landscape to easily monitor and uncover any issues and/or areas of improvement.
Additional visibility into the overall health and reliability of the web and desktop client can be accessed from your Applications module using the Microsoft 365: Teams application.
Advanced troubleshooting and remediation
For more in-depth investigations, you can rely on the results of specific data-gathering remote actions.
Get Microsoft Teams Work or School client status: Retrieves the installation status of MS Teams as well as the client version and the number of months since the last update.
This data-gathering remote action is used to populate the live dashboard and should already be scheduled. You can query the results by investigating KPIs from the Live dashboard or from your own investigations.
To resolve some of the detected issues, the following remote actions can be triggered when required:
Clear Microsoft Teams Work or School cache: Closes Microsoft Teams Work or School if it is open and deletes the cache files
The "Close Microsoft Teams (short maintenance) - Invoke" campaign can be used with its RA to ask users if they agree to have MS Teams closed for maintenance.
Once the cache has been cleared, the "Close Microsoft Teams (short maintenance) - Completed" will inform the users that they can re-launch MS Teams.
Reinstall Microsoft Teams Work or School Windows: Downloads and installs the latest version of Microsoft Teams on all targeted devices
The "Reinstall Microsoft Teams - Invoke" campaign asks users if they agree to have MS Teams reinstalled for maintenance. If they agree, the remote action will close MS Teams and reinstall the application.
The "Reinstall Microsoft Teams - Completed" campagin informs users that MS Teams has been re-installed and can be restarted. It will appear after the remote action is successful.
Reinstall Microsoft Teams Work or School macOS: Downloads and installs the latest version of Microsoft Teams on all targeted devices
The "Reinstall Microsoft Teams - Invoke" campaign asks users if they agree to have MS Teams reinstalled for maintenance. If they agree, the remote action will close MS Teams and reinstall the application.
The "Reinstall Microsoft Teams - Completed" campagin informs users that MS Teams has been re-installed and can be restarted. It will appear after the remote action is successful.
Use cases
Identify areas of improvement
In the dashboard's summary tab, you can access a helicopter view of where you might have problematic areas. Based on this information, you can navigate to the respective tab to troubleshoot in more details.
The filters above the dashboard can help you focus your visibility on a specific area, device or platform type. The time picker can also be used to look at your data on more granular or longer-term time scale.
Troubleshoot compliance
Microsoft Teams is an essential tool for facilitating and improving collaboration both between employees and with third parties. As a result it is imperative that Teams is installed, and kept up-to-date, on all required devices. Devices without an up-to-date Teams client may result in an impaired digital experience and should be investigated. Devices with Teams not installed should also be investigated to ensure that this is not an oversight.
Troubleshoot Teams migration
This dashboard is designed to monitor and remediate issues with the 'new' MS Teams client. Devices still running the MS Teams classic client should be investigated to see why the Teams update process is failing. The Teams Updater section in the 'Stability and Performance' tab can be referred to for further investigation. To resolve this issue, the remote actions "Reinstall Microsoft Teams Work or School Windows" or "Reinstall Microsoft Teams Work or School macOS" can be deployed to the target devices, depending on which operating system is in use.
Troubleshoot stability and performance issues
This tab displays data from the new Microsoft Teams client only (msteams/ms-teams.exe), which excludes Microsoft Edge WebView2 component activity.
The dashboard's 'Stability and performance' tab identifies potential issues and correlates with common root causes. This information can be used to inform support teams to assist in making appropriate decisions, such as changes to the application or upgrading the affected devices.
For instance, a common culprit of stability and performance issues is application versioning. Bar charts shows potential correlations between crashes/freezes or CPU/memory performance and the outlook binary.
Trend information is displayed on line charts to help track improvements over time to see if any taken actions have been effective.
Devices with Teams Updater crashes in particular should be investigated, as they could be in a non-compliant state.
Troubleshoot connectivity issues
Microsoft Teams has become essential for facilitating and improving employee collaboration for many companies. Network connectivity issues, such as consistently high connection establishment times, or failed network connections will result in employee frustration and a loss in collaboration and productivity. The 'Connectivity' tab contains sections dedicated to these two measures, with breakdowns by binary version, entity, and the destination domain. Use of the dashboard filters to select individual regions, or location type will help you to pinpoint connection issues.
The widgets in this tab track network connections to the destination domain "*teams*.microsoft.com". A new filter for destination domain has been added, to allow a more restrictive search, if required.
A connections breakdown and network traffic section are provided to allow further investigation into network connectivity issues.
Configuration
To ensure that this dashboard and it's dependencies are configured correctly, please refer to the Configuration guide.
Last updated
