How to Send Sentry Error Alerts to Microsoft Teams (and Slack Simultaneously)

The Alert Routing Problem

Sentry is one of the few monitoring tools that supports both Slack and Microsoft Teams as native alert destinations. This sounds like it should eliminate the configuration problem — but it doesn't, for one reason: each destination requires its own alert rule.

If you want a critical error alert to reach both your engineering Slack channel and your SRE leadership Teams channel simultaneously, you need two Sentry alert rules pointing to the same condition. When you change the alert condition — adjust the threshold, modify the filter, add a project — you update two rules, not one. Over time, the rules drift. One gets updated, the other doesn't. You discover the mismatch during an incident.

For organizations running more than a handful of alert rules, this duplication creates maintenance overhead that compounds with every new project, every new team, and every threshold tuning cycle.

The Single-Endpoint Approach

SyncRivo does not receive Sentry webhooks and does not relay messages posted by bots or apps, so it is not an alert fan-out layer. Keep Sentry's native Slack and Microsoft Teams integrations for the alerts themselves, and keep your rule conditions documented so the Slack and Teams destinations stay aligned.

Where SyncRivo helps is the human side: bridge the Slack incident channel with the Teams SRE channel, so the engineers and SRE leadership discussing an alert are in one conversation, each in their own platform.

Setup:

1. In Sentry, install the Slack and Microsoft Teams integrations (Settings → Integrations).
2. In Sentry, go to Alerts → Alert Rules. Edit an existing alert rule or create a new one.
3. In the Actions section, add the Slack and Microsoft Teams notification actions for the channels that need the alert.
4. In SyncRivo, bridge the Slack and Teams channels where the incident discussion happens. Sentry's alert posts stay native on each platform; replies and discussion between people flow both ways.

For project-level webhook events (outside of alert rules), use Settings → Integrations → Webhooks to send them to your own endpoint or a workflow tool; SyncRivo does not consume Sentry webhooks.

Routing by Severity

The power is in the routing rules. Sentry's webhook payload includes the event level (debug, info, warning, error, fatal) and the issue category (error, performance, cron). Sentry alert rules can filter on these fields, so each level can go to the right native destination:

This routing structure means your on-call team sees only what requires action. Leadership sees what requires awareness. Resolved events confirm closure without noise.

Post-M&A Considerations

For organizations that have grown through acquisition, the alert routing problem is acute. The acquired engineering team uses Slack. The parent SRE organization uses Teams. The same Sentry project needs to notify both.

Keep Sentry's native Slack and Teams integrations so each team receives the alert in its own platform. With SyncRivo, bridge the acquired team's Slack incident channel with the parent SRE organization's Teams channel, so the discussion that follows an alert happens in one conversation across both platforms.

This also applies when rolling up monitoring from multiple acquired companies into a single Sentry organization: Sentry's alert rules can differentiate by project, environment, or event type, sending the right alerts to the right team on the right platform, while SyncRivo keeps the cross-platform discussion connected.

Centralizing Your Alert Stack

If you run multiple monitoring tools — Sentry for errors, PagerDuty for on-call, Datadog for infrastructure, Grafana for dashboards — configure each tool's native Slack and Teams integrations for its alerts. SyncRivo is not an alert routing layer: it does not receive tool webhooks or relay bot and app posts. What it connects is the human conversation — when engineers on Slack and SRE leadership on Teams respond to an alert, a bridged channel keeps that discussion in one place across platforms.

For the full setup walkthrough and event routing matrix, see the Sentry Error Alerts in Slack & Teams integration guide.