> ## Documentation Index
> Fetch the complete documentation index at: https://docs.backline.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Teams Integration

> Receive Backline notifications in Microsoft Teams

## Overview

Microsoft Teams is a messaging platform for team communication. This integration connects Backline with Microsoft Teams so Backline can post remediation updates and security notifications into a channel of your choice, and answer replies in the same thread.

## What You Can Do

With the Microsoft Teams integration, you can:

* Receive real-time remediation alerts and updates, such as when Backline opens a remediation pull request
* Get notified about security events, such as a vulnerability approaching its deadline
* Reply in the thread and get an answer from Backline

## Prerequisites

Before connecting Microsoft Teams, ensure you have:

* A Microsoft 365 organization with Microsoft Teams
* A team owner who can add apps to the team
* Access to the standard channel where you want notifications

## Adding Backline to a Team

A team owner does these steps.

<Steps>
  <Step title="Find Backline in Teams">
    In Teams, open **Apps** in the left rail and search for **Backline**.

    <Note>
      If your organization restricts which apps can be installed, a Teams administrator must first allow Backline in the [Teams admin center](https://admin.teams.microsoft.com) under **Teams apps** → **Manage apps**.
    </Note>
  </Step>

  <Step title="Add Backline to the Team">
    Click **Add**, choose the team, then click **Go**. Backline is installed for the whole team, so any of its standard channels can be picked in Backline later.

    The permissions Backline receives in that team are listed under **Permissions overview** on the app card and granted when it is added. They are what lets replies in a Backline thread reach Backline without anyone mentioning it by name, in that team only — never across your organization.
  </Step>
</Steps>

Backline offers only channels from teams it has been added to, so add it to the team that holds the channel you want Backline to post to. If you later switch to a channel in another team, add it there first.

## Connecting Microsoft Teams

<Steps>
  <Step title="Navigate to Integrations">
    In Backline, go to **Integrations** in the main menu.
  </Step>

  <Step title="Select Microsoft Teams">
    Find and click on the **Microsoft Teams** integration card.
  </Step>

  <Step title="Authorize with Microsoft">
    Click **Connect**. You'll be redirected to Microsoft to sign in and approve the requested permissions.
  </Step>

  <Step title="Return to Backline">
    Once authorized, Microsoft redirects you back to the integration page.
  </Step>

  <Step title="Configure Channel">
    In the Configuration tab, select the **Default channel** where Backline will send messages. The list shows **Team name / Channel name** for every channel Backline can reach. Save your changes; Backline tests the channel before the integration counts as connected.

    <Note>
      Only standard channels in teams the Backline app has been added to appear in the list. Private and shared channels are not offered, because Backline cannot post in them.
    </Note>
  </Step>
</Steps>

### What the Sign-in Asks For

* **Read the names of teams you are in** and **read the names of their channels** — so the channel list can show your teams and channels. Backline reads names only, never message content, through this permission.
* The permissions granted when the app was added to the team are what lets replies in a Backline thread be read, in that team only.

<Warning>
  Some organizations require an administrator to approve these permissions. Microsoft then shows **Need admin approval** during sign-in and Microsoft Teams stays disconnected in Backline. Ask a Microsoft 365 administrator to grant the permissions, then click **Connect** again.
</Warning>

## After Connection

Backline posts nothing on Save. Messages start arriving with Backline's next notification, for example when a remediation pull request is opened or a vulnerability nears its deadline.

* Messages arrive from **Backline**, not from a person's name, and the remediation's owner is mentioned by name when Backline can identify them in the team.
* Follow-ups appear underneath the first message as replies, not as new channel posts.
* Replying in that thread gets an answer in the same thread.

## Managing the Integration

### Changing Channels

To send notifications to a different channel:

1. If the channel is in another team, have a team owner add the Backline app to that team first
2. Open the Integrations page
3. Click **Configure** on the Microsoft Teams integration card
4. In the Configuration tab, select the new channel
5. Save your changes

### Testing the Connection

From the Microsoft Teams integration card, run **Test connection** at any time. If it reports that Backline could not reach Microsoft, your Microsoft sign-in has expired or was revoked. Click **Connect** again to sign in, then re-run the test.

### Disconnecting

<Steps>
  <Step title="Open Integration Menu">
    On the Integrations page, click the **three dots menu** on the Microsoft Teams integration card.
  </Step>

  <Step title="Select Disconnect">
    Click **Disconnect** and confirm.
  </Step>
</Steps>

<Warning>
  Disconnecting stops all Backline messages to Microsoft Teams and Backline stops answering replies in existing threads. Other messaging integrations keep working. The Backline app stays installed in your teams until a team owner removes it.
</Warning>

## Troubleshooting

| What you see | What it means |
| - | - |
| No channels offered when connecting | The Backline app is not added to any team you belong to. Add it, then reconnect. |
| Your team's channels are missing, but others appear | The Backline app was not added to that team. |
| A channel listed as `(default channel)` | Microsoft did not return that channel's name. It still works; it is usually the **General** channel. |
| Microsoft sign-in says **Need admin approval** and Backline stays disconnected | Your organization requires an administrator to approve the permissions above. Ask them to, then connect again. |
| **Test connection** says Backline could not reach Microsoft | Your Microsoft sign-in expired or was revoked. Connect again. |
| Messages stopped after the app was removed from a team | Removing the app removes Backline's access. Add it again, then reconnect. |