Two partner organisations on separate Microsoft Entra tenants want their members to collaborate in Microsoft Teams shared channels using their home accounts, and a strict requirement states that no guest user objects may be created in either tenant. You must enable this collaboration model in your cross-tenant access settings while leaving ordinary B2B guest invitations unaffected. Which capability should you enable for the partner organisation?
- AB2B direct connect inbound settings, which establish a mutual trust that lets partner users access Teams shared channels with no guest object created. Correct
- BB2B collaboration inbound settings, which let the partner's users be added to your tenant as guest objects you can target with Conditional Access.
- CSelf-service sign-up for the application, so partner members create their own accounts when they first open the shared resource.
- DCross-tenant synchronisation, which provisions the partner's users into your tenant automatically and keeps them in step as joiners and leavers occur.
Why A is correct: B2B direct connect is the only model that grants Teams shared channel access through a tenant-to-tenant trust without creating any guest user object.
Why B is wrong: B2B collaboration is the standard guest model, but it creates guest user objects, which the requirement explicitly forbids.
Why C is wrong: Self-service sign-up produces local accounts in your tenant for an external app and does not enable Teams shared channel access without guest objects.
Why D is wrong: Cross-tenant synchronisation also creates B2B user objects in the target tenant, so it still produces accounts the requirement prohibits.