Microsoft Teams
Let visitors subscribe a Teams webhook on your status dashboard.
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. For Adaptive Card format and delivery logs, see Microsoft Teams notifications.
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:
- Paste a Teams Workflows webhook URL (from the channel's Workflows app / Power Automate).
- Enter a management email used for verification, manage links, and delivery-failure alerts.
- Select one or more components from your dashboard (grouped when component groups are enabled).
- Accept consent and terms checkboxes.
- Complete the reCAPTCHA check when the dashboard is public (SSO off).
- Click Subscribe.
Endpoints must be Workflows webhook URLs — see 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:
- The visitor submits the subscribe form.
- StatusDashboard stores a pending subscriber record and sends a verification email.
- The visitor clicks the link (
/subscribe/verify?token=…). - 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). Component selections stay unchanged. |
| Visitor (manage page) | Deselect all components and save. |
| Platform (suppression) | After repeated delivery failures (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 above |
| Admin-managed (locked) subscriptions | Admin — Microsoft Teams integrations |
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.

