Add an On-Premises Exchange Server to Microsoft 365
Question details
The organization wants to add an on-premises Exchange server for users who will not use Microsoft 365.

- Product
- Microsoft Exchange Server, Microsoft 365, and Microsoft Entra Connect
- Device & OS
- not provided
- Scenario
- Some Active Directory accounts already sync to Microsoft 365, but the organization has no on-premises Exchange server.
- Observed behavior
- The desired setup is to host selected users' mailboxes on-premises while continuing to use Microsoft 365 for other users.
Inventory existing cloud mailboxes, Active Directory accounts, email domains, and Microsoft Entra Connect synchronization scope. Check the current Exchange Server version's prerequisites, licensing, DNS, certificate, and Active Directory requirements before installation.
Deploy Exchange and create on-premises mailboxes
Use this approach to host mailboxes locally alongside an existing Microsoft 365 tenant.
Starting directory synchronization before installing Exchange does not by itself prevent an on-premises deployment. Plan each user's mailbox location before provisioning: do not create a new local mailbox for an account that already has a cloud mailbox without following a supported migration process.
Directory synchronization copies supported directory attributes, not mailbox contents. An on-premises mailbox does not require a Microsoft 365 mailbox license merely because its user account is synchronized.
Review Microsoft's Exchange Server deployment documentation and verify supported Windows Server, Active Directory, licensing, certificate, and DNS requirements for the Exchange version you select.
Prepare the existing Active Directory environment as required, then run Exchange Setup on the planned server and install the Mailbox role.
In the Exchange admin center, go to Recipients > Mailboxes and create or enable mailboxes for the users who will be hosted on-premises. Verify their email addresses and mailbox location before provisioning.
Open Microsoft Entra Connect on the synchronization server and review the selected organizational units and filtering rules. Include the on-premises users only if their accounts need to appear in Microsoft Entra ID.
Review the domain's MX and Autodiscover records and configure Exchange mail flow for the planned mailbox locations. If both environments use the same email domain, plan accepted domains, connectors, and routing so each environment can deliver to the other.

Configure Exchange hybrid coexistence when needed
Use a hybrid deployment when the organization needs coordinated mail flow, recipient management, or mailbox moves between on-premises Exchange and Exchange Online.
Use WPS Office for Documents Alongside Your Exchange Deployment
WPS Office is a free, lightweight alternative for everyday document work, with a familiar interface and Microsoft Office format support that makes moving existing files easier. It does not install or manage Exchange servers.

Frequently Asked Questions
Can I install Exchange after Microsoft Entra Connect is already running?
Yes. Plan and install Exchange in the existing Active Directory environment, then review the synchronization scope and recipient configuration. Existing cloud mailboxes require particular care to avoid duplicate mailbox provisioning.
Do on-premises mailbox users need Microsoft 365 mailbox licenses?
Not solely because their accounts synchronize to Microsoft Entra ID. Check Exchange Server and client access licensing requirements separately, as well as licensing for any Microsoft 365 services they use.
Does Microsoft Entra Connect move mailboxes to the cloud?
No. It synchronizes supported directory objects and attributes; it does not transfer mailbox contents. Mailbox moves require a supported Exchange migration method.
Is an Exchange hybrid deployment required?
Not for every local mailbox deployment. Consider hybrid when you need coordinated coexistence, recipient management, or mailbox moves between Exchange Server and Exchange Online.
Can on-premises and cloud mailboxes share the same email domain?
Yes, but shared-domain mail flow must be planned. Configure the relevant accepted domains, connectors, and routing so messages reach recipients hosted in either environment, and test delivery in both directions.




