For a customer vi have an O365 tenant and assisting them with deploying everything. One very interesting scenario related to B2B collaboration is when a person is invited from another O365 tenant (Azure AD).
Using PowerShell one can set -usertype 'Guest' or -usertype 'Member'. The first option we all know a regular guest user, sourced from an External Azure Active Directory. The other options on the other hand is quite more interesting - except for a more general description from docs what does this means in the real life ?
Example:
Trudy from the partner Tenant A is invited as a guest with usertype = Member into the Host Tenant. When Trudy access the SharePoint Online landing-page in the Host Tenant she has read access, and sees the content alongside licensed user in the Host Tenant. But in the Office 365 Suite Bar the my account link takes her back to her Account page in Tenant A. In the AppLauncher, available services is from Tenant A - Only the content from SharePoint Online is from the Host Tenant.
All this is logic and expected behavior - because Trudy can now access Host Tenant resources alongside licensed users
BUT ANYONE ??
- PowerApps can not be shared with traditional guest users. BUT when Trudy has usertype = Member, the PowerApp can indeed be shared - and is that even allowed ref licensing?
- When beeing invited into Temas as guest user with usertype = Member it seems to messes up presences going back and forth between tenants in the Teams App
- Are there other sideeffects when a user has its usertype = Member ?
- ANYONE have experience using this setup in real life ? Any knowledge sharing would be most appreciated
