Plan an Exchange Online hybrid deployment in Office 365
Applies to: Office 365 Deployment Guide for Enterprises
Topic Last Modified: 2013-10-17
Summary: Describes the requirements and considerations for a hybrid Exchange deployment.
To provide the smoothest migration to the Office 365 environment, or to keep a mix of on-premises mail users and Office 365 mail users for a long time, organizations can configure an Exchange hybrid deployment.
A hybrid deployment provides a unified email experience for your Office 365 deployment. It enables users who have mailboxes in your on-premises Exchange Server environment and users who have Exchange Online mailboxes to find one another in the global address list (GAL), and to send, receive, and reply to email regardless of which system is hosting their mailbox.
A hybrid deployment can be either Exchange 2013-based or Exchange 2010-based. Both Exchange 2013 CU2 and Exchange 2010 SP3 include support for hybrid deployments using the Hybrid Configuration wizard, components designed to help you easily configure hybrid deployments. Used stand-alone, or together with the Exchange Deployment Assistant, this wizard provides Exchange administrators with a streamlined process to create and configure a hybrid deployment between on-premises Exchange and Office 365 organizations.
A hybrid deployment provides these advantages:
Exchange Online users and on-premises users can share free/busy calendar data.
Administrators can use the Exchange Admin Center (EAC) with Exchange 2013 or the Exchange Management Console (EMC) with Exchange 2010 to manage both the Exchange Online and on-premises Exchange mail environments.
Administrators can use powerful and familiar Exchange management tools to move users to Exchange Online.
Outlook profiles for users are automatically updated to the Exchange Online environment when the Exchange hybrid deployment and Autodiscover are configured appropriately. Administrators do not have to manually reconfigure Outlook profiles or resynchronize .OST files after they move users’ mailboxes.
Outlook Web App redirection allows for redirection from the on-premises Outlook Web App environment to the Office 365 Outlook Web App environment. You specify a target URL for your organization (for example, www.outlook.com/contoso.com).
MailTips, out-of-office messages, and similar features understand that Office 365 and on-premises users are part of the same organization.
Delivery reports and multi-mailbox search work with users who are on-premises and those working in Exchange Online.
Authentication headers are preserved during cross-premises mail flow. So, all mail looks and feels like it is internal to the company (for example, recipient names resolve in the GAL).
If necessary, administrators can easily move mailboxes back to the on-premises Exchange environment.
For more information about Exchange 2013-based hybrid deployments, see Exchange Server 2013 Hybrid Deployments.
For more information about Exchange 2010-based hybrid deployments, see Understanding Hybrid Deployments with Exchange 2010 SP3.
You should consider the following before you implement an Exchange hybrid deployment:
- Mailbox permissions On-premises mailbox permissions such as Send As, Receive As, and Full Access that are explicitly applied on the mailbox are migrated to Exchange Online. Inherited (non-explicit) mailbox permissions and any permissions on non-mailbox objects—such as distribution lists or a mail-enabled user—are not migrated. Therefore, you have to plan for configuring these permissions in Exchange Online if applicable for your organization. For example, you can use the Add-RecipientPermission and Add-MailboxPermission Windows PowerShell cmdlets to set the permissions in Office 365.
- Cross-premises permissions We do not support cross-premises permission scenarios. Permissions are only migrated and functional when implementing an Exchange hybrid deployment if there are corresponding directory objects in Exchange Online. Additionally, all objects with special permissions such as Send As, Receive As and Full Access must be migrated at the same time. This also means that to migrate these permissions, you must make sure directory synchronization has completed before you start moving mailboxes.
- Offboarding As part of ongoing recipient management, you might have to move Exchange Online mailboxes back to your on-premises environment.
For more information about how to move mailboxes in an Exchange 2010-based hybrid deployment, see Move an Exchange Online mailbox to the on-premises organization.
For more information about how to move mailboxes in an Exchange 2013-based hybrid deployment, see Move Mailboxes Between On-Premises and Exchange Online Organizations in 2013 Hybrid Deployments.
- Multi-forest Active Directory environments If your organization implements multiple forests for logon or resource segmentation, Exchange hybrid deployment is not supported.
There are several requirements for configuring an Exchange hybrid deployment with your on-premises Exchange environment:
- Exchange 2013-based hybrid deployment requirements For the requirements for an Exchange 2013-based hybrid deployment, see Hybrid Deployment Prerequisites.
- Exchange 2010-based hybrid deployment requirements For the requirements for an Exchange 2010-based hybrid deployment, see Hybrid Configuration Wizard Prerequisites.