Using Teams with multiple organizations

GraniteStateColin Preaching to the choir mate 😉 I am a member (guest user) in multi tenants so understand your posts. Simply adding that organizations don't always have to add people as guests (B2B) for proper collaboration. I don't work for Microsoft but at least they are trying to do something about it and "second half of 2022" isn't that far away, even though it seems that this specific feature probably would rollout at the end of the year.

ChristianJBergstrom, that link is a good sign. It looks like I had posted a comment in there a few months ago, but had lost track of it, so THANKS! However, the text of your reply seems to again completely miss the point. You're looking at this from the point of view of an IT admin managing your tenant and figuring out how you can get access to people. That's the wrong perspective and the reason you're missing the point.

Here's the most common scenario driving the tens of thousands of requests for MS to fix this: you work with 2 (or more) completely unrelated companies. They each add you with a full user account to their tenant, because that's their standard practice for their people. Maybe one or both makes you owner of a few teams in their tenant or even sets you as an admin and expects you to create your own Teams as you need them (e.g., I need to create a new cross-functional team in Teams for each major project I run). Cross-tenant access is not an option. That would require the IT admin to do something special. If I'm a contractor, I would NEVER ask my client to trust my account from another client, nor would I ask them to add my personal email address to their Teams access grants. Those both draw negative attention and undermine my value as a contractor.

In my case, I'm an admin in Teams at multiple tenants. In all cases, they would never do this for me if my email domain differed from the tenant domain name. In one I'm a global SharePoint Owner, in another I'm just given access to create new Teams, but can't change settings for other users. 

Further, take these 2 situations that have no other solution as far as I know:

1. Integration with Outlook Calendar for sending Meeting invites with a working "Join Now" button in the Outlook calendar. Currently, it's only possible to schedule a Teams meeting from Outlook for the Tenant currently signed-in to Teams. That's terrible. I need to be able to schedule Teams meetings from Outlook across multiple tenants.

2. Teams VoIP. Telephone calling from Teams ("Calls" in the left navigation in Teams) works great to place a call by clicking on a phone number anywhere in Windows. Fantastic feature and one of dozens of examples why Teams is in a class by itself compared to limited systems like Slack and Google's meager offerings. But as with #1, this currently ONLY works with the currently single signed-in Team. In my case, I only have Teams telephone calling active in 1 tenant, which means that if that tenant is not the active tenant in Desktop Teams (because I needed to sign out and sign in to a different tenant for all the reasons we've been reviewing here), then all telephone links are effectively broken, just reporting "Sorry, we couldn't connect you." and another message, "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."

GraniteStateColin Work in progress https://feedbackportal.microsoft.com/feedback/idea/d256e0f6-262e-ec11-b6e6-00224827bbc2

It’s not always necessary to be a guest user in another tenant, and then cross-tenant access settings (direct connect/shared channels) are perfect. No need to switch organizations while having access to every shared channel with posts, notifications, files, apps etc.

ChristianJBergstrom, I know you're just another user trying to help, so thank you. I also think some of the comments here bashing Teams' functionality are absurd -- functionally Teams is light years beyond Slack or any other group collaboration platform.  It is without peer in terms of what it does. Slack and Google's offerings are to Teams as a bi-plane is to an Apollo lunar mission rocket. 

However, Teams is IMPOSSIBLE to use in the very specific situation (and widely requested) where a user needs to be able to join multiple tenants at the same time. This is the only way to receive live notifications of posts and chats, which, from my perspective, is a critical component of a collaboration platform -- real-time communication. Signing into other tenants via the web interface is the only real work-around, and this does give access to as many tenants as you want all at the same time. However, there are no Taskbar notifications for chats/posts in the browser. Even if you install the Teams page as an app, there are still no Taskbar notifications. If you're looking at your screen and running it in Edge, you will get the browser notice, but if you happen to not be looking at your monitor during the few seconds that alert appears, you'll only know there was a notice if you look at the browser's Teams window (or the Windows Notification history), which again destroys the entire point of live/real-time communication. It effectively makes Teams chat no better than asynchronous email.

So, ideally, Microsoft should enable multiple simultaneous access to multiple tenants, just like Outlook allows for connecting to multiple Exchange Servers. If they can't all be live in the same window, fine. Then allow multiple copies of Teams to run at the same team, each its own Tenant, sandboxed and isolated from each other for security. That should be a simple-to-implement solution (unless Electron makes that impossible -- in which case Teams should never have been built in Electron). 

But if MS can't do any of that, then fix the limitation between Edge and Windows so that browser-installed apps can have a badge count in the Taskbar. If I could see the red circled number indicating new activity in the Taskbar, I'd be OK with the browser version as the work-around. It's still not as good as the desktop app for large meetings with lots of people on video, and doesn't have the same Settings for communication device management, but for the most part, the web experience is very close to the desktop app's, minus the notification badge in Taskbar. 

Do you know if Microsoft even understands the need and the problem? My concern from reading through this entire thread is that Microsoft and others are not even trying to understand the problem. Or maybe MS is only talking with IT admins and not users -- of course many IT admins don't care about this, because they are responsible for their solo tenant. This is a problem that affects users and contractors (or board members who serve on the boards of multiple companies) who need to join multiple tenants for unrelated clients at the same time. I appreciate offering work-arounds as better than nothing, but it would also be good to hear someone acknowledge the pain and give us some confidence that MS is trying to take that pain away.

I really don't understand why this is so hard for Microsoft to understand why someone would need to or want to log into multiple organizations at a time with each teams client.

Being a consultant, I have to log into multiple slacks, multiple ad/teams/domain environments, gsuites, and others in between to function and survive.  It's like no one at microsoft has worked with 2 customers or more at a time to live in multiple worlds with the thick client.  I can't run multiple profile/org instances, nor switch accounts in one, but absolutely need either/both, and hack around it by running different windows desktop vms, which is terrible.  I can only manage this otherwise today with different browser instances via web browsers, but this is iffy too with teams chat on web (it still seems to hate linux as a host os).

I do multiple orgs with slack before microsoft started giving teams away, and never imagined it would have *not* been a thing to do this already until customer orgs of mine started defaulting to using o365, and still microsoft doesn't get this simple use case to support this.  Consultants and others that require participating in multiple org teams chats need to connect to them all, all the time - this is what we are requesting.

The mobile app does it.  Your competitors do it.  Why is this still not a thing with the thick client of teams?

Thanks for the update, ChristianJBergstrom, however, this still does not solve the original problem where you need to be signed in to multiple tenancies at the same time.

ChristianJBergstrom  thanks - so if I have received a Teams invitation as a Guest it is likely that this has not been set up correctly as a channel?