We have configured ADFS 2.0, Microsoft Online Services Module for PowerShell, enabled a public domain for SSO, activated AD synchronization in Office 365, installed & configured Dir Sync tool in our on-premise environment & sync’d AD with Office 365. Read part one, two, three and four, if you have missed it. In this part, we will add the Office 365 forest in our on-premise Exchange 2010 EMC and configure hybrid deployment to have a seamless functionality irrespective of whether your mailbox is on-premise or in the cloud.
As we have a sync’d AD in the cloud, let’s add the Office 365 tenant to the Exchange 2010 EMC. Launch EMC and select “Microsoft Exchange”. Click on “Add Exchange Forest” on the right hand pane. Type in a friendly name, (say Office 365) and select “Exchange Online” as the fqdn for remote PowerShell instance & click ok.
Enter the Office 365 admin credentials.
Wait for a minute or two and the console will display the Office 365 options in the EMC.
This is all fine, but we really need to setup the “hybrid deployment” feature in Exchange 2010 SP2 next. A hybrid deployment provides the seamless look and feel of a single Exchange organization between on-premises and cloud based organization. Having hybrid deployment configured properly gives the following benefits for on-premise and cloud based mailbox users.
- Free/busy sharing
- Mailbox Moves
- Message Tracking
- Online Archiving
- OWA Re-direction
- Secure email using TLS.
Let’s create a hybrid deployment in 2010 SP2. Launch EMC, select Organization Configuration and select “Hybrid Deployment” tab. Click on “New Hybrid Configuration” from the right hand pane. Click “New”.
Click “finish” and that’s it.
The above process only creates a new hybrid deployment. The next step si to configure it. Select the “Hybrid Configuration object and click “Manage Hybrid Configuration”. A new wizard starts and this is where we configure the settings for seamless functionality between on-premise and Office 365.
Make sure the pre-reqs are met and click Next. You should have a public certificate for your Exchange services configured, which any org will have.
Enter the admin credentials for Office 365 and on-premise Exchange. Check the “remember my credentials” checkbox.
Add the domain to configure for hybrid setup. This domain has to be an accepted domain in the on-premise Exchange.
Proof of ownership for the domain has to confirmed. You will be asked to add a TXT record in your public DNS. Once that is down, check the box & select “Next”. If the replication takes a while, you can run the wizard again.
Select the on-premise CAS and Hub servers.
Select the public IP through which emails will be received from the cloud. Specify the on-premise hub server fqdn as well and click next.
Select the certificate to be used for secure email using TLS (this has to be a public certificate on the Exchange server). The choice for email flow path can be selected as well.
Have a look at the summary and click “Manage” if you are happy with the settings.
You will now have seamless functionality irrespective of the location of the user mailbox.
This concludes part 5. Stay tuned for part 6!
UC Architect, Blogger, Husband & Dad. I have been in IT for the last 14 years, with interests in Active Directory, Exchange, Office 365 & Windows Azure. I am active on Experts Exchange & TechNet forums and I am a technical author for SearchExchange.