Exchange Hybrid Deployment Across Multiple Active Directory Forests Guide
Question details
Understanding supported Exchange hybrid designs and synchronization requirements when connecting multiple Active Directory forests to separate Microsoft 365 tenants.

- Product
- Microsoft Exchange Server
- Device & OS
- not provided
- Scenario
- Planning or configuring an Exchange hybrid topology where multiple on-premises Active Directory forests connect to different Microsoft 365 tenants.
- Observed behavior
- Need to determine the supported Exchange versions, synchronization configurations, and functional limitations for multi-forest, multi-tenant hybrid setups.
Verify your current on-premises Exchange Server versions and ensure you have administrative credentials for both your Active Directory forests and the target Microsoft 365 tenants.
Configure Exchange 2016+ for Multiple Microsoft 365 Tenants
Upgrade to a supported Exchange version and use Azure AD Connect filtering to manage hybrid connectivity across multiple tenants.
If multiple Active Directory forests are connecting to separate Microsoft 365 tenants, the topology can support separate hybrid deployments provided the infrastructure meets specific version and synchronization prerequisites.
Deploy or upgrade your on-premises environment to Exchange 2016 CU18 or later. Note that Exchange 2013 does not support multiple forests in one on-premises organization connecting to different Microsoft 365 tenants.
Install and configure Azure AD Connect. Implement domain-based filtering or organizational-unit (OU) filtering to ensure users and objects from each forest are synced only to their designated Microsoft 365 tenant.
Run the Exchange Hybrid Configuration Wizard (HCW) for each forest, configuring it to connect securely to its respective separate Microsoft 365 tenant.
Review Microsoft's current multiple-forest hybrid documentation and validate the architecture with Microsoft support before proceeding with a production rollout.

Try WPS Office for Your Daily Productivity Needs
While your IT team manages complex Active Directory and Exchange Server hybrid deployments, ensure your end-users have a fast, reliable, and lightweight office suite. WPS Office is a powerful free alternative to Microsoft Office that is easy to deploy and use.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the Suite: Run the installer, agree to the terms, and follow the simple on-screen prompts to complete the setup.
- 3. Start Working: Open WPS Office to instantly start creating, editing, and sharing your documents, spreadsheets, and presentations.

Frequently Asked Questions
Does Exchange 2013 support connecting to multiple Microsoft 365 tenants?
No, Exchange 2013 does not support a topology where multiple Active Directory forests in a single on-premises organization connect to different Microsoft 365 tenants. You must upgrade to Exchange 2016 CU18 or newer.
How do I control which Active Directory users sync to which tenant?
You must configure Azure AD Connect using either domain-based filtering or organizational-unit (OU) filtering to ensure objects from a specific forest or domain synchronize only with the correct Microsoft 365 tenant.
Can I move mailboxes to Exchange Online in this multi-tenant hybrid setup?
Mailbox moves directly to Exchange Online are generally unsupported in a multi-forest to multi-tenant hybrid deployment scenario. Alternative migration strategies may be required.
Will Modern Authentication work for all users in this hybrid topology?
Modern Authentication may be unsupported or experience functional limitations in some multi-forest, multi-tenant hybrid scenarios. It is highly recommended to review Microsoft's official multiple-forest hybrid documentation for the latest authentication support details.




