Treat users in your own organization but on different tenant differently than a regular guest. We should not have to add them a a Guest user in our tenant.
Have you looked into the "Connected organizations" and the use of "Access packages? https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-organization
I'm currently running through a POC to confirm this meets the orgs requirements and far easier that doing manual B2B guest invitations.
Given that most corporate collaboration environments are now O365-based, this is a key capability we need to see. Very important for mergers and divestitures.
We have various needs for separate tenancies - eg who can administer them, but need to share resources with users, like with an AD Trust. B2B at the moment feels more like B2I (individual), we really need an organisational level capability.
This would be a vital feature. I would prefer to leave tenant data where it was created rather than investigate tenant-to-tenant migration options. Creating a "tenant trust" makes more sense to enable cross tenant collaboration.
Andy S commented
We have separate tenants for staff and students which is becoming more and more of an issue.
It would be great to have the ability to specify domains that Microsoft Teams recognises as a set of users who can be added as members and not just guests.
We also find the options that owners are able to set for members is greatly more advantageous than the options that can be turned on and off for guests.
This would make it a lot easier to use guests across different tenants within the same organisation.
Angie Fletcher commented
This is definitely something we need. It is a ways away from any move to a multi-geo tenant for our organization given work that needs to be done and our continuance of acquiring companies and the process before integrating them into the company. This will allow so much collaboration that is lacking in a multi-tenant setting when there are a small # of tenants that are part of the enrolment and organization so shouldn't be seen as "external".
Rémi Drouin commented
Our situation is same to that of Chris. Currently we have no satisfactory solution to manage the collaboration between the tenants of our group.therefore the user experience is not suited to collaboration.Therefore the user experience is not suited to collaboration.
If the promise of Tenant Friending is to recognize our "internal" users between authorized tenants it would solve many problems. Still, Sharepoint, Teams and Yammer have to support this new type of user.
Chris Chadwick commented
We are a global organisation with multiple tenants. Being able to collaborate as internal users across tenants would solve many problems for us. Having a single tenant is not an option!