Two partner organisations on separate Microsoft Entra tenants want their members to join each other's Microsoft Teams shared channels and use shared apps with their home accounts, and a requirement states that no guest user objects may be created in either tenant. Which cross-tenant capability satisfies this without creating guest accounts?
- AConfigure B2B collaboration in cross-tenant access settings, because inviting the partners as collaboration users grants the same shared-channel access through their home credentials.
- BConfigure B2B direct connect in cross-tenant access settings, because it establishes a mutual trust that lets external members access Teams shared channels without any guest object being created. Correct
- CConfigure cross-tenant synchronisation from each tenant to the other, because it links the partner members so they can reach shared channels without separate accounts.
- DConfigure direct federation with each partner domain, because federating the domains lets the members sign in to shared channels using their existing identity provider.
Why A is wrong: B2B collaboration does grant access with home credentials, but it creates a guest user object in the resource tenant, which directly violates the no-guest-object requirement.
Why B is correct: B2B direct connect creates a mutual trust between tenants that authorises shared-channel and shared-app access using the user's home account, and it provisions no guest object in either tenant.
Why C is wrong: Cross-tenant synchronisation reaches shared resources only by provisioning B2B collaboration guest objects, so it creates the very accounts the requirement forbids.
Why D is wrong: Direct federation governs how invited external users authenticate, but it still relies on a guest object being created for the user and is not the shared-channel trust mechanism.