How to Enable Collaboration Between Two Microsoft 365 Domains
Question details
Administrators need to set up cross-domain collaboration for separate Microsoft 365 organizations to share resources while keeping the domains distinct.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- An organization manages two separate domains (e.g., a school and a church) and wants users to share links, address books, calendars, and Teams presence without merging the tenants.
- Observed behavior
- Users are currently isolated within their own domains and need properly configured admin settings to collaborate and communicate across tenant boundaries.
Ensure you have Global Administrator privileges for both Microsoft 365 tenants to properly configure external identities and cross-tenant access settings.
Configure Cross-Tenant Access in Microsoft Entra ID (Azure AD B2B)
Use Entra ID B2B collaboration to allow users from one domain to access resources like SharePoint and Teams in the other domain seamlessly.
Microsoft 365 supports robust inter-tenant collaboration through B2B settings. By configuring cross-tenant access, you establish a trusted relationship between the two domains, allowing guests to authenticate securely while adhering to your Conditional Access policies.
Log into the Microsoft Entra admin center. Navigate to External Identities > Cross-tenant access settings.
Click 'Add organization' and enter the tenant ID or domain name of the second Microsoft 365 domain.
Select the newly added organization and modify both inbound access (what they can access in your tenant) and outbound access (what your users can access in theirs) to 'Allow B2B collaboration'.
Go to the Microsoft Teams Admin Center. Under Users > External access, add the partner domain to allow presence sharing, chat, and audio/video calls between the two domains.
Open the SharePoint admin center, navigate to Policies > Sharing, and ensure that external sharing is set to allow 'New and existing guests' so users can share links across the domains.

Set Up Organization Relationships in Exchange Online
Configure an Exchange Online relationship to allow users to view free/busy calendar information across both domains.
Simplify Document Collaboration with WPS Office
If your team needs an easier, cost-effective way to co-edit documents without managing complex Microsoft 365 tenant configurations, WPS Office provides a lightweight, highly compatible alternative. Share and collaborate on documents instantly across any platform.
- 1. Download and Install: Get WPS Office from the official website and install it on your PC or mobile device.
- 2. Create and Save: Create a document and save it to WPS Cloud for real-time syncing.
- 3. Share via Link: Click the 'Share' button to generate a secure link, allowing anyone in the other domain to view or edit the document instantly.

Frequently Asked Questions
Do I need additional licenses for B2B collaboration between Microsoft 365 tenants?
No. Azure AD (Entra ID) B2B collaboration allows you to invite guest users at a 1:5 ratio by default, meaning one licensed internal user can invite up to five guest users without needing extra licenses for basic collaboration.
Can we merge the Global Address Lists (GAL) of both domains without combining tenants?
By default, Microsoft 365 does not natively sync GALs between separate tenants. To share address books fully, administrators must implement GALSync using Microsoft Identity Manager or use a third-party synchronization tool.
Does enabling inter-tenant collaboration compromise our internal security?
No. When using Entra ID B2B, guest users are still subject to your domain's Conditional Access policies. You maintain full control over which applications they can access and can enforce rules like required MFA or device compliance.
Why can't our users chat in Teams even after setting up B2B collaboration?
Teams chat requires External Access to be explicitly configured. Ensure that you have gone to the Teams Admin Center > Users > External access, and added the partner domain to the list of allowed domains in both tenants.




