The Horror of Microsoft Teams

The Short version

The easiest comparison I would make is to consider two other messaging clients that are perhaps more familiar- WhatsApp and Outlook.

So what are the issues?

Automatic subscription

Edit: It’s been brought to my attention that this feature is an organisation-specific setting. It’s not clear to me whether this is default behaviour or not. It was certainly the case where I used Teams.

Discoverability

Of course, nobody is interested in IM channels that don’t concern them, they are interested in those that do. It might be an obvious statement but communication mediums are about communication. It’s useful to be able to search for channels based on topics. Except you can’t with Teams, at least not in a meaningful way with default policies. It’s never really clear what the bounds are for your search, the caching is horribly slow, and a lot of stuff just isn’t available to search with or for (i’ll come back to this). Guess they really like those default channels.

Message threading

The way that messages in a channel are threaded is preposterous. Coupled with the caching issues, it is near impossible. My team gave up almost immediately in favour of a simple, single-threaded team chat. This brought its own issues but at least it was reasonably clear what was happening. Corporate channels continued to use the threaded message system so we had to use it there but it never got any easier and we never chose to switch back.

Message alerting

Anyone who has worked in a an organisation of size will have experienced alerting for inappropriate ‘noise’ events and channels. Usually you can mute or unsubscribe right? Not with Teams! Firstly you can’t mute a channel you are subscribed to. This means that if someone does @${channel_name} you will get an alert. MS have not implemented muting as a feature. Secondly, for all those automatic/admin channels, you can’t unsubscribe yourself (or at least not with the default policies). Brilliant, isn’t it? Unavoidable alerts that any idiot on any channel can annoy people with.

Central control

I suppose the above emphasis on centralised control and disempowerment of users should not come as a surprise when you look at what’s coming to Teams this summer. Horrific as these upcoming developments sound, I did not have to suffer them. I did have to suffer some related aspects though.

Policy failures

Some of the above issues were mitigated and some compounded by the (presumably default) policies, which were somewhere between brain-dead and slapstick in many cases.

Channel naming

I’ve already pointed out that it wasn’t possible for me to mute or unsubscribe from centrally managed channels. What was permitted was for any user to rename a channel. Because @here isn’t supported (you need to @{channel_name} to alert everyone on that channel, this was actually an effective method to mute all of those automated deployment alerts that the less technically proficient are so fond of, mentioning ‘deployment’. At least this was true until people started manually setting alerts for their ever_so_important message, and had to be asked not to, because people who wanted to actively ‘follow’ a channel for alerts on all messages could still do so….

Group chat participant admin

It may come with the advent of channel admins but in the meantime, if someone invites someone else to a group chat, you can’t remove them, and neither can they. You have to ask them nicely to leave, in their own sweet time. Lovely

Channel admin

similar to the above, if you set up a channel and someone, I don’t know, hooks it up to an rss feed so it is all spam, then you’re stuck. You can’t remove it or block the feed, you have to ask them nicely to do so, in their own sweet time, if you know who it was, otherwise you’re stuck… Brilliant.

Device admin

In just the same way as MS Exchange Still in 2019 expects admin on your entire device by default, just for the privilege of checking your email, so MS Teams by default demands the same. Except there’s a web interface that doesn’t- ok, so you have to use ‘Desktop view’ but you have access to almost everything- the desktop fat client is electron after all. So why do you need that admin permission again? After a year or so, my org relaxed the default device admin requirement — see below.

Unable to add outsiders

At least in my org we were not able to add outsiders to our channels or share channels with them. We had to have them invited in some way into our own organisation with an Active Directory identity (centrally requested). Of course this presumed on those people running a Teams client logged in with that identity when they would not otherwise. Not sure how this works if you are in two different orgs without federated trust but it’s a non-issue on slack where you can have your client signed into multiple organisations.

Client performance

This is abysmal and was much noted by all of my immediate colleagues. Video conferencing on a MacBook Pro would immediately peg multiple cores at 100% and max out the fans. Battery life would shrink markedly for using Teams. I realise that it’s an Electron App (on Mac) but come on… On Android there is a native Teams App which I tried for a short time. It literally halved the battery life on my phone — on a new OnePlus 6t, from 30 to 15 hours. I uninstalled it after a week. No, The Android Slack client doesn’t have a marked effect on battery life.

Caching/searching

This is awful on any platform. It’s not clear what the bounds are for any search and only a very brief history is cached locally. Everything else has to be fetched remotely so scrolling is painful and searching glacial. Woe betide you if you need to catch up on a day or two’s messages when you return from leave or you want to check your multiple threads…

No Linux client

Despite thousands of people requesting it, MS have not (yet) produced a Linux client. You can trick out the web client with a wrapper and have a near-native experience, even including video conferencing, but you can’t share your desktop with it. It’s a bit like Slack’s promising dark mode (which Teams does have, as does Slack on Android). It’s clearly not difficult, they simply don’t want to do it. In just the last week there have been rumours of this finally coming. Even if it does then the above will still stand, we will see!

In Conclusion

Microsoft Teams is the solution that nobody asked for the problem that nobody had. It is an easy sell to organisations that are Microsoft-addicted so I don’t expect it to go away. Just like those old organisations that bought SharePoint and Exchange licenses for their datacentres now moving to Azure to purchase more SharePoint and Exchange licenses (but in the cloud!), so the ones that fancy themselves or have an account rep that fancies themselves, will start using Teams. If you have not used anything different, are generally scared of new things and don’t have the ‘expertise’ (or desire to develop it) to actually understand IM clients then MS Teams is an easy sell.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Joshua Kite

Joshua Kite

Infrastructure Engineering and DevOps www.joshuamkite.co.uk @joshuamkite