Skip to content

Support Microsoft Teams Workflows (Incoming Webhook – New) for Teams notifier (deprecating legacy Office 365 connector)#13

Open
sanjay-zeidlergroup wants to merge 2 commits intokmcphillips:mainfrom
sanjay-zeidlergroup:add_support_of_teams_workflow
Open

Support Microsoft Teams Workflows (Incoming Webhook – New) for Teams notifier (deprecating legacy Office 365 connector)#13
sanjay-zeidlergroup wants to merge 2 commits intokmcphillips:mainfrom
sanjay-zeidlergroup:add_support_of_teams_workflow

Conversation

@sanjay-zeidlergroup
Copy link
Copy Markdown

Microsoft Teams is deprecating the legacy Office 365 Connector–based Incoming Webhooks on 31 December.
The current MS Teams notifier in exception_notification relies on this deprecated webhook format.

This PR updates the Teams notifier to support the new Microsoft Teams Workflows Incoming Webhook, which uses a different payload structure, ensuring notifications continue to work after the deprecation.

What Changed

  • Updated Teams notifier payload to match Workflow Incoming Webhook requirements
  • No changes to the public notifier API
  • Existing behavior preserved where possible
  • Added/updated tests for the new payload format

Reproduction / Verification

Before

  1. Configure the MS Teams notifier using the existing (legacy) webhook
  2. Trigger an exception
  3. Notifications rely on deprecated connector format

After

  1. Create a Microsoft Teams Workflow with an Incoming Webhook
  2. Configure the notifier with the new webhook URL
  3. Trigger an exception
  4. Notification is successfully delivered to the Teams channel

Tests

  • Added automated tests for Workflow webhook payload
  • All existing tests pass
  • Manually verified using a real MS Teams Workflow webhook

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant