How to Configure Exchange Hybrid with Three Microsoft 365 Tenants
Question details
The organization needs to synchronize three Active Directory domains from a single forest to three separate Microsoft 365 tenants, while enabling Exchange hybrid for one of the domains.
- Product
- Microsoft Exchange / Microsoft 365
- Device & OS
- not provided
- Scenario
- Deploying a multi-tenant directory synchronization topology and establishing a hybrid email environment for a specific domain.
- Observed behavior
- The goal is to properly align local directory objects with multiple Microsoft Entra ID tenants and set up Exchange hybrid without sync collisions or topology errors.
Ensure you have Global Administrator privileges for all three Microsoft 365 tenants and Enterprise Admin access to your on-premises Active Directory forest before modifying synchronization rules.
Set Up Single-Forest Multi-Tenant Synchronization
Deploy multiple Azure AD Connect servers to carefully scope and synchronize each domain uniquely to its respective Microsoft 365 tenant.
This topology fully supports an Exchange hybrid configuration with exactly one tenant. The most critical requirement is ensuring that each local directory object is represented only once in Microsoft Entra ID and synchronized solely to the correct tenant.
Provision three separate Azure AD Connect (or Microsoft Entra Connect) servers. A single sync server cannot export data to multiple Microsoft 365 tenants simultaneously.
Configure the synchronization rules on each server to strictly filter by Domain or Organizational Unit (OU). Ensure there is no overlap between the objects synchronized to each of the three tenants.
Ensure your on-premises Exchange servers are running a supported version with appropriate cumulative updates, such as Exchange 2016 CU18 or later, or Exchange 2019 CU7 or later.
Launch the Exchange Hybrid Configuration Wizard (HCW) exclusively for the specific domain and tenant where you intend to establish hybrid routing and coexistence.
Optimize Software Costs with WPS Office
While your IT team navigates complex Microsoft 365 tenant topologies and Exchange setups, your enterprise might also be seeking to reduce endpoint software licensing costs. WPS Office is a free, lightweight, and highly compatible alternative suite that covers all your users' everyday document needs.
- 1. Download the software: Visit the official WPS Office website to download the free enterprise or personal installation package.
- 2. Deploy across your domain: Use your standard endpoint management tools to deploy the lightweight installer across your network.
- 3. Open existing files natively: Users can instantly open, edit, and save their existing Microsoft Office documents with complete formatting preservation.
Frequently Asked Questions
Can I use a single Azure AD Connect server to sync all three tenants?
No. A single Azure AD Connect installation can only connect and synchronize to one Microsoft Entra ID (Azure AD) tenant. You must set up three separate sync servers.
Are cross-tenant mailbox moves supported in this hybrid setup?
No, cross-tenant mailbox moves are not natively supported in a topology where a single on-premises forest synchronizes to multiple separate Microsoft 365 tenants.
What Exchange Server versions are required for this multi-tenant hybrid configuration?
You need to use supported Exchange versions and their respective cumulative updates. Microsoft recommends Exchange 2016 CU18 or later, or Exchange 2019 CU7 or later.
Can I enable Exchange hybrid for all three tenants from the same on-premises forest?
No, within this specific multi-tenant single-forest topology, you can only establish an Exchange hybrid configuration with one of the Microsoft 365 tenants.
