Sending Alerts to Teams and Slack

What it does

Alerts can be delivered to a Microsoft Teams channel and/or a Slack channel as formatted cards: severity, the plain-language summary, and a link straight to the alert. Most retail ops teams live in one of the two, and a card in the channel gets seen faster than an inbox.

Setting up Microsoft Teams

1. In Teams, create an incoming workflow for the channel you want alerts in (Workflows → "Post to a channel when a webhook request is received"). Teams gives you a URL.
2. In Edge, open Settings → Notification defaults and paste the URL into the Microsoft Teams field.
3. Click Send test: a sample card should appear in the channel within a few seconds.
4. Save.

Setting up Slack

1. In Slack, create an incoming webhook for the target channel (via a Slack app with Incoming Webhooks enabled). Slack gives you a URL.
2. Paste it into the Slack field on the same Settings card.
3. Click Send test, confirm the card arrives, and save.

How routing works

Teams and Slack are tenant-default channels: every alert that reaches your tenant defaults goes to them. Per-rule and per-certificate overrides handle email and webhook destinations; if a rule has its own routing, it still falls through to your defaults for Teams and Slack.

Pause semantics

Pausing alert emails (Settings → Alert Emails) also pauses Teams and Slack cards. They follow email semantics because they serve the same "human reads this" purpose. Plain webhooks are never paused, so PagerDuty-style on-call integrations keep working. See Pausing Alert Emails.

Tips

• Treat the webhook URLs as secrets: anyone with the URL can post to your channel. Rotate them from the Teams/Slack side if they leak.
• If the test succeeds but real alerts don't arrive, check whether alerts are currently paused, and whether the rule that fired has notifications routed elsewhere.