Support

Configuration guide: MS Teams (classic) compliance

The configuration options on this page are only accessible to administrators.

Refer to the Usage guide: Microsoft Teams compliance to use library content as a standard user.

Prerequisites

This library pack contains content from the following required expansion products:

Some of these products offer default access to their respective content and can still be used without expansion products.

To learn more about default thresholds for expansion products, visit the extended documentation.

Included content and dependencies

This library pack contains the following content and dependencies:

Content type
Name
Description
Dependencies

Remote actions

Get Microsoft Teams Classic client status

Checks for installation, version, and other compliance data for the Teams Classic client.

Used directly in the workflow

Remote actions

Clear Microsoft Teams Classic Cache

Clears Teams cache as part of troubleshooting steps.

Used directly in the workflow

Remote actions

Set Teams Classic GPU hardware acceleration

Disables GPU acceleration in Teams Classic.

Used directly in the workflow

Campaigns

Close Microsoft Teams (short maintenance) - Invoke

Notifies users before closing Teams for cache clearance or GPU adjustments.

Used by a remote action

Campaigns

Close Microsoft Teams (short maintenance) - Completed

Confirms Teams has been closed successfully.

Used by a remote action

Workflow

MS Teams (classic) compliance

This workflow is designed to automate Microsoft Teams Classic compliance checks and remediations using Nexthink Infinity.

Configuring the MS Teams (classic) compliance pack

Adapt these suggested configuration steps to edit and customize content according to your organizational needs.

Follow these steps to install and configure content:

Step 1 - Configure remote actions

Name
Trigger schedule
Parameters to edit

Get Microsoft Teams Classic client status

Workflow

None

Clear Microsoft Teams Classic Cache

Workflow

Requires campaigns for user notifications: [CampaignId]: Close Microsoft Teams - Invoke [OperationCompletedCampaignId]: Close Microsoft Teams - Completed

Set Teams Classic GPU hardware acceleration

Workflow

Requires campaigns for user notifications: [CloseTeamsCampaignId]: Close Microsoft Teams - Invoke [OperationCompletedCampaignId]: Close Microsoft Teams - Completed

Step 2 - Edit campaigns

  1. From the main menu, navigate to the Campaigns > Manage Campaigns page.

  2. Review and edit your campaigns. For each installed campaign:

    • Customize the sender name and image.

    • Review and adjust questions.

    • Publish the campaign when you are ready to use it.

Nexthink recommends the following configurations for these campaigns:

Name
Trigger
Priority

Close Microsoft Teams (short maintenance) - Invoke

Remote action

Not urgent

Close Microsoft Teams (short maintenance) - Completed

Remote action

Not urgent

Step 3 – Schedule the workflow

This workflow was designed primarily to be run manually to ensure that client fixes can be submitted quickly. However, it can be configured to run on a schedule.

When configuring the scheduler we recommend the following settings as a baseline:

NQL:

Code
devices during past 7d
| where operating_system.platform == Windows
 and operating_system.name !in ["*server*"]

Recurrence: Weekly - select at least one day.

Please note: Once all the prerequisites and workflow are installed and configured, you can use the built-in validation feature that runs every time you save the workflow.

RELATED TOPICS

Last updated

Was this helpful?