If you set up Jira notifications in Teams a few years ago with an "Incoming Webhook" connector, they've stopped. Microsoft finished retiring Office 365 Connectors in Teams in May 2026, and those webhook URLs no longer deliver.
Here's what's left, and how to choose.
Option 1: Atlassian's Jira Cloud for Microsoft Teams app
Free and official. It gives each user personal notifications, and you can set up channel notifications filtered by space and event type. You can also create, update and assign work items by mentioning @Jira in a conversation.
Good fit if your filters are simple (this project, these events).
Option 2: Power Automate Workflows webhooks
Microsoft's replacement for connectors. You create a workflow in Teams that gives you a webhook URL, then point a Jira automation rule at it.
- Works in standard, private and shared channels.
- You build the message yourself. Interactive buttons need Adaptive Cards and a flow that handles the responses, and messages post as the Workflows bot or as the flow's owner, not as a named Jira bot.
- You maintain the flow and the Jira automation rule, and their limits. Each flow belongs to the person who created it, so it can break when they leave.
Good fit for a handful of simple alerts if you're comfortable with Power Automate.
Option 3: A dedicated Jira to Teams app
Apps like Advanced Microsoft Teams Connector for Jira (made by our team) are for when you need finer control:
- Channel rules with JQL, for example
priority = Highest AND component = Payments, with a live preview of matching issues. - Delivery through a bot (two-way) or a Workflows webhook (one-way), including shared channels.
- Personal notifications for things you're assigned, reported, watching or mentioned in, plus due-date reminders.
- Actions on bot cards: assign yourself, comment, log time or change status without leaving Teams.
- Delivery-failure alerts, covered in the next section.
Why notifications silently stop, and how to spot it
When channel notifications stop arriving, the cause is usually one of these:
- The bot can no longer post to the channel (the channel was deleted, the app was removed, or permissions changed).
- The webhook URL is dead or rejects requests (for example, the workflow was deleted or turned off).
- The user's personal chat with the bot is unavailable.
Whatever tool you use, check these three first. Our app now shows admins and users when a rule stops delivering, and why, instead of failing silently.
Quick decision guide
- Simple per-project alerts: the official app.
- A few custom alerts, and you know Power Automate: Workflows webhooks.
- JQL filtering, actions on cards, or many teams and channels: a dedicated app.
Did the connector retirement catch your team out? What did you move to?
Further reading: Notification destinations, Notification rule reference