Comment by simfree
5 days ago
Teams is shovelware. Force bundled, with questionably reliable messaging, okay video calling (if your organization policies don't break it), and a fairly useless Phone System component that misbehaves often.
Great for organizations that believe these forms of communication should be an afterthought that has rough edges and inconsistent reliability.
The recent changes to end webhook support, kill Linux desktop support and do yet another rewrite are inane. Don't expect features you use today in Teams to work in 2 years...
My org went all in on Teams over 6 years ago. Removed all PBX systems and desk phones. Pulled out Cisco phones from 20 offices. Ported all numbers to MS. By all accounts it was unremarkable to the end users, and when WFH mandates started it was seamless. Definitely a lot less IT support for configuring and troubleshooting a phone system too. There is far less downtime because Teams will ring through to your cell phone if the office internet is down or your laptop is off. That was not possible when the Cisco routers and CallManager in the office were running the DIDs and local extensions
> That was not possible when the Cisco routers and CallManager in the office were running the DIDs and local extensions
You could do it with other software hosted outside the office though. There are definitely options here.
yeah, thats why people just use Teams
It was, in fact, even with existing Microsoft products (Lync/Skype for Business). It was even possible if you had paid for those features for UCM from Cisco. Teams was simply the cheaper option (although they tried to keep charging my org Lync prices, and we had to threaten to uproot MS products and go to Cisco before they gave us the new pricing).
[flagged]
> The main problem now is that it works fine
Except from:
* notifications for channels
* search
* using more than one org (needs app restart!) although screen sharing between 'classic' and 'web' editions works only if sender's and receiver's graphic cards share a hw-accelerated video format blessed by teams. Not, it's not easy to check what edition you are running and you can't change it without poking js variables by hand
* inconsistent read statuses between devices
* 'incoming call not shown at all' bug (but you get a missed call notification)
* can't join two video calls even in two separate windows
* random audio device switching on every morning (even if you don't close the app and computer for the night)
It's fine. Messages sometimes fail to appear unless you navigate away and back and sometimes they fail to appear at all until 30 minutes later but it's fine. This regularly slows down communication and costs company time, but it's fine. It's 2026, classrooms full of children can vibe code a chat app but a $3T company struggles with basic chat functionality. It's fine.
Whatever. I've been using it since day one and its still a broken turd. People are just used to shit software, restarting, rebooting, missing calls, missing messages. Sure you can make it work, but you can't deny its a real piece of shit.
still no way to check your email from teams though.
3 replies →
Maybe in 2020. Teams is the defacto IM app for enterprise now. It may not be to your liking, but most workplaces don't need apps to constantly be adding new features. They need videoconferencing, chat, meeting recording and AI transcription and note-taking. All synced with everyone's Outlook calendars and authenticated by the same SSO used org-wide. Teams has had all of those for years.
> Teams is the defacto IM app for enterprise now.
Slack has more mindshare
For the 1000+ headcount companies who sit outside the Silicon Valley webdev/software dev world, it doesn't. Silicon Valley looks at these as "products". Purchasing managers see these as "commodities" that need to be interoperable with the rest of their stack first.
Only because they use Office and Teams is bundled, everyone using it that's heard of Slack wants to be using Slack instead.
Honestly prefer teams over slack. Slack is good at text threads, while I'd still choose Teams for calls and meetings.
1 reply →
They're ending webhooks? Bummer. By the looks of it, they're going to introduce a more complex alternative. No, two, because why not. Why make something work when you can also make two things that work half, right?
> Great for organizations that believe these forms of communication should be an afterthought
Yeah great for in person and email companies.
Direct webhooks have been removed but you can still use webhooks to send messages to Teams using PowerAutomate.
It's messier to set and maintain but it works as intended and also you can add more things to the workflow.
If you just want a URL to send json to, the new way is awful. But if you want to have more control, now you can.
Sometimes I like the PowerAutomate way, sometimes I hate it...