Overview of hybrid deployment from exchange to Office 365 series (25)

After all preparations are completed, we can configure hybrid deployment. First, let's first understand what hybrid deployment is.

Local exchange can be migrated directly to Office 365, or you can select the hybrid deployment mode. The hybrid deployment mode can have the following benefits:

• Secure Mail routing between an internal deployment organization and an exchange online organization.

• Use the mail route of the shared domain namespace. For example, both the internal deployment and the Exchange Online organization use the @ contoso.com SMTP domain.

• The unified global address list (GAL), also known as the "shared address book ".

• Free/busy sharing and calendar sharing between an on-premises organization and an exchange online organization.

• Centralized control of inbound and outbound mail streams. You can configure all inbound and outbound Exchange Online mails to use the internal deployment of the exchange organization route.

• The URL of a single Microsoft Office Outlook Web app that is deployed inside the organization and Exchange Online organization.

• You can move an existing on-premises mailbox to an exchange online organization. If necessary, you can also migrate the Exchange Online mailbox back to the internal deployment organization.

• Use the internal deployment Exchange Management Center (EAC) to centrally manage mailboxes.

• Email tracking, email reminders, and multi-Mailbox searches between an on-premises organization and an exchange online organization.

• Deploy cloud-based email archiving for exchange mailboxes. Exchange Online archiving can be used with hybrid deployment.

Under normal circumstances, if the migration is directly to Office 365, after the MX record is directed to Office 365, the local exchange will no longer work, and all emails will be directed to Office 365, it is also from the Exchange Online protect in Office 365. If it is configured as a hybrid deployment mode, the mail will be routed between the two systems, you can use the MX record to select who receives the email first. For example, if the MX record points to Office 365, the email is first sent to Office 365, then route to the local exchange, and vice versa, configure the hybrid deployment mode, you can also choose to migrate to the cloud, or migrate from the cloud to the local

To configure hybrid deployment, you must first meet the following conditions:

For exchange 2007 and exchange 2010 organizations, at least one exchange 2013 Client Access Server and one exchange 2013 mailbox server must be installed in the local organization to run the "hybrid configuration" Wizard and support exchange 2013-based hybrid deployment. When you configure a hybrid deployment for the Exchange 2007 and exchange 2010 environments, You need to combine the exchange 2013 client access and mailbox server roles to a single server. All local exchange 2013 servers must have the cumulative update 1 (cu1) or later version of exchange 2013 installed to support the hybrid function of Office 365.

Hybrid deployment is supported in all Office 365 plans that support Windows azure active directory synchronization. All Office 365 enterprise, government, academic, and midsize plans support hybrid deployment. The Office 365 small business and Office 365 home plans do not support hybrid deployment. The Office 365 tenant version must be 15.0.62.1628 or later to configure the exchange 2013 hybrid deployment.

Deploy the Windows azure active directory synchronization tool to synchronize Active Directory with your local organization

Configure Automatic Discovery of Public DNS records to point to an internal exchange 2013 client to access the server.

 

Must have trusted third-party certificates (internal ca issues are not allowed)

For more information about hybrid deployment, see the exchange deployment assistant. Here, we will introduce some systems, including deployment suggestions in various environments.

Http://technet.microsoft.com/zh-cn/exdeploy2013/Checklist? State = 2419-w-aaaaaaaaqaaaeaaaaaaaa ~

This article is from the "Just make it happen" blog, please be sure to keep this source http://mxyit.blog.51cto.com/4308871/1568608

overview of hybrid deployment from exchange to Office 365 series (25)