# Microsoft Teams

Let visitors subscribe a Teams webhook on your status dashboard.

Source: https://statusdashboard.com/docs/status-dashboards/subscriptions/teams

> This is a plan-gated feature. If it isn't available in your account, visit the [Billing](/docs/org-mgmt/billing) page or contact support to review your options.

This page covers the public **Subscribe** and manage flows for Microsoft Teams on your status dashboard. For endpoint URL rules, admin registration, and suppression, see [Microsoft Teams integrations](/docs/integrations/teams). For Adaptive Card format and delivery logs, see [Microsoft Teams notifications](/docs/notifications/teams).

***

## What visitors see
Microsoft Teams subscriptions let visitors register a Teams Workflows webhook URL and receive Adaptive Card updates when matching events are created or updated.

On `/subscribe`, visitors with the Teams channel effectively enabled see a **Microsoft Teams** tab where they:

1. Paste a **Teams Workflows webhook URL** (from the channel's Workflows app / Power Automate).
2. Enter a **management email** used for verification, manage links, and delivery-failure alerts.
3. Select one or more **components** from your dashboard (grouped when component groups are enabled).
4. Accept consent and terms checkboxes.
5. Complete the **reCAPTCHA** check when the dashboard is public (SSO off).
6. Click **Subscribe**.

Endpoints must be Workflows webhook URLs — see [Endpoint URL rules](/docs/integrations/teams#endpoint-url-rules) for accepted hosts and rejected connector URLs.

They must select at least one component to complete a new subscription. On public dashboards, **Subscribe** stays disabled until reCAPTCHA is completed.

Below the subscribe form, an **Already subscribed?** section lets returning managers enter their management email and click **Manage** to receive a link for updating preferences.

## Double opt-in (verification)
Teams subscriptions use **double opt-in** via the management email:

1. The visitor submits the subscribe form.
2. StatusDashboard stores a **pending** subscriber record and sends a verification email.
3. The visitor clicks the link (`/subscribe/verify?token=…`).
4. The subscription is **activated** and the visitor is redirected to a management page.

Verification links expire after **24 hours**.

## Managing preferences
After verification — or after requesting a manage link — visitors land on `/subscribe/manage?token=…` (token valid for **1 hour**). Managers can change components (deselecting all stops notifications without deleting the subscription), clear suppression after fixing a broken webhook (**Resume deliveries**), or request a new manage link later.

When a tenant admin has **paused deliveries** for this endpoint in the admin console, the manage page shows a read-only notice. Visitors cannot clear that pause from manage; they can still change component selections while paused.

Each new verification or manage-link email **revokes** any previous management link for that subscriber.

### Pausing deliveries
Teams subscriptions support pausing deliveries in a few different ways.

| Who                        | How deliveries stop                                                                                                                                            |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Tenant admin**           | **Pause deliveries** in the admin console ([Managing subscribers](/docs/integrations/teams#managing-subscribers)). Component selections stay unchanged.        |
| **Visitor (manage page)**  | Deselect all components and save.                                                                                                                              |
| **Platform (suppression)** | After repeated delivery failures ([Suppression](/docs/integrations/teams#suppression)). Use **Resume deliveries** on the manage page after fixing the webhook. |

Admin pause, an empty component selection, and suppression are independent. Clearing suppression does not resume an admin pause.

## Subscriber limits
* Each **new** unique endpoint consumes one slot at sign-up time.
* The same endpoint on a second dashboard does **not** use an additional slot.
* When the limit is reached, new endpoints are rejected; existing endpoints may still subscribe on other dashboards.

## What admins control vs. what visitors control
| Setting                                 | Controlled by                                                                         |
| --------------------------------------- | ------------------------------------------------------------------------------------- |
| Whether Teams subscriptions are offered | Plan (**integrations**) + dashboard **Subscriptions** tab toggle                      |
| Which components an endpoint watches    | Visitor (unless **admin-managed / locked**)                                           |
| Pause deliveries (integration flag)     | Tenant admin only — see [Pausing deliveries](#pausing-deliveries) above               |
| Admin-managed (locked) subscriptions    | Admin — [Microsoft Teams integrations](/docs/integrations/teams#managing-subscribers) |

## Security notes
* Teams webhook URLs contain secrets. Treat manage links like password-reset links.
* List views show a redacted endpoint display only.
* Public dashboards require reCAPTCHA on subscribe and manage-request forms; SSO-protected dashboards use the IdP session instead.