In the last part of this series we looked at preparing for Hybrid deployment with Office 365. In this article we’re going to create the Hybrid configuration between the on-premises Exchange organization and the Office 365 tenant.
The current on-premises environment is running:
- 2 x Exchange 2016 Mailbox servers
- 1 x Exchange 2013 multi-role server
- 1 x Exchange 2013 Edge Transport server
- 1 x Exchange 2010 multi-role server
The Exchange 2016 Mailbox servers are the internet-facing servers for the organization, with a load balancer distributing traffic across them. Since those servers will be internet-facing for the Hybrid configuration, they need to be MRS Proxy enabled. Currently they are not MRS Proxy enabled, as seen here in the output of Get-WebServicesVirtualDirectory.
[PS] C:\>Get-WebServicesVirtualDirectory | fl server,mrs* Server : EX2013SRV1 MRSProxyEnabled : True Server : EX2010SRV1 MRSProxyEnabled : True Server : EX2016SRV1 MRSProxyEnabled : False Server : EX2016SRV2 MRSProxyEnabled : False
The servers can be MRS Proxy enabled by running Set-WebServicesVirtualDirectory.
[PS] C:\>Get-WebServicesVirtualDirectory -ADPropertiesOnly | Where {$_.MRSProxyEnabled -ne $true} | Set-WebServicesVirtualDirectory -MRSProxyEnabled $true
The Hybrid Configuration Wizard is launched from the Exchange Admin Center, in the hybrid section.
After clicking enable we need to sign in to the Office 365 tenant with a global admin account.
We’re directed to download the Hybrid Configuration Wizard tool. Click on the click here link to download it.
Follow the prompts to install the application.
When the Hybrid Configuration Wizard launches, click Next to begin.
The HCW will detect a server to use automatically, or you can specify one if you need to.
Enter credentials for both the on-premises organization and the Office 365 tenant.
When the connections and credentials have been successfully validated, click Next to continue.
For my scenario I’ll be using the Edge Transport server for secure mail flow, and not enabling centralized mail transport.
There is only one Edge Transport to choose in my environment.
Next we choose a reference server, and then an SSL certificate on that server, to use for secure mail flow.
Enter an FQDN that can be used by Exchange Online Protection to route mail to the on-premises organization. This name should resolve in DNS to the public IP address of your on-premises server.
After entering all of the information in the wizard click Update to configure and enable Hybrid for your organization. The configuration takes just a few moments as long as there are no errors encountered.
In the next part of this series we’ll look at testing the features of the Hybrid configuration.
This article Creating a Hybrid Configuration with Exchange and Office 365 is © 2016 ExchangeServerPro.com
Get more Exchange Server tips at ExchangeServerPro.com
