# Microsoft Teams Integration

Source: https://docs.qualflare.com/docs/integrations/microsoft-teams · Last updated: 2026-11-02

Post Qualflare defect, launch, failure cluster, milestone and flaky test events to Microsoft Teams channels through a Workflows webhook URL.

The Qualflare Microsoft Teams integration posts a card to a Teams channel when an event you pick happens in a project; a workspace Editor connects up to 20 channels by pasting each channel's Workflows webhook URL, and each project picks one channel.

It isn't the project **Teams** feature, which groups project members: see [Project teams](https://docs.qualflare.com/docs/administration/teams).

## What the integration does

The Microsoft Teams card is under **Notifications** on the workspace **Integrations** page. The integration offers all seven events: [Defect Created](https://docs.qualflare.com/docs/integrations/events#defect-created), [Defect Resolved](https://docs.qualflare.com/docs/integrations/events#defect-resolved), [Launch Completed](https://docs.qualflare.com/docs/integrations/events#launch-completed), [Launch Failed](https://docs.qualflare.com/docs/integrations/events#launch-failed), [Cluster Created](https://docs.qualflare.com/docs/integrations/events#cluster-created), [Milestone Completed](https://docs.qualflare.com/docs/integrations/events#milestone-completed) and [Flaky Test Detected](https://docs.qualflare.com/docs/integrations/events#flaky-test-detected). Once a project is set up, Qualflare posts one card per selected event to the project's channel, in the same words as Slack ([Chat and alert messages](https://docs.qualflare.com/docs/integrations/events#chat-messages)). The integration only posts: nothing you do in Teams changes Qualflare.

## Before you begin

* You connect channels on the workspace **Integrations** page (requires the Editor role or higher in the workspace).
* You set up each project on its own **Integrations** page (requires the Editor role or higher in the project).
* You need permission to add workflows to the channel in Teams.

## Connect a channel

A workspace connects up to 20 channels, each with its own URL and a name no other channel has (ignoring case), and the URL must be an `https` Workflows URL on `logic.azure.com`, so old Office 365 connector URLs don't work.

### Step 1: Create a workflow in the Teams channel

1. In Teams, open the channel and choose **⋯ → Workflows**.
2. Pick **Post to a channel when a webhook request is received**.
3. Finish the setup and copy the URL it shows.

Copy the whole URL. Anyone who has it can post to the channel.

*Figure: The workflow gives one URL for one channel; copy all of it.*

### Step 2: Paste the URL in Qualflare

In the workspace sidebar, open **Integrations**. On the **Microsoft Teams** card, click **Install** for the first channel, or **Channels** to add another. Enter a **Name**, which is how projects see the channel, because Teams doesn't tell Qualflare its name. Paste the **Webhook URL**, then click **Connect channel**.

*Figure: Once a channel is connected, the card's Channels button adds and removes channels.*

### Step 3: Check the message in Teams

Before it saves the channel, Qualflare posts "Qualflare is now connected to this channel." to it. If it doesn't appear, "the workflow may be disabled or its creator may have left the organisation", as Qualflare's confirmation says.

## Configure a project

1. In the project sidebar, open **Integrations**. It lists only integrations enabled in the workspace.
2. Click **Configure** on Microsoft Teams (**Edit** once it is set up).
3. In **Teams channel**, pick one of the connected channels.
4. Under **Events**, select at least one event.
5. Click **Save**.

Each project posts every selected event to its one channel.

*Figure: Each project posts the events you pick to one connected channel.*

## Check deliveries

Each delivery attempt is a row in [Recent deliveries](https://docs.qualflare.com/docs/integrations/events#recent-deliveries) on the project's **Integrations** page, with Teams in the **Integration** column. **Delivered** means the workflow accepted the request. The workflow runs after that, so a **Delivered** row with no card in the channel means the workflow failed.

## Message format

Each message is an Adaptive Card with one block of text, the same text Slack and Discord post, and no buttons. Square brackets in names are escaped, so a defect or test name can't turn into a link. [Chat and alert messages](https://docs.qualflare.com/docs/integrations/events#chat-messages) gives each event's text. In **Launch Completed** cards the counts currently always read `Passed: 0, Failed: 0` (see [Launch Completed](https://docs.qualflare.com/docs/integrations/events#launch-completed)).

*Figure: The card carries the same one-line text Slack and Discord post.*

## Manage and remove channels

To remove one channel, click **Channels** on the Microsoft Teams card, then the trash button next to the channel. As the dialog says, "Removing a channel stops delivery to it. Rules pointing at it keep their other settings." A project still set to that channel then gets **Dropped** deliveries: edit the project and pick another **Teams channel**.

Removing the last channel keeps the integration and every project's settings, and nothing is delivered until you connect a channel and pick it in each project.

To remove the integration with all its channels:

> **Caution:** Removing Microsoft Teams deletes every project's Microsoft Teams settings. To use Microsoft Teams again, connect a channel and set up each project from scratch.

On the Microsoft Teams card, click the trash icon, then **Remove**. Only the person who installed it, or a workspace **Maintainer** or **Owner**, can remove it.

Removing a channel or the integration doesn't revoke anything at Microsoft. To stop the URL working, delete the workflow in the Teams channel.

## Data sent to Microsoft Teams

Qualflare sends only each event's [message text](https://docs.qualflare.com/docs/integrations/events#chat-messages) to the workflow URL you pasted, and stores that URL encrypted without ever showing it again.

## Troubleshooting

* `that does not look like a Microsoft Teams Workflows webhook URL; copy it again from the channel's Workflows setup`: copy the URL again from the workflow; it must be an `https` URL on `logic.azure.com`.
* `could not post to that channel; check the workflow still exists in Teams and copy its URL again`: the workflow was deleted or the URL is incomplete, so create the workflow again and paste its URL.
* `teams: at most 20 channels can be connected` or `teams: a channel with that name is already connected`: remove a channel you no longer use, or choose another name.
* `teams: that webhook URL is already connected`: that channel is already connected, so pick it in the project's **Teams channel**.
* **Delivered** rows but no card in the channel: the workflow failed after accepting the request, so open its run history in Teams or Power Automate.
* **Dropped** rows with `teams: the webhook is no longer available` in **Detail**, with more than one channel connected: that channel's workflow was deleted in Teams or its URL changed (the card doesn't change), so create the workflow again or copy its new URL, connect it in **Channels**, pick it in **Teams channel** in each project that used the old channel, then remove the old channel.
* **Reconnect** on the card: the workspace's only channel stopped accepting posts, so Qualflare turned the integration off and projects no longer list it; connect a working channel in **Channels**, have the person who installed it or a workspace **Maintainer** or **Owner** click **Enable** on the card, pick the new channel in each project's **Teams channel**, then remove the dead channel (the **Reconnect** badge can stay).
* "Integrations require maintainer access": you need the Editor role or higher in the workspace.

## Related

* **Guides:** [Integrations](https://docs.qualflare.com/docs/integrations) · [Slack](https://docs.qualflare.com/docs/integrations/slack)
* **Reference:** [Integration events](https://docs.qualflare.com/docs/integrations/events) · [Project teams](https://docs.qualflare.com/docs/administration/teams)
* **CLI/API:** [CI/CD integration](https://docs.qualflare.com/docs/cli/ci-cd)