My team has some users on Linux, and one benefit Slack has is a Linux client. Without a Linux client on Microsoft Teams, some orgs may have to turn away in favor of Slack so everyone can participate without keeping a browser open all the time.
Thank you for your feedback that helped us launch the Microsoft Teams Linux client. The client is now available for everyone to use. Please find instructions for installing and more details here: https://docs.microsoft.com/microsoftteams/get-clients#linux. Enjoy!
1878 commentsComments are closed
Mark Liederbach commented
As a member of a team of developers, I can tell you that this is very disappointing. Not much reason to keep this as our collaboration tool if we can't use a dedicated client on our primary workstations.
so disappointed!! i really need screensharing on linux
This is rather disappointing with how vested our company is within the Microsoft/Office365/Azure architecture. Tough blow to the users using Linux, we've been waiting for better support to make the full swap from legacy communication methods to Teams, however this makes the decision much easier for other methods.
If a Linux client is to not be made, can we at least get better native browser notification support? Our users constantly miss messages in our initial testing of Teams.
James Blessing commented
So, Electron builds on Linux (within certain constraints), and all you have to do is change the user agent presented in order to get it to work for voice (something that Electron allows you to do).
Sounds like someone is deliberately holding this back rather than being technically stymied.
Mario Sánchez commented
Don't worry, my company is happy to use Slack
Sincerely hope you guys work ******* the webclient then... Make it as compatible as possible with the Mac/Windows MS Teams client. PLEASE!
So much for that love Linux thing, I guess it only matters when it directly benefits Ms it counts. I think dev teams should consider this case when they adopt MS tech, especially since very little resources would have been used to create a client for Linux.
Richard Wilson commented
At the time of rejection, a linux client was the #5 request. But please, tell us more about how this has been declined due to lack of resources.
Another vote for Slack. It was here years ago, it's well-supported, it works, and it works on everything. Why would I continue to entertain anything else?
So much for that love linux thing.
Christian Hujer commented
As pointed out by Rene Greuel, it is possible to get audio and video calls in Microsoft Teams to work on Linux in Chrome and Chromium (and possibly other browsers as well). I've written a blog article about how to do it, it's actually quite simple: http://nelkinda.com/blog/microsoft-teams-on-linux/
Please share this blog article to a wide audience so that as many Linux users as possible are no longer barred from making audio and video calls in Microsoft Teams on Linux.
Obviously, it technically works! The only reason why it doesn't work actually is that Microsoft is somewhere checking the User-Agent and making the claim that it doesn't work, although it actually does. This is a lie, this is evil, this is not interoperable, this is making development teams angry, and this makes us question whether Microsoft is actually serious about loving Linux.
Bad for software development teams
Dominik Dünnebacke commented
This is sad news as the majority of our clients is Linux and we might need to reconsider Teams as collab solution.
I think this is a political decision as Linux clients will not generate revenue for Microsoft . One goal behind Office 365 / Microsoft 365 is to encourage the usage of Microsoft platforms including Windows. Yes, they do support macOS as well, but enterprises will in most cases go for the Windows platform due to cost and compatibility. Teams not being available on Linux adds to this compatibility theory.
Sean Ellis commented
The very first bit of text on the Electron website is literally "build cross-platform".
Given that the Teams client is really just a website wrapped in a Windows-flavored box, and if the website works on Linux, which you say it will Real Soon Now, then why is it impossible (or even non-trivial) to put the same website in a Linux-flavored box?
Christoph Lütjen commented
Confused… you really create a product called "teams" that's not available for all team members (in most technical teams). That makes no sense...
Sean Ellis commented
Wow. One of the stated benefits of using Electron is that it is cross-platform.
The problem you have here is that Teams is, well, a team product. If not everyone in the team can use it, then its usefulness as a central resource is greatly reduced. Even the web client doesn't work properly on Linux.
If workplaces have a mixture of platforms, then the probability of having at least one Linux user in at least one team approaches 100%, at which point you have to maintain two separate ways of doing things. (Assuming you want to talk to them, which I hope is a given.)
And if the other solution works for Linux users too, why not just maintain that one?
Andrey Ladyko commented
Audio and video calls in browser,
this issue make solve current issue,
Michael Stein commented
The point is: Your customers pay for your products - So bring them out of beta-status.
If you're not able to make a native linux client, then fix the webapp.
We payed for that!
Bring us audio, video and screensharing. If you don't know how that works, look at nextcloud or some of the others.
Adam Nicholson commented
To re-iterate many the other comments since the decline announcement, if you at least can get video calls and screen sharing working in the web client on Linux then we could live without the native client. At least do one of those things with some priority. This has been dragging on for 2 years.
But I thought Microsoft loves Linux... ? No?
Matthias Neumeister commented
If at least the Web Client would support all functions, that would be a step forward. Video and screen sharing is still not possible. Why does Google get it to work with Hangouts and Microsoft doesn't?