Skip to content

[Notifier][MicrosoftTeams] Add support for Workflow as MS teams O365 connectors are being deprecated. #57682

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
faizanakram99 opened this issue Jul 8, 2024 · 6 comments

Comments

@faizanakram99
Copy link
Contributor

faizanakram99 commented Jul 8, 2024

Description

image

MS teams O365 connectors are being deprecated in favour of something "Workflow". See https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

Notifier doesn't work with Workflows yet, it assumes the end point is office.outlook.com which isn't the case for workflows which is usually something like prod-XX.{region}.logic.azure.com:443/workflows/blabla

PS: I would contribute if I could get this new workflow thingy working, unfortunately I can't get it working, not even with curl.

No response

@Nathalie-Verdavoir
Copy link

Hello! I got the new workflow working with a specific adaptativeCard version in a post request with json :

{ "type":"AdaptiveCard", "attachments":[ { "contentType":"application/vnd.microsoft.card.adaptive", "contentUrl":null, "content":{ "$schema":"http://adaptivecards.io/schemas/adaptive-card.json", "type":"AdaptiveCard", "version":"1.2", "body":[ { "type": "ColumnSet", "columns": [ { "type": "Column", "items": [ { "type": "Image", "style": "person", "url": "https://as2.ftcdn.net/v2/jpg/04/76/33/39/1000_F_476333957_2BrK0tKdpmRSuzkLAb62IrzTpEPp4inf.jpg", "altText": "Topics", "size": "Large" } ], "width": "auto" }, { "type": "Column", "items": [ { "type": "TextBlock", "weight": "bolder", "text": "Topics", "wrap": true }, { "type": "TextBlock", "spacing": "none", "text": "Message", "isSubtle": true, "wrap": true } ], "width": "stretch" } ] }, { "type": "TextBlock", "text": "Logs", "wrap": true } ] } } ] }

@dpfaffenbauer
Copy link

@Nathalie-Verdavoir You are using the Notifier API to send that JSON? Or do you send it directly to the MS Teams Azure Link?

@Nathalie-Verdavoir
Copy link

Hello @dpfaffenbauer , @faizanakram99 can't get it to work properly so I was just sharing the right request to send. I only tested it via postman. I didn't try to implement it on my symfony app yet.

@carsonbot
Copy link

Hey, thanks for your report!
There has not been a lot of activity here for a while. Is this bug still relevant? Have you managed to find a workaround?

@Nathalie-Verdavoir
Copy link

Nathalie-Verdavoir commented Mar 1, 2025

Hello ! Microsoft fixed the problem ! You Just have to update the link of the connector in team Chanel params. Si Suppose that the bug is not relevant anymore.

@carsonbot carsonbot removed the Stalled label Mar 1, 2025
@xabbuh xabbuh closed this as completed Mar 1, 2025
@devnix
Copy link

devnix commented May 22, 2025

Hi @xabbuh, maybe we sould consider reopening this issue. While is true that updating the Webhook link, it seems like they are dropping support at the end of 2025 anyway:

Keep in mind the entire O365 Connectors service in Teams will be retired at the end of 2025, so consider moving your webhooks to the Workflows app within Teams to avoid conducting another migration

https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

@derrabus derrabus reopened this May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants