How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 4

In this Multi Part Article Series, We will see how to setup Hybrid Exchange 2016 with Office 365 by using ADFS and AAD Directory Sync Services.

How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 1

How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 2

How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 3

Now Click on Install to begin the Hybrid Configuration Wizard

Screenshot_53

Screenshot_54Click on Next

Screenshot_55

Select Detect the optimal Exchange server and Click on Next Screenshot_56

Uncheck Use Current Windows Credentials if the System login and Service account both are different and enter the credentials and Click on NextScreenshot_57 Screenshot_58 Screenshot_59Now, We need to create another TXT record needs to be created on the Public DNS Provider and Verify the DNS ownership. Once Domain Ownership verified, Click Next

Screenshot_60 Screenshot_61

Select Configure my Client Access and Mailbox servers for secure mail Transport (typical) and Click NextScreenshot_62

Select Client Access Server to create Recive connector for mail flow and click Next

Screenshot_63

Select SSL Certificate for the TLS Mail Flow between on-premises and Office365 Screenshot_65

Enter FQDN for On-premisesScreenshot_66

So far so good. Now it is fun time.. Yes it is..

Click on Update to update the Hybdrid configuration. It may take some time to complete depends on your onpremises Exchange and Active Directory.Screenshot_67 Screenshot_68

Congratulations.. Hybrid deployment has been successfully configuredScreenshot_69

How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 1

How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 2

How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 3

Author Bio

Radhakrishnan Govindan

One thought on “How to Configure Exchange 2016 Hybrid Deployment with Office 365-Part 4”

Leave a Reply

Your email address will not be published. Required fields are marked *