If your Jira notifications stopped appearing in Microsoft Teams, you're not alone — this is one of the most recurring threads on the Atlassian Community. The short answer: it's usually one of five causes — a disconnected Teams app, a private channel (not supported by the native integration), an expired connection, webhook errors on the Microsoft side, or notification settings that were silently reset. Below are the fixes for each, plus how to decide if the native integration is the right tool at all.
Quick diagnosis: which symptom do you have?
- Notifications stopped completely — app disconnected or auth expired → Fix 1
- Never worked in this channel — private channel → Fix 2
- Intermittent — some arrive, some don't — webhook 400 errors on the Microsoft side → Fix 3
- Working but flooding the channel — no event/field filtering in the native app → Fix 4
- Need approvals or transitions only — native can't filter that finely → Fix 5
Fix 1: Reconnect the Jira Cloud app in Teams
- In Teams, right-click Jira Cloud in the left rail → Uninstall
- Search the Teams app store for Jira Cloud → Add
- Sign in with the same Atlassian account and re-authorize the site
- Re-create the channel connection: channel → ⋯ → Connectors → Jira Cloud → Configure
This resolves the majority of "stopped working" cases — the OAuth connection between Teams and Jira expires or breaks after tenant changes.
Fix 2: Move out of private channels
The native Jira Cloud for Teams app does not support private channels. If the channel is private, notifications will never arrive — and no error is shown. Options: use a standard channel, or use a connector app that supports private channels.
Fix 3: Intermittent delivery (webhook 400 errors)
Since late 2024, users report intermittent delivery caused by webhook errors on the Microsoft side. Check Teams admin center → Manage apps → Jira Cloud for blocked permissions, and re-save the connector configuration to refresh the webhook URL. If it persists, the failure is outside your control — see "When the native app isn't enough" below.
Fix 4: Stop the notification flood
The native app's filtering is coarse: project-level events, limited issue-type and field filters. If your channel is drowning, turn off comment events first (the biggest noise source), then assignee changes. If you need filtering by status transition, specific field change, or JQL — the native app can't do it.
Fix 5: Status-transition-only notifications
A top Community request: "notify ONLY when an issue moves from In Progress to Done." Not possible natively. This requires a connector with per-event, per-field configuration.
When the native app isn't enough: the Native-Plus Rule
We tell every admin the same thing: native is fine until you need any one of these five things:
- Private channel support
- Filtering by field change, transition, or JQL
- Two-way actions (comment, transition, create from Teams)
- Embedded Jira views inside Teams tabs
- Data Center support
Zero boxes ticked → keep the free native app. One or more → you need an advanced connector. That's the entire rule.
Our Advanced Microsoft Teams Connector for Jira covers all five — it's why 7,500+ organizations including Amazon, Boeing, and Siemens run our integrations, and it's SOC 2 Type II certified for the security review your IT team will ask about. Setup takes about five minutes, no code access required.
Start a free trial on the Atlassian Marketplace →
FAQ
Why did my Jira notifications in Teams suddenly stop?
Most commonly the OAuth connection expired or the Teams app was updated and lost its configuration. Reconnect via Fix 1.
Does Jira Cloud for Teams work in private channels?
No. The native app doesn't support private channels. Advanced connectors do.
Can I get Jira notifications in Teams only for specific status changes?
Not with the native app. Connector apps with per-event field filtering can do this.
Is the native Jira-Teams integration free?
Yes, and it's the right choice for basic needs — see the Native-Plus Rule above for when it stops being enough.
