How to Send OpsGenie Alerts to Microsoft Teams (and Slack Simultaneously)

OpsGenie Teams Integration — The Hidden Problem

OpsGenie does have a native Microsoft Teams integration. On that front it is different from Intercom, Freshdesk, or Linear — which have no native Teams support at all. OpsGenie's Teams integration is documented and functional.

But there is a structural problem: OpsGenie's native integrations route to one destination at a time. If you want alerts in Teams, you configure the Teams integration. If you want alerts in Slack, you configure the Slack integration. If you want both — which most on-call teams do, because engineering is on Slack and management is on Teams — you create two separate integration configurations and maintain two separate alert policy rules.

For organizations with complex routing logic (severity-based routing, on-call schedule routing, escalation routing), maintaining two parallel configurations doubles the maintenance surface. A routing rule change must be applied twice. A new channel must be added to both integrations. Policy drift between the two configurations introduces subtle gaps.

The Single-Endpoint Approach

The alternative is to treat OpsGenie's outbound notification as a single stream and fan it out at the routing layer — not within OpsGenie.

Configure a single OpsGenie notification integration pointing to SyncRivo. In SyncRivo, define routing rules: P1 and P2 alerts to Slack #incidents and Teams #engineering-ops simultaneously; P3 and P4 alerts to Slack only; escalation events (when an alert goes unacknowledged) to both platforms; resolution events to the original alert thread on both platforms.

The result: one OpsGenie configuration, one place to maintain routing logic, consistent behavior across both platforms.

Setup (15 minutes):

1. Connect your Slack workspace and Microsoft Teams tenant to SyncRivo via OAuth.
2. Create a Webhook source in SyncRivo. Copy the endpoint URL.
3. In OpsGenie, go to Settings → Integrations → Add Integration → Webhook. Paste the SyncRivo endpoint. Select "All alerts" or filter by team.
4. In SyncRivo, configure routing: map OpsGenie priority fields to Slack and Teams channels. P1/P2 → both platforms; P3/P4 → Slack only. Optionally add Webex or Google Chat destinations for NOC teams.

Alert Types Worth Routing

Alert created (P1/P2): Route to both platforms immediately. The on-call engineer will see it in Slack; the engineering manager monitoring Teams will see it simultaneously.

Alert acknowledged: Route to the originating channel thread on both platforms. Closes the "is anyone handling this?" loop without requiring cross-platform coordination.

Alert escalated: Route to both platforms with escalation context — who was notified, who did not acknowledge, what the next escalation target is. This is the event managers care about most.

Alert resolved: Route to both platforms' threads. Post-incident review participants on both platforms see the resolution without needing to check OpsGenie directly.

For organizations running post-M&A IT environments where two engineering teams use different platforms, or for enterprises with distributed NOCs, this pattern eliminates the cross-platform coordination overhead that slows incident response.

For the full routing matrix, configuration guide, and native vs. SyncRivo comparison table, see the OpsGenie Alerts in Slack & Teams integration guide.