Integration

Incident alerts in Microsoft Teams

Post confirmed outages into the Teams channel IT already uses — without asking them to install Slack.

See pricing Setup docs

The message

What lands in Microsoft Teams

Open, ack, and resolve — not a one-line “site down” with nowhere to go.

Event

What the room sees

Who should ack

Open

A Workflow / Adaptive Card with the monitor, timing, and a link into Tallwatch. Built for a channel that already has too many bots.

The ops or IT owner of that channel — not the whole org Team. Put the card in a dedicated incidents channel.

Ack

Follow-up that someone claimed it. Ack still happens in Tallwatch (or your pager via webhook), not as a Teams emoji.

Whoever is on the rotation. Teams is the broadcast; the ack UI is elsewhere.

Resolve

A recover card so the channel does not stay red in the sidebar all afternoon.

Nobody in Teams. Close the loop in the tool that owns the incident.

Use this when

Why Microsoft Teams

The company standardized on Teams. IT already has an incoming webhook or Workflow. You need the outage in that channel without a Slack migration.

Not instead of

What this channel is not

Teams is not a pager. If the rotation lives in Rootly or similar, post here as broadcast and let the pager page. Do not make the all-company Team the on-call.

Setup

Connect Microsoft Teams

High-level steps — confirm the latest details in docs before you rely on it overnight.

Create an incoming webhook for a dedicated incidents channel (Workflows / Adaptive Cards — see docs).
Add a Microsoft Teams channel in Tallwatch with that URL.
Bind it to monitors or as a broadcast step beside the real pager.
Send a test and confirm the card is readable in the desktop and mobile clients you actually use.

FAQ

Microsoft Teams alerts, answered

Teams setup, plan coverage, and when to pair it with email or a webhook into your pager.

Other channels

Not this one?

Slack

The channel you already have open. On Free.

Webhooks

You want the JSON, not another chat app.

Email

Works at signup. Slow. Still the backup everyone forgets to add.

Teams is on Pro — email works without IT tickets

Start on Free with email and Slack. Add Teams when that is the room procurement already blessed.

See pricing Read the docs

Agent

Page as markdown

Raw agent-readable copy for this route. Copy it into a model, or browse the site-wide agent index at /llms.txt.

---
title: "Microsoft Teams"
description: "Route Tallwatch outage alerts into Microsoft Teams after multi-region consensus. Paid plans."
canonical: https://tallwatch.com/integrations/microsoft-teams
url: https://tallwatch.com/integrations/microsoft-teams
llms_url: https://tallwatch.com/llms.txt
updated: 2026-09-04
---
Integration

# Incident alerts in Microsoft Teams

Post confirmed outages into the Teams channel IT already uses — without asking them to install Slack.

[See pricing](https://tallwatch.com/pricing) · [Setup docs](https://docs.tallwatch.com/alerts/microsoft-teams)

## What lands in Microsoft Teams

| Event | What the room sees | Who should ack |
| --- | --- | --- |
| Open | A Workflow / Adaptive Card with the monitor, timing, and a link into Tallwatch. Built for a channel that already has too many bots. | The ops or IT owner of that channel — not the whole org Team. Put the card in a dedicated incidents channel. |
| Ack | Follow-up that someone claimed it. Ack still happens in Tallwatch (or your pager via webhook), not as a Teams emoji. | Whoever is on the rotation. Teams is the broadcast; the ack UI is elsewhere. |
| Resolve | A recover card so the channel does not stay red in the sidebar all afternoon. | Nobody in Teams. Close the loop in the tool that owns the incident. |

Use this when
## Why Microsoft Teams

The company standardized on Teams. IT already has an incoming webhook or Workflow. You need the outage in that channel without a Slack migration.

Not instead of
## What this channel is not

Teams is not a pager. If the rotation lives in Rootly or similar, post here as broadcast and let the pager page. Do not make the all-company Team the on-call.

Setup
## Connect Microsoft Teams

High-level steps — confirm the latest details in docs before you rely on it overnight.

1. **Step 1** — Create an incoming webhook for a dedicated incidents channel (Workflows / Adaptive Cards — see docs).

2. **Step 2** — Add a Microsoft Teams channel in Tallwatch with that URL.

3. **Step 3** — Bind it to monitors or as a broadcast step beside the real pager.

4. **Step 4** — Send a test and confirm the card is readable in the desktop and mobile clients you actually use.

## Microsoft Teams alerts, answered

Teams setup, plan coverage, and when to pair it with email or a webhook into your pager.

### Does Tallwatch need a Teams app store install?

No. You connect with a Teams incoming webhook / Workflow URL. Current steps are in the Microsoft Teams alert docs.

### Is Microsoft Teams on Free?

No. Free includes email and Slack. Teams is on Pro and Business.

### Can Teams be the only on-call channel?

Only if someone in that channel owns the acknowledge. Many IT orgs still keep email or a webhook into their pager as a later step.

## Teams is on Pro — email works without IT tickets

Start on Free with email and Slack. Add Teams when that is the room procurement already blessed.

[See pricing](https://tallwatch.com/pricing) · [Read the docs](https://docs.tallwatch.com/alerts/microsoft-teams)