1 vote0 comments · Public » Accessibility (keyboard navigation, reader, colors etc.) · Flag idea as inappropriate… · Admin →
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.
and to drive it home: fast tenant switching is not the ask. At all. Not one of the consolidated complaints is saying "i want to logout faster". We want to either:
1. login everywhere at once, bypassing the speed problem
2. have one login receive all information so multiple accounts aren't necessary.
Ether of those work. Faster logout/login is not the ask.
Adding fuel to the fire:
The multi-org support in Teams is fundamentally broken. If my primary account is added as a guest into a new org, I have to _switch_ orgs to talk to anyone. This is in stark contrast to simply talking freely in a B2B scenario under skype. While I completely understand org switching is needed as you attach to different SharePoint backends when navigating the actual teams ... ad-hoc chats do not need this. They simply need to be able to .. well ... chat.
I attached a sample image where I have chats going on in three orgs and my only option is to _constantly_ change orgs to even see what is being said.
Chat should be global. Never need switching. Only switch Teams/Files section of the client.
These seem like multiple fundamentally different ideas and as such it may take years before everyone sees what they want. Id suggest NOT merging these into one ask. The largest ask is one of multiple accounts. The key issue here is the _client_. The ask is simple: just let us log into multiple accounts at once, just at you can with Outlook. Build a collapsing tree view on the right so we can easily browse across accounts. No integration, no cross tenant work, no shared channels. Just let me open multiple accounts in the client.Other options that involve possible complex backbend tenant work is nice to have, and speeding logout is cool I guess... But really they miss the ask:. Log into multiple accounts in one client.
The guest/federation option in Teams is a complete failure from understanding customer needs to it's execution (even if e wanted it, it was done poorly).
All that is needed is effectively a duplication of what already exists in mail systems like Outlook or other chat systesm like Slack.
1. buisness creates an account for you (or uses an invite wizard that does this)
2. you add account to your client
3. you effectively see messages/mail from all logged in clients.
Instead, what we got is a complicated guest/federation system that is riddled with "landmines" that keep proper account use from even occuring:
1. Customer uses invite system to add a user.
2. If IT setup an account for this user, he has to be careful NOT to select this user otherwise the wong acocunt will be invited to the chanel.
3. If IT setup a mailbox and tried ot be nice and setup a forwarding rule to the invited person ... that person might still get an invite email ... that will not work.
4. But if IT setup a contact, or someone else did this setup before so said user already exists as a guest in AzureAD ... then it's OK to select that user. Good luck knowing when.
5. Then the guys accepting the invite needs to be careful. Becuase if he ever created both a Microsoft Account and has a federated account with the same email address ... then he risks opening the link under the wrong account and never being able to use Teams as you can only log into 1 at a time ... meaning full logout log in to change orgs.
6. All the above needs to be done just so that we can have .... an accelerated logout/login process with the client that doens't even amke it possilbe to see messages from mulitple orgs.
It's just an awful experience. All you needed to do was allow teams to log-into multiple accounts at once and make a light-weight user-creation process for teams (like slack does) and all of the above hoop jumping would be resolved.
PLEASE: reconsider if guest account/federation is even really nessisary for teams. All the user base wants is a simple multi-account login. Outlook does this perfectly, so we know you guys can pull it off.
This is not getting nearly enough up-votes, Im guessing because most are hoping multiple login support will fix the issue for them.
The bottom line is if you are invited as a guest to multiple organizations, chatting becomes a nightmare. In older skype like chat systems, the user could simply chat with you as long as they were federated. Under Teams, I can only chat with somone when I change into the context of their organization. Otherwise I get garbage like this attached imag.
Having to constantly switch orgs is ridiculous and pointless. I can see it for the literal teams (you're switching into their share-point backend) but for simple, ad-hoc communication it completely fails.
As we announced at Microsoft Ignite 2019 this morning, we are excited to confirm that Multi-window capabilities are coming to Microsoft Teams, and will start rolling out to the public ring early next year!
Alex & the Teams team
for additional clarity: chats should be universal, not org specific. If Im invited to another org and switch over to look at the various teams I should _still_ get chat messages, and not have to "switch back" to answer a quick message.
We’re currently working on defining a compact mode experience. I will post more details when we have more to share.
We are still considering this feature for future releases, and will continue to update the status when it changes.
In an Agile development workflow this is a critical feature.
In competing products, a channel or group chat can be made around specific stories or defects, and said channel will only live as long as the story does. This makes for an "ideal" experience as multiple people can join, discuss, and contribute on very targeted topics confidently and archiving when complete.
permanent channels discurages this behavior, and instead starts to lend it self to generalized "topics" which quickly become 100+ member messes that people stop following.
We’re pleased to confirm the Teams client for Linux will be available in preview by the end of this calendar year, enabling people who use Linux client at work or in educational institutions to collaborate with others on Teams. Users will be able to install native Linux packages in .deb and .rpm formats.
65 votes7 comments · Public » Accessibility (keyboard navigation, reader, colors etc.) · Flag idea as inappropriate… · Admin →