Retirement of Office 365 connectors within Microsoft Teams

[ryanbuening]

It appears that Microsoft is retiring Office 365 connectors within Microsoft Teams.

I was wondering if this app will continue to work with the new Workflows app they are pushing users to? I noticed that there is a Power Automate template for "Post card to channel in Microsoft Teams when webhook request is received", however, I'm unsure if Seq.App.Teams would need updated to accommodate the Microsoft changes.

Or maybe there is a different/better way to handle pushing alerts to Teams from Seq that I'm unaware of? @nblumhardt

[nblumhardt]

Hi Ryan,

I checked out the linked post, I can't make a lot of sense of it. Incoming webhook connectors are so widely-used it'd be really, really strange for Microsoft to retire them with three months notice.

The docs for creating webhooks don't mention any kind of deprecation:

https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet#create-an-incoming-webhook

I'm unfortunately not the best person to answer (very little experience with Teams) so someone paying closer attention may be able to clarify this :) Cheers!

[ryanbuening]

Incoming webhook connectors are so widely-used it'd be really, really strange for Microsoft to retire them with three months notice.

Yeah, people don't seem too happy about it in the comments. 🫤

Here is what the Seq alert looks like now with the Action Required message:

[nblumhardt]

Thanks for posting the screenshot. What happens if you click "Set up workflow"? It sounds like the webhook functionality is just being moved there, in which case this app would still be the way to trigger it. Keen to help but not sure where to start at this point :-)

[ryanbuening]

@nblumhardt it looks like converting to Seq.App.Teams.AdaptiveCard (and using Workflows) might be the answer here, so I think we're good. Thanks!

Relevant issue in Seq.App.Teams.AdaptiveCard here.

[bbenouarets]

The deadline was actually extended. However, the URL of the webhooks must be updated again by December 31, 2024.

If other system administrators are having difficulties locating the affected teams:
I have written a small tool in Golang that uses the Graph API to output the affected teams.

Teams Webhook Finder

This has helped us enormously, as Microsoft does not offer its own solution for reading the affected channels and teams. We have over 350 teams in our company, which we would otherwise have had to search through manually.

I hope I could help someone here with this.

Independently of my day job, I would like to create an alternative to the native “incoming webhooks”. Maybe someone will benefit from it.