Microsoft Teams alerts

Microsoft Teams alerts for M365-native ops

Send incident alerts as Adaptive Cards to any Teams channel via Incoming Webhook. Priority-tinted header, structured body and timestamp — zero Azure AD app registration for v1.

Start free Browse integrations
Latency
~3 s
Per message
Free
Reach
Teams channel

Live preview

DEMO
Engineering / oncall · WardenPoint
CRITICAL · Production

Checkout p99 latency above SLO for 5 minutes (service=checkout)

2026-05-22 13:42 UTC

When to pick this

When your team lives in Microsoft 365

Enterprise teams on M365 already get Teams everywhere. Incoming Webhook + Adaptive Card is the lowest-friction way to put alerts in front of them.

M365 enterprise

Default ops chat

Mid-market and enterprise teams default to Teams. Webhook setup happens via the channel context menu — no admin approval cycle.

Adaptive Card

Structured layout

Teams renders Adaptive Cards natively — priority banner, message body, timestamp footer. Reads cleanly on desktop, web and mobile clients.

Per-channel

One webhook per channel

Each Teams channel gets its own webhook URL. Route critical to ops, info-only to engineering all-hands.

Channel profile

What to expect

Real numbers and constraints for the Teams Incoming Webhook route.

Median latency
~3 s

WardenPoint → Teams webhook edge. Teams' webhook ingestion adds 1–3 seconds on healthy tenants.

Cost
Free

Teams Incoming Webhooks are free with any M365 plan. No per-message billing.

Delivery proof
HTTP 200

We log Teams' HTTP response (200 OK or the error body). Interactive ack via Adaptive Card actions = Phase B.

Constraint
Workflow OR Connector webhooks

Microsoft is migrating legacy O365 connector webhooks to Power Automate workflow webhooks. WardenPoint accepts both URL shapes.

Setup

Three steps to first Teams alert

Create an Incoming Webhook in the Teams channel, paste the URL in WardenPoint, send a test.

  1. 1Step 1

    Create the Incoming Webhook in Teams

    Teams channel → Manage channel → Connectors → Configure 'Incoming Webhook' → Name it 'WardenPoint' → copy the generated URL. For modern tenants use 'Workflows' app instead with the 'Post to a channel when a webhook request is received' template.

    $ https://prod-xx.westus.logic.azure.com:443/workflows/…
  2. 2Step 2

    Add a Teams recipient in WardenPoint

    Recipients → Add → Microsoft Teams. Paste the webhook URL as the recipient value. Set is_active = true.

    $ Dashboard › Recipients › + Microsoft Teams
  3. 3Step 3

    Send a test alert

    Dashboard → Send test → Microsoft Teams. The Adaptive Card lands in the channel with priority-tinted header.

    $ Send test → Microsoft Teams

Frequently asked

Common Microsoft Teams questions

No for v1 — Incoming Webhooks need no AAD app. Phase B adds optional Bot Framework registration for two-way ack via Adaptive Card actions, but the webhook flow remains the default zero-config path.
Free plan

Wire your first Teams alert in three minutes

Paste a Teams webhook URL, send a test — watch an Adaptive Card land in your ops channel. No admin approval needed.

Start free Browse integrations
  • Zero Azure AD setup
  • Adaptive Card layout
  • M365-native delivery