# Configuration guide: MS Teams (classic) compliance

{% hint style="warning" %}
The configuration options on this page are only accessible to [administrators](https://docs.nexthink.com/platform/user-guide/administration/account-management/roles#roles-administration).

Refer to the [Usage guide: Microsoft Teams compliance](/platform/library-packs/collaboration-and-productivity-applications/workflow_-ms-teams-compliance/usage-guide-ms-teams-classic-compliance.md) to use library content as a standard user.
{% endhint %}

## **Prerequisites** <a href="#documentation-pre-requisites" id="documentation-pre-requisites"></a>

This library pack contains content from the following required [expansion products](/platform/overview/products.md):

* ​[Employee Engagement - Campaigns](/platform/user-guide/campaigns.md)​
* ​[Flow - Workflows](/platform/user-guide/workflows.md)

{% hint style="info" %}
Some of these products offer default access to their respective content and can still be used without [expansion products](/platform/overview/products.md).

To learn more about default thresholds for expansion products, [visit the extended documentation](broken://spaces/OrWF1QMMEwqZgv33QBkR).
{% endhint %}

## **Included content and dependencies** <a href="#documentation-contentanddependencies" id="documentation-contentanddependencies"></a>

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** <a href="#documentation-configurationguide" id="documentation-configurationguide"></a>

{% hint style="info" %}
Adapt these suggested configuration steps to edit and customize content according to your organizational needs.
{% endhint %}

Follow these steps to install and configure content:

* Before configuration - Install library pack content from [Nexthink Library](/platform/user-guide/nexthink-library.md)
* [Step 1 - Configure remote action(s)](#step-1-configure-remote-actions)
* [Step 2 - Edit campaigns](#documentation-step3-editcampaigns)
* [Step 3 – Schedule the workflow](#step-3-schedule-the-workflow)

### **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         | <p>Requires campaigns for user notifications:<br><code>\[CampaignId]</code>: Close Microsoft Teams - Invoke<br><code>\[OperationCompletedCampaignId]</code>: Close Microsoft Teams - Completed</p>        |
| **Set Teams Classic GPU hardware acceleration** | Workflow         | <p>Requires campaigns for user notifications: <code>\[CloseTeamsCampaignId]</code>: Close Microsoft Teams - Invoke<br><code>\[OperationCompletedCampaignId]</code>: Close Microsoft Teams - Completed</p> |

### **Step 2 - Edit campaigns** <a href="#documentation-step3-editcampaigns" id="documentation-step3-editcampaigns"></a>

1. From the main menu, navigate to the **Campaigns** > [Manage Campaigns](/platform/user-guide/campaigns/managing-campaigns.md) 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 title="Code" lineNumbers="true" %}

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

{% endcode %}

**Recurrence:** Weekly - select at least one day.

{% hint style="info" %}
**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.
{% endhint %}

***

RELATED TOPICS

* [Workflow: MS Teams (classic) compliance](/platform/library-packs/collaboration-and-productivity-applications/workflow_-ms-teams-compliance.md)
* [Usage guide: MS Teams (classic) compliance](/platform/library-packs/collaboration-and-productivity-applications/workflow_-ms-teams-compliance/usage-guide-ms-teams-classic-compliance.md)
* [Manage Workflows](/platform/user-guide/workflows/managing-workflows.md)
* [Manage Campaigns](/platform/user-guide/campaigns/managing-campaigns.md)
* [Manage Remote Actions](/platform/user-guide/remote-actions/getting-started-with-remote-actions/managing-remote-actions.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nexthink.com/platform/library-packs/collaboration-and-productivity-applications/workflow_-ms-teams-compliance/configuration-guide-ms-teams-classic-compliance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.