# Opsgenie: Major incident: Issues with Microsoft Teams notifications for Opsgenie customers

**Summary:** Opsgenie reported a major Microsoft Teams notification outage for standalone customers, starting 2026-08-27 10:26 UTC and resolved 2026-09-03 06:06 UTC (6 days 19 h); Jira Service Management Operations was unaffected. An external partner’s operational error caused the issue; partner corrective measures restored service, though customers still affected were directed to restore their integration. _(machine-written, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-08-27 10:26 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/06s5mhj7hwtn](https://stspg.io/06s5mhj7hwtn)
- [Company: Opsgenie](https://rewindex.com/company/opsgenie.md)
- Versions: before (none: first archived) → after incident\_version:284/2c1bx0zpvmws@388d847edc96
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ Issues with Microsoft Teams notifications for Opsgenie customers
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-08-27 10:26 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-09-03 06:06 UTC
```

**6. Added: Affected components**

```diff
+ EU - Outgoing Integration Flow, Outgoing Integration Flow, US - Outgoing Integration Flow
```

**7. Added: Update** (identified) · 2026-08-27 10:26 UTC

```diff
+ On August 19, 2026, we identified an issue affecting the delivery of Microsoft Teams notifications for Opsgenie standalone customers. The root cause has been identified and our teams are working with our partners to resolve this issue. This issue does not impact Jira Service Management Operations customers. We will provide the next update in 24 hours.
```

**8. Added: Update** (identified) · 2026-08-28 10:38 UTC

```diff
+ Our teams continue to work with our partners towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 72 hours or sooner if we have a material update.
```

**9. Added: Update** (identified) · 2026-08-31 10:29 UTC

```diff
+ Our teams continue to work with our partners, towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 24 hours, or sooner if there is a significant update.
```

**10. Added: Update** (identified) · 2026-09-01 10:16 UTC

```diff
+ Our teams continue to work with our partners towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 24 hours, or sooner if there is a significant update.
```

**11. Added: Update** (identified) · 2026-09-02 10:17 UTC

```diff
+ Our teams continue to work with our partners towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 24 hours, or sooner if there is a significant update.
```

**12. Added: Update** (resolved) · 2026-09-03 06:06 UTC

```diff
+ On August 19, we identified an issue affecting the delivery of Microsoft Teams notifications for Opsgenie standalone customers. The root cause was attributed to an operational error caused by our external partner, and they have taken corrective measures to restore services.  If you are still experiencing issues, please follow these steps to restore your integration: https://support.atlassian.com/opsgenie/docs/restore-the-opsgenie-microsoft-teams-v2-integration/. If you require further assistance, please reach out to Atlassian Support via support.atlassian.com/contact.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-08-27 10:26 UTC | Major incident: Issues with Microsoft Teams notifications for Opsgenie customers (this change) | outage |

All Opsgenie changes: [timeline](https://rewindex.com/company/opsgenie/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/i6e129a738a30eb · Markdown: https://rewindex.com/change/i6e129a738a30eb.md · JSON: https://rewindex.com/api/v1/changes/i6e129a738a30eb · Generated 2026-10-18T03:22:18.000Z
