823 votesJoakim Atterhall supported this idea ·
The engineering team is continuing to work on adding support for multiple accounts on desktop clients. We will first launch support for 1 work/school account and 1 personal account so users can enjoy Teams for work and personal side-by-side. Windows and MacOS. Support for multiple work accounts is still being worked on and will come at a later date.
You can track status via the roadmap here: https://www.microsoft.com/microsoft-365/roadmap?searchterms=68845.
An error occurred while saving the commentJoakim Atterhall commented
As most others commenting here, I'm also a consultant that works with many customers who mostly use email and Skype4B as main channels. It's really frustrating to only have access with one account using Teams (that also drops the login after a while without telling me so I don't know if I miss anything on that account).
Imagine having Outlook and you have to login/logout with different accounts all the time to get emails from all your mailboxes. Nobody would use such an application.
And technically it shouldn't be too difficult to implement this. Just save all the logins like you do in applications like Outlook or Visual Studio, and keep the authentication tokens up-to-date.
In my current project, we would like to use Teams but we chose Slack instead, and this is one of the reasons.
Maybe this sounds a bit harsh, but this one of the first things that should be considered and implemented before releasing a tool like this, which has a really great potential. I really like that I can have my TFS boards and other connections available.
This also actually applies for all web applications. I can't be logged in to different tenants at the same time. I use Azure and O365 a lot and I always have to logout/login to get to different tenants. E.g. I would like to manage several Azure tenants at the same time, but that isn't possible. It should be pretty simple to cache all the tokens with separate keys for each tenant.