Microsoft Teams users rally to stop webhooks retirement

Microsoft recently announced it would retire Office 365 Connectors in Microsoft Teams. The retirement, set to begin on August 15, 2024, is prompting an outcry from users who rely heavily on webhooks for their integrations and notifications. In response, users are banding together on the Microsoft Feedback portal, demanding the tech giant reconsider this decision.

As of this writing, there are over 1,400 upvotes on a 2-day-old feedback thread requesting Microsoft to stop plans to retire webhooks in Teams and replace them with Power Automate. The announcement post, made earlier this month, has also seen massive traffic from angry Microsoft Teams users who do not wish to see support for webhooks ending.

From the reactions, users aren’t exactly thrilled about the prospect of ditching their trusty webhooks, which seamlessly send notifications and updates straight into their Teams channels. The proposed alternative, Power Automate workflows, seems to have struck a sour chord, leaving many feeling like Microsoft is trying to upsell them on a service they neither need nor want.

The feedback thread reads like a scene straight out of a digital revolution. And so do several other threads on Reddit. Users are wielding their virtual pitchforks, demanding Microsoft reconsider its “webhook retirement plan.” One user laments, “It’s not just changing how to create a webhook, it also needs a format change and to move from a simple message card to adaptive card,” while another gripes, “This is a very stupid decision. The previous webhook was very convenient and simple.”

Some users have even threatened to convince their companies to abandon Office 365 licensing altogether, which would be some serious digital defiance. Meanwhile, Microsoft’s suggestion to switch to the Workflows app in Teams, part of Power Automate, isn’t winning any popularity contests. Users point out several issues with this alternative: the need for a Power Automate license, the complexity of maintaining workflows compared to the simplicity of webhooks, and concerns over security with shared credentials and access tokens.

Apparently, Power Automate workflows require a licensed user, which goes against some organizations’ security protocols. One user cleverly likened the situation to replacing text messaging with snail mail – complete with envelopes, stamps, and the agonizing wait for the mailman.

But there’s more. Microsoft, in an attempt to appease the masses, recently acknowledged user feedback…by removing a footer message from notification cards. This minor concession has left users feeling like Microsoft is dodging the real issue. “The customer feedback was don’t deprecate webhooks, not get rid of the footer message!” one user roared.

So, what’s next in the great webhook war? Will Microsoft back down and reinstate webhooks and other Office 365 connectors in Teams, or will they force users to migrate to the not-so-popular Power Automate pastures? Only time will tell, but meanwhile, Microsoft has a PR battle brewing on its hands.

In the meantime, Teams users are banding together, sharing their woes and strategizing ways to keep their webhooks alive.