Usage guide: MS Teams (classic) compliance

This page outlines various ways to use the pack, including use case examples.

Administrators can refer to the Configuration guide to set up and customize the installed content.

The MS Teams (classic) compliance library pack enables EUC teams to:

Ensure Microsoft Teams is installed, running the latest version, and properly configured.
Automatically fix known compliance issues such as version mismatches and GPU acceleration.
Reduce manual investigation time for L1 support teams.

Library pack uses

Jump to Use cases on this page to see relevant scenario applications.

Use the library pack content for the following purposes.

Visibility

The MS Teams (classic) compliance workflow gives IT teams visibility into the status of the Teams Classic client across all devices. This includes whether it is installed, up to date, and compliant with your organization’s configuration standards.

Predefined workflow structure and steps

The MS Teams (classic) compliance workflow is structured in these main steps:

The workflow checks for the installation and version status of the MS Teams classic client

At the start of this workflow, there is a "Get Microsoft Teams Client Status" thinklet configured to automate the retrieval of Microsoft Teams client status information using a remote action.

If the client is not installed or is outdated, the workflow will generate a ticket indicating this.
Otherwise, the workflow moves on to the next step.

The cache data is removed with the help of the 'Clear Microsoft Teams Classic cache' remote action

In the next step, the workflow uses the "Clear Microsoft Teams Classic cache" remote action to clear the cache.

When enabled, the workflow will disable GPU acceleration in the classic MS Teams client

Since the hardware GPU acceleration option is known to cause issues with the classic MS Teams client, the workflow checks to see if this setting is enabled and, if so, disables it.