> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/business-systems/microsoft-teams.md).

# Microsoft Teams

Learn how to integrate Microsoft Teams with Couchdrop.

## Overview

Microsoft Teams is a collaboration platform used by teams to communicate, share information, and coordinate work through channels and chats.

Couchdrop integrates with Microsoft Teams to send workflow notifications to a selected Teams channel. This allows teams to receive updates about file transfers and automation activity directly in Microsoft Teams.

### How Microsoft Teams works with Couchdrop

Microsoft Teams is configured in Couchdrop as a system integration using an incoming webhook URL.

The webhook URL is created in Microsoft Teams and determines which channel receives messages from Couchdrop.

Unlike [Slack](/integrations/business-systems/slack.md), which uses a bot to retrieve available channels, Microsoft Teams uses a webhook URL that is linked to a specific destination.

Each Couchdrop Microsoft Teams integration supports **one Teams channel**. To send notifications to multiple channels, create a separate Microsoft Teams integration for each channel.

Couchdrop uses the Microsoft Teams integration in three places:

* **Custom Notification action:** Add a Teams notification to any branch of an Automation Workflow, including [conditional paths](/automations/conditional-filtering.md) and [failure-handling paths](/automations/error-handling.md). You can write a custom message and insert workflow variables into the message.
* **Workflow success and failure notifications:** Send a Teams notification when the entire workflow [completes successfully or fails.](/automations/notifications.md)
* **Transfer Shield approvals:** Send approval requests to a Teams channel when a [Transfer Shield Content Rule Group](/security-and-governance/transfer-shield-dlp/content-rule-groups.md) is configured with **Require Approval**. Approvers can review and complete approval requests directly within Microsoft Teams, without needing to switch to Couchdrop.

### Using Microsoft Teams for Transfer Shield approvals

Transfer Shield can send approval requests to Microsoft Teams when a file matches a Content Rule configured to require approval.

When a file requires approval, Couchdrop emails the configured approvers and sends an additional notification to the selected Microsoft Teams channel.

Approvers can complete the approval process directly within Teams. The same capability is available through the Couchdrop Slack integration.

{% hint style="info" %}
Microsoft Teams and Slack notifications supplement email approvals rather than replace them. Configured approvers will always receive an email when a file requires approval.
{% endhint %}

## Set up the Microsoft Teams integration

{% hint style="warning" %}

### Before you start

You need:

* Couchdrop administrator access
* Access to the Microsoft Teams channel where you want to receive notifications
* Permission to create a webhook workflow in Microsoft Teams

You must create the incoming webhook in Microsoft Teams before configuring the integration in Couchdrop.
{% endhint %}

{% stepper %}
{% step %}

### Create an incoming webhook in Microsoft Teams

1. Open **Microsoft Teams**.
2. Open **Workflows** from the Teams interface.
3. Search for an incoming webhook template, such as **Send webhook alerts to a channel**.
4. Select the template.
5. Choose the **Team** and **Channel** where Couchdrop should send notifications.
6. Click **Save** to create the workflow.
7. Open the newly created workflow's details and copy the generated **Webhook URL**.

This URL allows Couchdrop to send messages to the selected Microsoft Teams channel.

For more information, see [Microsoft's guide to sending messages in Teams using incoming webhooks](https://support.microsoft.com/en-us/workflows/send-messages-in-teams-using-incoming-webhooks).

{% hint style="info" %}
Each webhook is associated with its configured destination. Create a separate webhook in Microsoft Teams if you need Couchdrop notifications delivered to another channel.
{% endhint %}
{% endstep %}

{% step %}

### Connect Microsoft Teams to Couchdrop

1. Open the [Admin Panel](/administration/admin-panel-and-user-mode.md).
2. Go to **Integrations > Platforms**.
3. Click **Add Connection**.
4. Find and select **Microsoft Teams**.
5. Configure the following fields:

<table><thead><tr><th width="202.69921875">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration name</strong></td><td>Enter a descriptive name to identify the integration in Couchdrop. For example, <code>Teams - SecOps Notifications</code>.</td></tr><tr><td><strong>Teams Webhook URL</strong></td><td>Paste the incoming webhook URL generated in Microsoft Teams.</td></tr></tbody></table>

6. Click **Send Test Message** to test the webhook.
7. Check the selected Microsoft Teams channel to confirm the test message was received.
8. Click **Add System Integration** to save the integration.

{% hint style="success" %}
The integration is ready when the test message appears in the selected Microsoft Teams channel.
{% endhint %}
{% endstep %}
{% endstepper %}

## Frequently asked questions

<details>

<summary>Can I send notifications to multiple Microsoft Teams channels?</summary>

Each Microsoft Teams integration in Couchdrop uses one webhook URL associated with a single Teams channel.

To send notifications to multiple channels, create a separate incoming webhook in Microsoft Teams for each channel, then add each webhook as a separate system integration in Couchdrop.

</details>

<details>

<summary>Does Couchdrop require a Microsoft Teams bot or application installation?</summary>

No. The Microsoft Teams integration uses an incoming webhook URL rather than a bot or application installation.

You configure the webhook in Microsoft Teams and provide its URL to Couchdrop.

</details>

<details>

<summary>Can I send notifications from different branches of the same workflow?</summary>

Yes. Add a [Custom Notification action](/automations/actions/notification-actions.md) to each branch that requires a notification, including conditional branches and failure-handling paths.

Custom messages can include Automation Workflow variables to insert information from the workflow execution.

</details>

<details>

<summary>Can a workflow send both custom notifications and completion notifications?</summary>

Yes. Custom notifications run at their configured position in the workflow, while success and failure notifications report the final workflow result.

Configuring both may result in multiple notifications during a single workflow execution.

</details>

<details>

<summary>What should I do if Microsoft Teams notifications stop working?</summary>

Check the following:

1. Confirm the incoming webhook workflow still exists and is enabled in Microsoft Teams.
2. Verify that the webhook URL configured in Couchdrop matches the URL provided by Microsoft Teams.
3. Open the Microsoft Teams integration in Couchdrop and send a test message.
4. Check the destination Teams channel for the message.

If the webhook has been deleted or its URL has changed, generate a new webhook URL in Microsoft Teams and update the Couchdrop integration.

See [Microsoft's incoming webhook documentation](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=dotnet) for additional troubleshooting information.

</details>

<details>

<summary>Is the Microsoft Teams webhook URL public?</summary>

The webhook is an externally accessible HTTPS endpoint. It does not require a Couchdrop-specific login when receiving a supported webhook request.

Treat the URL as a secret. Anyone with a valid webhook URL may be able to submit messages to its configured destination, subject to the webhook's authentication settings.

Do not publish webhook URLs in documentation, support tickets, or public repositories.

</details>

<details>

<summary>Can I change the Teams channel after creating the integration?</summary>

A Couchdrop Microsoft Teams integration sends messages to the destination configured for its webhook.

To use another channel, create an incoming webhook for that channel in Microsoft Teams and configure Couchdrop to use the new URL.

</details>

<details>

<summary>Can I approve Transfer Shield requests directly from Microsoft Teams?</summary>

Yes. When a [Transfer Shield Content Rule Group](/security-and-governance/transfer-shield-dlp/content-rule-groups.md) uses **Require Approval**, you can select a Microsoft Teams integration under **Additional notifications**.

Approval requests are sent to the configured Teams channel, where approvers can complete the approval workflow directly.

Couchdrop also sends approval emails to the configured **Allowed approvers**, regardless of whether Teams notifications are enabled.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/integrations/business-systems/microsoft-teams.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
