Exchange Hybrid Coexistence Between Independent Tenants: How It Works, the Limits, and the Licensing
If you run two independent Microsoft 365 tenants, after an acquisition, across two legal entities or with a close partner, someone will ask for "Exchange hybrid between the tenants" so calendars, the address book and mail look like one company. There is no hybrid answer: Exchange hybrid joins an on-premises Exchange organization to Exchange Online, never one tenant to another. What you can have is coexistence, a set of separate cross-tenant features with their own limits and licenses. This guide covers what each gives the people in both tenants, what it cannot do, and what it costs.
Why there is no hybrid between two tenants
Microsoft's documentation describes an Exchange hybrid deployment as the configuration that gives an on-premises Exchange organization and Exchange Online the look and feel of one organization: a shared domain namespace, a unified global address list, free/busy across both sides, mail routing and mailbox moves. Microsoft's documentation states that one on-premises organization can even be in hybrid with two or more tenants, but the on-premises side is always one end. Two tenants have no Exchange Server between them, so there is nothing to configure.
That is why the search phrase "coexistence Exchange hybride, tenant indépendant, relation B2B" lands on pages that do not answer it. Free/busy, mail routing and Teams collaboration exist as separate features; a unified address book does not. And hybrid tooling applies only while one organization still runs Exchange Server, where our hybrid migration from your own Exchange Server is the right project.
Mail flow and domains: one domain, one tenant
A custom domain is verified in one Microsoft 365 tenant at a time. Microsoft's documentation states that a domain is associated with only one service, and that moving it means removing it from the first tenant before verifying it in the second. So contoso.com belongs to one tenant, its MX record points there, and Autodiscover resolves there. The other tenant keeps its own domain or a separately verified subdomain.
The workaround is a split domain: contoso.com stays in tenant A as an internal relay accepted domain, tenant A holds a mail user for every contoso.com person who sits in tenant B, with a target address on tenant B's domain, and an outbound connector relays unresolved recipients. It is also the state cross-tenant mailbox migration leaves behind. It means every joiner and leaver in tenant B needs an object maintained in tenant A. Fine for a 90-day transition; as a permanent state it is a second directory administered by hand. One domain for everyone is a domain cutover, and the MX spooler service ($2,890 per project) keeps it from bouncing mail.
Calendar free/busy: organization relationships and the new cross-tenant access policy
Free/busy between two Exchange Online tenants has run for years on an organization relationship, created in each tenant toward the other. Microsoft's Set-OrganizationRelationship reference lists three access levels: None, AvailabilityOnly (times only) and LimitedDetails (time, subject and location). Full calendar details stay a per-user sharing decision, and because each side creates its own relationship, free/busy can be one-way.
This is changing now. Microsoft 365 Message Center notice MC1446796 (August 2026) states that free/busy, MailTips and calendar sharing with another Microsoft 365 organization through an organization relationship, availability address space or sharing policy relies on Exchange Web Services; that the replacement is a Microsoft 365 cross-tenant access policy rolling out since August 2026; that EWS deprecation for this scenario begins October 1, 2026; and that tenants must migrate before the EWS shutdown on April 1, 2027. If your tenants already share free/busy, that migration is due now; our EWS retirement guide covers the wider changes.
Address book: there is no shared GAL across tenants
Nothing in Exchange Online merges two tenants' global address lists. The options Microsoft documents, in order of effort:
Multitenant organization. Microsoft's planning guide (March 2026) describes a multitenant organization of up to 100 tenants in which users are provisioned into the other tenants as B2B collaboration users of type member rather than guest, which turns on cross-tenant people search. It requires Microsoft Entra ID P1 or above in all tenants plus the synchronization licensing below. It is the closest thing to a shared GAL Microsoft ships.
Cross-tenant synchronization. The Entra service that creates, updates and deletes B2B users in the target tenant from the source tenant automatically (Microsoft, May 2026). Each synchronized user needs an Entra ID P1 license in their home tenant; with showInAddressList set, they appear in the target tenant's address lists. It synchronizes internal members only.
Mail contacts, by script or tool: no Entra licenses, but no presence, no Teams chat and no cleanup when someone leaves.
If both tenants run Business Premium or Microsoft 365 E3, P1 is included and synchronization adds no license cost. Otherwise add Entra ID P1 for the synchronized users, $7.00 per user per month on an annual term ($84.00 ÷ 12, Microsoft list price, October 2026 price list).
Teams and SharePoint: external access, guests, and shared channels
Three mechanisms, three user experiences.
External access (federation) lets your people find, chat with, call and meet people in the other tenant from their own Teams. Microsoft's documentation states that an external user is not a member of anything: no access to your files, teams or rosters.
B2B collaboration (guests) invites a person from the other tenant into your directory as a guest who signs in with their home identity (Microsoft, April 2026). Guests join teams and open SharePoint sites and OneDrive links. Billing follows the Entra External ID monthly active user model, which requires linking the tenant to an Azure subscription (Microsoft, June 2026); that meter is your Azure consumption, not part of any license from us.
B2B direct connect (shared channels) is a mutual trust between the tenants with no guest object: the other company's users open a shared channel from their own Teams (Microsoft, April 2026). Microsoft's cross-tenant access documentation (March 2025) states that B2B direct connect needs an Entra ID P1 license in both tenants, and that configuring trust settings, or scoping inbound and outbound access to specific users, groups or applications, also needs P1.
All three are governed from the cross-tenant access settings in Entra: default settings for every outside tenant, organizational settings for the partner you actually coexist with. Configure the partner explicitly and leave the defaults tight.
Cross-tenant mailbox migration: coexistence that ends in a move
Microsoft's cross-tenant mailbox migration (documentation dated September 2025) moves Exchange Online mailboxes between tenants under an organization relationship with MailboxMoveEnabled and a migration endpoint. The prerequisites make it a project:
- Every migrating user must exist in the target tenant as a MailUser with specific attributes before the batch runs, with an Exchange Online license waiting: Exchange Online Plan 1 is $4.00 per user per month on an annual term ($48.00 ÷ 12) and Plan 2 is $8.00 ($96.00 ÷ 12), Microsoft list prices, October 2026 price list.
- A Cross-tenant user data migration license is assigned per user on the source or target object; Microsoft describes it as a one-time fee that also covers the OneDrive move. It is $15.00 per user on the October 2026 price list, listed on a one-year term. Without it the migration fails.
- Batches should not exceed 2,000 mailboxes, mailboxes on hold are blocked, auto-expanding archives do not move, and Teams chat, Microsoft 365 Groups and public folders are not part of the mailbox move.
- Afterwards the source mailbox becomes a MailUser pointing at the target until the domain is cut over.
This is the engagement behind our tenant-to-tenant cutover email migration ($3,500 tenant fee plus $35 per mailbox, 5 weeks) and the no-downtime variant ($3,800 plus $35 per mailbox, 3 weeks). The merger migration guide covers Teams, SharePoint and Azure; one tenant or many covers the case for staying separate.
Frequently asked questions
Can two independent Microsoft 365 tenants be set up as an Exchange hybrid?
No. Hybrid connects an on-premises Exchange organization to Exchange Online. Between two tenants you combine free/busy sharing, cross-tenant access settings in Entra for Teams and files, and cross-tenant mailbox migration.
Can both tenants use the same email domain?
Not at the same time. A split domain routes mail during a transition, but every user on the other side needs a mail user maintained by hand in the owning tenant.
Do we need Entra ID P1 in both tenants?
For shared channels, yes, and wherever trust settings or scoped cross-tenant access policies are configured. Guest invitations and Teams external access do not require P1. Business Premium and Microsoft 365 E3 include it.
Sources
- Microsoft Learn source files on GitHub (MicrosoftDocs/entra-docs), opened: "Cross-tenant access with Microsoft Entra External ID", ms.date 03/28/2025; "B2B direct connect overview", ms.date 04/24/2026; "What is Microsoft Entra B2B collaboration?", ms.date 04/24/2026; "Billing model for Microsoft Entra External ID", ms.date 06/22/2026; "What is cross-tenant synchronization in Microsoft Entra ID?", ms.date 05/29/2026
- Microsoft Learn source files on GitHub (MicrosoftDocs/microsoft-365-docs), opened: "Cross-tenant mailbox migration", ms.date 09/28/2025; "Plan for multitenant organizations in Microsoft 365", ms.date 03/31/2026
- Microsoft Learn pages that could not be retrieved when this article was written, cited without a date: "Exchange Server hybrid deployments"; "Organization relationships in Exchange Online" and the Set-OrganizationRelationship reference; "Migrate to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips"; "Domains FAQ"; "Communicate with users from other organizations" (Teams)
- Microsoft 365 Message Center notice MC1446796, "Migrate Free/Busy, MailTips, and Calendar Sharing before EWS deprecation", August 2026
- IT Partner blog: content/blog/new/domain-cutover-in-a-microsoft-365-tenant-to-tenant-migration-the-outage-window-and-the-mx-spooler.json; exchange-server-se-and-ews-retirement-october-2026.json; tenant-to-tenant-migration-after-a-merger-a-complete-guide.json; one-microsoft-365-tenant-or-many-holding-companies-franchises-and-roll-ups.json
- IT Partner pages: content/services/ITPWW120MIGOT, ITPWW380MIGOT, ITPWW170MIGOT, ITPWW320CONOT and ITPWW530MIGOT; Exchange Online (Plan 1) CFQ7TTC0LH16, Exchange Online (Plan 2) CFQ7TTC0LH1P, Microsoft Entra ID P1 CFQ7TTC0LFLS, Cross-tenant user data migration CFQ7TTC0R2N9, October 2026 price list
- IT Partner engineering notes from merger coexistence projects, September 2026
| What the user sees | Free/busy relationship or cross-tenant access policy | Teams external access | B2B guests | Shared channels | Multitenant organization |
|---|---|---|---|---|---|
| Free/busy | Times, or subject and location | No | No | No | Still needs the Exchange relationship |
| Address book | No | No | Only where added | No | Yes, people search and address lists |
| Teams chat | No | Chat, calls, meetings | Yes, switching tenants | Inside the channel | Yes, as members |
| SharePoint sharing | No | No | Per site or link | Channel files | Yes, as members |
| Licenses | Exchange Online in both tenants | Teams in both tenants | Host plan; External ID MAU billing on Azure | Entra ID P1 in both tenants | Entra ID P1 in all tenants |
Key takeaways
- Exchange hybrid is on-premises to Exchange Online; two tenants coexist through separate features, and hybrid tooling applies only while one side still runs Exchange Server.
- A domain is verified in one tenant; a split domain with internal relay and mail users is a transition, not a design.
- Cross-tenant free/busy is moving from EWS-based organization relationships to the Microsoft 365 cross-tenant access policy; EWS deprecation for it started October 1, 2026, with shutdown on April 1, 2027.
- There is no native shared GAL; cross-tenant synchronization or a multitenant organization, both on Entra ID P1, is the supported way in.
- Cross-tenant mailbox migration needs a MailUser and an Exchange Online license in the target plus a $15.00 per-user Cross-tenant user data migration license, and it moves mail only.
If one side still runs Exchange Server, start with our hybrid migration from your own Exchange Server: Microsoft-sponsored, subject to eligibility, otherwise $2,500 plus $35 per mailbox over 2 weeks. If both sides are in Exchange Online and the plan is one tenant, the no-downtime tenant-to-tenant email migration ($3,800 plus $35 per mailbox, 3 weeks) is the engagement, and mergers and acquisitions tenant consolidation scopes everything around it. Quote licenses from the Exchange Online Plan 1 and Entra ID P1 pages, or book 30 minutes with Mike with your two tenant names and the closing date.
Questions this article didn’t answer?
Thirty minutes with Mike — our CEO, not a sales rep. Bring the hard version of the question.