Before May 1st, I was busy with the project, doing the hybrid deployment of Exchange 2013 and Office 365. Now let’s record the process of hybrid deployment.
First, explain the following architecture: The
local Exchange 2013CU17 has been deployed and functions normally;
hybrid deployment plans to use
- An AAD Connect server;
- Two ADFS servers;
- Two ADFS proxy servers;
- An ADFS public network certificate;
| server nickname | IP address | effect |
|---|---|---|
| AADonline | 10.7.81.23 | AAD Connect Server |
| ADFS01 | 10.7.81.24 | ADFS server |
| ADFS02 | 10.7.81.25 | ADFS server |
| proxy01 | 172.7.81.26 | ADFS proxy server |
| proxy02 | 172.7.81.27 | ADFS proxy server |
The AAD Connect server is responsible for synchronizing local AD users to Azure AD; the
ADFS server is deployed to provide the single sign-on function for the cluster;
the ADFS proxy server is placed in the DMZ area to proxy ADFS to prevent ADFS from being directly exposed to the public network. Deploy two clusters;
We first add the office 365 domain name. Since we are using 21Vianet's office 365 this time, log in to the " portal.partner.microsoftonline.cn " website, enter the O365 administrator account password 
to log in, and click "Administrator" on the home page. Enter the admin center interface, start our operation, 
select "Install" - "Domain" and 
click "Add Domain" 
to enter our domain name, which is our email domain name. Next 
, add the following TXT record in our public network DNS, After the addition is complete, verify 
that "I will manage my own DNS records" is selected, the next step is 
to select online services, and "Exchange" is checked, and the next step 
is to add the following TXT records to our public network DNS, because I don't want autodiscover here The MX record is changed (mail flow), so only the msoid record is added. After the addition is completed, the verification is 
completed
So far, we have completed the steps of adding a domain. In the next article, we will install and configure AAD Connect.