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 post 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 notification logic (severity-based, on-call schedule, escalation), maintaining two parallel configurations doubles the maintenance surface. A rule change must be applied twice. A new channel must be added to both integrations. Policy drift between the two configurations introduces subtle gaps.

Running Both OpsGenie Integrations Deliberately

There is no single-endpoint shortcut through SyncRivo: it does not accept OpsGenie webhooks, does not route alerts by priority, and does not relay messages posted by bots or apps. What works is treating the two OpsGenie integrations as one policy.

Setup:

1. In OpsGenie, go to Settings → Integrations → Add Integration → Slack. Connect the workspace and map the alert filters: P1/P2 → #incidents; P3/P4 → #alerts-low.
2. Add Integration → Microsoft Teams. Connect the tenant and map the filters: P1/P2 → #engineering-ops; escalation events → #engineering-ops.
3. Give both integrations the same team and priority filters so the two audiences see the same set of alerts, and review them together after any change.
4. Optionally add OpsGenie's Webex or Google Chat integrations for NOC teams on those platforms.

Alert Types Worth Sending to Both Platforms

Alert created (P1/P2): Both platforms immediately. The on-call engineer will see it in Slack; the engineering manager monitoring Teams will see it at the same time.

Alert acknowledged: Both platforms. Closes the "is anyone handling this?" loop.

Alert escalated: 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: Both platforms. Post-incident review participants on both platforms see the resolution without needing to check OpsGenie directly.

Where SyncRivo Fits (and Where It Doesn't)

What SyncRivo bridges is the human conversation during the incident. Connect Slack #incidents to Teams #engineering-ops, and the response — the on-call engineer's "acked, looking at the database", the manager's "do we need a status page update?", the decision to page a second engineer — is visible on both platforms, in both directions, with threads, edits, files, and @mentions kept in sync. The OpsGenie alerts themselves still arrive through OpsGenie's own Slack and Teams integrations; SyncRivo does not copy them across.

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

For the OpsGenie integration setup reference, see the OpsGenie Alerts in Slack & Teams integration guide.