Share an Email Domain Across Microsoft 365 and Exchange Forests
Question details
Determine how separate Active Directory forests can use one email domain while hosting mailboxes both on-premises and in Microsoft 365.

- Product
- Microsoft 365 and Exchange Server
- Device & OS
- not provided
- Scenario
- Three entities want to retain separate Active Directory forests while sharing an email domain across on-premises Exchange and Exchange Online mailboxes.
- Observed behavior
- Users need mail delivery to the correct mailbox without unnecessarily exposing one entity's environment to another.
Inventory the Exchange organizations, server versions, Active Directory forests, existing Microsoft 365 tenants, email domains, and mailbox locations. Identify the required isolation and visibility between entities before choosing the tenant and mail-routing design.
Plan a Multi-Forest Exchange Hybrid Deployment
Use a supported hybrid design to coordinate identities and mail flow between on-premises Exchange and Exchange Online while retaining separate forests.
A custom email domain can be verified in only one Microsoft 365 tenant at a time. If the entities require separate tenants, sharing the exact domain requires a different, carefully designed routing arrangement rather than verifying it in every tenant.
Hybrid connectivity and directory synchronization do not by themselves guarantee isolation. Define which administrative access, directory visibility, and network connections are permitted, and validate the proposed multi-forest and Exchange organization topology against current Microsoft documentation.
In the Microsoft 365 admin center, open Settings > Domains and check which tenant owns the shared email domain. Plan to use that tenant for the Exchange Online mailboxes if the entities can meet their isolation requirements within it.
Review Microsoft Entra Connect Sync's supported multi-forest configurations and select the forests and users to synchronize. Plan unique identities and matching rules for any users represented in more than one forest; on-premises-only users do not automatically need cloud mailboxes.
Review the Exchange Server versions, Exchange organizations, certificates, DNS records, and network connectivity. Consult Microsoft's Exchange hybrid documentation to confirm support for the specific multi-forest topology before running the Hybrid Configuration Wizard.
In the Exchange admin center, review Mail flow > Accepted domains and Connectors. Design the public MX destination and routing between environments so each recipient resolves to the correct mailbox without delivery loops; use internal relay settings only where the routing design requires them.
Run the Hybrid Configuration Wizard for the supported topology, configure the approved synchronization scope, and test messages to and from mailboxes in each environment. Verify recipient visibility and administrative permissions against each entity's isolation requirements.

Document Your Exchange Migration Plan with WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility, making it easy to move existing planning documents and spreadsheets into WPS. It does not configure Exchange hybrid or resolve email routing.

Frequently Asked Questions
Can the same email domain be verified in multiple Microsoft 365 tenants?
No. A custom domain can be verified in only one tenant at a time. Check its ownership in the Microsoft 365 admin center under Settings > Domains before designing the deployment.
Do all on-premises Exchange users need an Exchange Online mailbox?
No. A hybrid deployment can have mailboxes on-premises and in Exchange Online. Plan directory synchronization and recipient representation according to the coexistence and routing requirements.
Can separate Active Directory forests synchronize to one Microsoft 365 tenant?
Microsoft Entra Connect Sync supports multi-forest configurations. Review the supported topology and configure forest connections, synchronization scope, and identity matching to avoid duplicate or conflicting accounts.
Does Exchange hybrid keep the entities completely hidden from each other?
Not automatically. Hybrid and synchronization can introduce shared directory visibility and connections. Review recipient visibility, administrative permissions, and network access as part of the design.
Where should the shared domain's MX record point?
The MX destination depends on the chosen mail-flow design. Plan how the receiving environment routes messages to both on-premises and cloud recipients, then review accepted domains and connectors under Mail flow in the Exchange admin center.




