Microsoft Teams
Alerts posted straight into the channel your team already watches
A plain HTTPS POST to a Teams Workflow webhook URL you paste in -- no bot to register, no tenant admin consent to request.
- One Teams Workflow webhook URL per rule, generated from the "Post card when a webhook request is received" template
- A new issue, a regression, a spike, or a missed heartbeat, each its own Adaptive Card with a button back to the issue
- Delivery runs off the ingestion hot path, same as every other channel here, so a slow or unreachable webhook never adds latency to reporting an error
A Workflow webhook URL, not a bot to install
Microsoft retired the old Office 365 Connector webhooks Teams used to use -- today's equivalent is a Workflow, built from Teams' own "Post card when a webhook request is received" template, which hands you a URL the same way Slack's "Incoming Webhooks" app does. Paste that URL into the rule's target field and delivery works immediately: no bot to add to the team, no tenant admin consent screen to get approved first.
The payload is an Adaptive Card rather than Slack's plain text message -- a bolded summary line plus a "View in ForgeOps" button when the alert links back to an issue or heartbeat -- but it shares the exact same HTTP-delivery path as Slack and the generic Webhook channel under the hood.
Teams is configured exactly the same way as every other channel here.
Never blocks on Teams being slow
Same as every other channel: notification delivery runs in a background job, kicked off after an event's already been grouped and stored, never inline in the request your app made to report the error. A slow or temporarily unreachable Teams webhook shows up as a failed delivery you can see, not a delay your users feel.
Paste the Workflow webhook URL into the same target field every channel uses.