The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else. Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.
I use Teams every day (for work, the company basically runs on it) for chat and meetings, and I'm one of those strange people who never really have much problem with it. I can think of one occasion in perhaps the last six months when it crashed and I had to kill and restart it. Otherwise it just sits there on my laptop and does its thing. Same with Outlook etc. So, what am I doing wrong? How do I get the authentic Te…
This isn't sarcasm or anything, I really mean it. If you're somehow on Teams' happy path and it does what you expect then I'm envious, I wish I was you and I am grateful that it's helpful to you at least.
For me, though, the frustration stems from being forced to use it at work, which amplifies every quirk tenfold. Minor annoyances like duplicated groups of the same people (splitting chat histories across sessions), the "every team is a SharePoint site" bloat, and the massive resource drain (though that's easing as hardware improves) add up fast.
That is to say that they also relay all of their calls through datacenters half a continent away, so if you're close to one of those then it's fine but the further you are the more likely you are to accidentally talk over people and so on, there's no peer-to-peer, even 1:1 calls are relayed with Teams; making Google Meet and Jitsi perform "better" (though people can't explain why).
Then there's the dev-side slop: mangled code snippets in chats, meeting controls jammed at the top (pulling your eyes away from the camera), and—God help you: if you've ever tried building chatops integrations on it, you'd break down and cry. Like, real, actual office-bathroom breakdown tears.