[Microsoft Teams] Add Support for sending notifications through Workflows in Microsoft Teams#4234
Merged
Merged
Conversation
antonmedv
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new
ms-teams-workflowsrecipe that adds support for sending notifications through Workflows in Microsoft Teams.The existing
ms-teamsrecipe relies on the "Microsoft 365 Connectors" API which has been deprecated by Microsoft 1. (The API actually still works, eventhough Microsoft mentions in their posts that the API has been disabled)As the webhook URLs between "Microsoft 365 Connectors" and "Workflows in Teams" / "Power Automate" differ, I've opted to create a new recipe that provides an easy way for users to switch without creating a breaking change for users.
Migration is simple as changing the import and the variable.
We could also keep the names of variables and scripts the same ("teams" instead of "teams_workflows"), but that wouldn't allow using both implementations in parallel in case users would like to test both paths.
Bug fix #…?
New feature?
BC breaks?
Tests added?
Docs added?
Footnotes
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ ↩