Live data from Hacker News

Retirement of Office 365 connectors within Microsoft Teams

devblogs.microsoft.com

1–10 of 17 posts

Re: Retirement of Office 365 connectors within Microsoft Teams

#4
This angers me a bit. I use O365 connectors all the time. They've been very useful.

What is workflows? Why is that REPLACING these instead of just, you know, being available as a totally separate product that I don't want to migrate to? Why can't I have the software grandfathered in?

I hate obvious resume-driven development and products.

Re: Retirement of Office 365 connectors within Microsoft Teams

#7
post #4

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

I can understand retiring products that duplicate functionality elsewhere—keeping systems operating, even in maintenance mode, isn't free—but the short timeframe is ridiculous.

Re: Retirement of Office 365 connectors within Microsoft Teams

#10
I really don'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.

The desktop app isn't much better either - it's slow, buggy, and the text editor absolutely blows if you're trying to do more than write a sentence or two.

Post reply on HN