Updating recipient policies for hybrid coexistence
Finally, we will add our on-premises domain to Office 365. The lab environment used as the basis of this article series consists of the following servers: The Active Directory forest name is ”clouduser.dk” and split-brain DNS is used, which means that the same namespace is used internally as well as externally.
Forest and domain functional level is running in Windows Server 2012 mode.
With tenants moved to or created in the new Office 365, we are encouraged to replace our Exchange 2010 hybrid servers with hybrid servers running Exchange 2013 Customer Update 1 (CU1).
Note: Existing Office 365 customers that have deployed Exchange 2010 based hybrid servers and are upgraded to the New Office 365 can still use these hybrid servers for coexistence, but will not get all the advantages that customers running Exchange 2013 hybrid server will get.
However, details around this new option will be included in another articles series.
Okay, so my previous article series focused on deploying ADFS-based identity federation, Directory Synchronization (Dir Sync) and an Exchange 2010 based hybrid deployment into an on-premises infrastructure containing an Exchange 2007 organization.
So if we leave third party migration solutions out of the picture, we have four different migration approaches at our disposal: Note: When migrating from an on-premises Domino/Notes environment, the approach is to use a third party tool such as CMT from Binary Tree or Notes migrator from Quest Software (Dell).
In this particular multi-part article series, I’ll go through the steps necessary to configure an Exchange 2010 hybrid configuration in a pure Exchange 2010 on-premises organization followed by migrating mailboxes to the new Exchange Online.
An Exchange hybrid deployment based migration to the new Exchange Online usually involves the following deployment steps: As most of you know, the new Office 365 not only consists of Exchange Online but also Lync Online and Share Point Online, Sky Drive Pro, Yammer, the rich Office application, Office Web Apps etc.
However in this article series we only focus on the Exchange side of things.
I’ll also uncover the advantages you get by choosing a hybrid configuration based migration.