Using B2B direct connect for shared Microsoft Teams channels across tenants

Design solutions for identity and access management
Answer Correct answer: C — B2B direct connect provides mutual-trust SSO access to shared Teams channels without guest accounts, meeting the cross-tenant collaboration requirements.

You have a Microsoft Entra tenant named contoso.com. You have an external partner that has a Microsoft Entra tenant named fabnkam.com. You need to recommend an identity governance solution for contoso.com that meets the following requirements: • Enables the users in contoso.com and fabrikam.com to communicate by using shared Microsoft Teams channels • Manages access to shared Teams channels in contoso.com by using groups in fabrikam.com • Supports single sign-on (SSO) • Minimizes administrative effort • Maximizes security What should you include in the recommendation?

  1. Cross-tenant synchronization
  2. Microsoft Entra B2B collaboration
  3. B2B direct connect Correct Answer
  4. Microsoft Entra Connect Sync
b2b direct connect shared teams channels cross tenant entra external identities

Community Votes

C
78%
B
22%

78% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

B2B direct connect is the feature purpose-built for shared Teams channels across tenants with mutual trust and SSO, without creating guest accounts; B2B collaboration (B) would add fabrikam users as guests instead.

To let contoso.com and fabrikam.com collaborate in shared Microsoft Teams channels with SSO and no guest accounts, use Microsoft Entra B2B direct connect, which establishes a mutual trust so fabrikam users access contoso's shared channels via their own identities.

Choosing B2B collaboration (B) — that adds external users as guest accounts in contoso, whereas shared Teams channels across tenants are enabled by B2B direct connect without guests.

Community Discussion (6 comments)

424ede1 👍 1 Selected: C
B2B direct connect requires a mutual trust relationship between two Microsoft Entra organizations to allow access to each other's resources. Both the resource organization and the external organization need to enable B2B direct connect in their cross-tenant access settings. When the trust is established, the B2B direct connect user has single sign-on access to resources outside their organization using credentials from their home Microsoft Entra organization. https://learn.microsoft.com/en-us/entra/external-id/b2b-direct-connect-overview
AleFerrillo 👍 1 Selected: C
"B2B direct connect is a feature of Microsoft Entra External ID that lets you set up a mutual trust relationship with another Microsoft Entra organization for seamless collaboration. This feature currently works with Microsoft Teams shared channels." https://learn.microsoft.com/en-us/entra/external-id/b2b-direct-connect-overview
Collecting 👍 1 Selected: C
B2B Direct Connect allows seamless collaboration between users in different Microsoft Entra tenants (Contoso and Fabrikam) without requiring guest accounts. It is specifically designed for shared Microsoft Teams channels and enables:
Er_01 👍 4 Selected: C
B2B collaboration involves adding users as guest to contoso. Direct connect allows for access using fabrikam accounts.
Ali96 👍 1 Selected: B
Microsoft Entra B2B collaboration allows external partners (in this case, fabrikam.com) to securely access resources in contoso.com, including shared Teams channels.
676ae1a 👍 1 Selected: B
Colaboración B2B de Microsoft Entra

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Microsoft Entra B2B direct connect is the feature designed specifically for shared Microsoft Teams channels between two Entra organizations. It sets up a mutual trust relationship and gives external users single sign-on access to the resource tenant's shared channels using their own home-tenant identities, with no guest accounts, minimizing administration while maximizing security.

Why the Other Options Are Wrong

B2B collaboration (B) adds fabrikam users as guest accounts in contoso, which does not meet the 'managed by groups in fabrikam' / no-guest model for shared channels. Cross-tenant synchronization (A) provisions users into the resource tenant, and Entra Connect Sync (D) is for on-premises sync, neither of which is the shared-channels mechanism.

Community Comment Notes

The community strongly favored C (78 votes). Comments cite the B2B direct connect overview confirming it is purpose-built for shared Teams channels with mutual trust and SSO, and note that B2B collaboration would instead create guest accounts.

Official Reference

https://learn.microsoft.com/en-us/entra/external-id/b2b-direct-connect-overview

Related Analysis

You have an Azure subscription. You plan to deploy Azure App

A-Grade

You have an Azure subscription that contains SQL Server on A

S-Grade

You have on-premises Windows 11 devices that have the Global

A-Grade

Practice All SC-100 Questions

Access 110 questions with complete answers and detailed explanations.

View Full SC-100 Practice Test →

← Back to SC-100 Study Guide