Retirement of Office 365 connectors within Microsoft Teams

Teams is already chaotic for development. The documentation mixes between multiple deprecated versions already. This is just going to add to the chaos. It feels like there is no-one at Microsoft responsible for "Teams" as a product. Instead it's the bastard orphan that gets bits given and taken away as each department takes a swing at it. At this point, I would genuinely say it's the current most hated Microsoft product in daily use. And for good reason.

Love the comments under the post :) For me it means no more notifications in Teams, as our organisation policy blocks all the useful workflow features.

I miss the good old time when software was shipped in a box and developers couldn't simply remove features with a commit.

I really don&#x27;t know how you can enshitify and mess up a chat application so badly. The web version of Teams fails to even load in Firefox for unexplainable reasons.<p>The desktop app isn&#x27;t much better either - it&#x27;s slow, buggy, and the text editor absolutely blows if you&#x27;re trying to do more than write a sentence or two.

they&#x27;re pissing on us without even the courtesy of calling it rain

Well there&#x27;s definitely a lot more functionality in Power Automate:<p><a href="https:&#x2F;&#x2F;www.connectorreview.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.connectorreview.com&#x2F;</a>

Is the an EU regulation response thing? The article doesn’t mention that but I’m not very familiar with this offering so I wasn’t sure.

I guess that you will be forced to &quot;pay per use&quot; with power automate...

This angers me a bit. I use O365 connectors all the time. They&#x27;ve been very useful.<p>What is workflows? Why is that REPLACING these instead of just, you know, being available as a totally separate product that I don&#x27;t want to migrate to? Why can&#x27;t I have the software grandfathered in?<p>I hate obvious resume-driven development and products.