Hybrid Configuration Business Case.
- On-premises IRM- Information Rights Management (IRM) enables users to apply Active Directory Rights Management Services (AD RMS) templates to messages that they send.
- Antispam and malware protection- Mailboxes moved to Office 365 are automatically provided with antivirus and anti-spam protection by Exchange Online Protection (EOP), a service provided by Office 365. However, for corporate compliance reason, mail must flow through via on-premises anti-spam and firewall devices.
- Public Folder- You have on-premises public folder and you would like to retain on-premises public folder.
- Legacy Application- You have legacy applications that only support localised email server instead internet based email server
- On-prem UM- You have on-premises unified messaging infrastructure or telephony systems that only communicate with localised email servers
- Use of current CAPEX- You want to utilise current on-premises investment until the equipment expires and you are not ready to move into cloud completely.
In a hybrid deployment when you connect your Office 365 Exchange Online organization to your existing on-premises Exchange organization using the Hybrid Configuration wizard. After configuring the hybrid deployment, the following features are enabled:
- Secure mail routing between on-premises between the organizations.
- Mail routing with a shared domain namespace. For example, both on-premises and Exchange Online organizations use the @domain.com SMTP domain.
- A unified global address list (GAL), also called a “shared address book,” showing full details of recipients.
- Free/busy calendar information sharing between the organizations.
- Centralized control of inbound and outbound mail flow. You can configure all inbound and outbound Exchange Online messages to be routed through the on-premises Exchange organization.
- A single Outlook on the web URL for both the organizations.
- Automatic Exchange ActiveSync profile redirection when mailboxes are moved to Office 365 (dependent on device support).
- The ability to move on-premises mailboxes to the Exchange Online organization and vice versa.
- Centralized mailbox management using the on-premises Exchange Administration Center (EAC).
- Message tracking, internal MailTips and Out of Office replies, and multi-mailbox search between the organizations.
- Cloud-based message archiving for on-premises Exchange mailboxes. Exchange Online Archiving can be used with a hybrid deployment
A hybrid deployment involves several different services and components:
- Exchange 2016 Servers- The Exchange 2016 Mailbox server role is required in your on-premises Exchange organization. All on-premises Exchange 2016 servers need to have the latest release of Exchange 2016, or the release immediately prior to the current release, installed to support hybrid functionality with Office 365.
- Office 365- Hybrid deployments are supported with Office 365 Enterprise, Government and Academic plans.
- Hybrid Configuration wizard- Exchange 2016 includes the Hybrid Configuration wizard which provides you with a streamlined process to configure a hybrid deployment between on-premises Exchange and Exchange Online organizations.
- Azure AD authentication system- The Azure Active Directory (AD) authentication system is a free cloud-based service that acts as the trust broker between your on-premises Exchange 2016 organization and the Exchange Online organization. On-premises organizations configuring a hybrid deployment must have a federation trust with the Azure AD authentication system. The Hybrid Configuration wizard as part of configuring a hybrid deployment creates the federation trust. A federation trust with the Azure AD authentication system for your Office 365 tenant is automatically configured when you activate your Office 365 service account.
- Azure Active Directory synchronization- Azure AD synchronization uses Azure AD Connect to replicate on-premises Active Directory information for mail-enabled objects to the Office 365 organization to support the unified global address list (GAL) and user authentication. Organizations configuring a hybrid deployment need to deploy Azure AD Connect on a separate, on-premises server to synchronize your on-premises Active Directory with Office 365.
- Active Directory Federation Services- AD FS provides simplified, secured identity federation and Web single sign-on (SSO) capabilities for end users who want to access applications within an AD FS-secured enterprise, in federation partner organizations, or in the cloud.
- Web Application Proxy Server- The Web Application Proxy under the Remote Access role that allows administrators to securely publish applications for external access. This service acts as a reverse proxy and as an Active Directory Federation Services (AD FS) proxy.
Hybrid infrastructure
To be able to configure your current on-premises Exchange organization for a hybrid deployment, the following components are required.
| Exchange Server 2016 with Mailbox Role |
EXCH2016 |
| Exchange Server 2016 with Edge Transport Role |
EXCH2016EDGE |
| Windows Server 2016 with Azure Active Directory Connect (AAD Connect) Installed |
AADCONNECT |
| Active Directory Federation Server(s) |
ADFS2016 |
| Web Application Proxy Server in perimeter |
EDGE2016 |
| Domain Controller running on minimum Windows Server 2008 R2 |
DC01 |
| Office 365 Subscriptions with default domain configured i.e. Service tenant FQDN |
Domain.onmicrosoft.com |
| Accepted Domain in Office 365 and On-premises |
Domain.com |
| On-premises domain type |
Authoritative |
| Office 365 Domain Type |
Internal Relay |
| User principal name domain and Microsoft Online ID domain |
@domain.com |
| External Azure AD Connect with AD FS FQDN |
sts.domain.com |
| On-premises Autodiscover FQDN |
Autodiscover.domain.com |
| Office 365 Autodiscover |
Autodiscover.outlook.com |
Configuring Hybrid Exchange Server
Step1: Add and validate primary Email domain to Office 365
Perform the following steps to add the primary SMTP namespace to Office 365:
- Log on to: Office 365 admin center preview
- Click Settings > Domains > Add domain.
- Enter the primary SMTP namespace. For example, domain.com. Then, click Next.
- Copy the TXT record from the Wizard, go to domain management portal and add a text record ms=msxxxxxxx record and verify the domain. Setup TTL to 10 minutes. When complete, wait 10 minutes and then click Verify. If the wizard says it can’t verify your domain ownership, you might need to wait longer for your DNS records to update across the Internet; this might take several hours. Also verify that the record you created is correct.
- On the Required DNS settings page, click Continue setup. Don’t update your DNS records right now. Instead, you’ll update your DNS records later in your hybrid deployment.
- On the Set up your online services page, select I’ll manage my own DNS records and click Next.
- On the Update DNS settings page, select Skip this step – I have custom DNS records, so I’ll add the records I need later. I understand that some Office 365 services may be unavailable until I manually add the records with my registrar. Click Skip, and then click Finish.
Step2: Setup Primary SMTP Domain to Internal Relay
Definitions of Domain Type
Authoritative – Selecting this option means that email is delivered to email addresses that are listed for recipients in Office 365 for this domain. Emails for unknown recipients are rejected.
Internal relay – Selecting this option means that recipients for this domain can be in Office 365 or your on-premises mail servers. Email is delivered to known recipients in Office 365 or is relayed to your own email server if the recipients aren’t known to Office 365.
Use the Exchange Online EAC to change the domain type
- In the EAC, navigate to Mail flow > Accepted domains.
- Select the domain and click Edit .
- In the Accepted Domain window, in the This accepted domain is section, select the domain type. Edit the domain value to Internal relay.
Step3: Configure Active Directory synchronization
- Download Azure Active Directory Connect on the computer where you’ll install it, and then open it.
- On the Welcome page, click Next if you agree to the license terms and privacy notice.
- On the Express Settings page, click Customize.
- On the Install required components page, click Install.
- On the User sign-in page, select Federation with AD FS and then click Next.
- On the Connect to Azure AD page, enter the username and password for a user account that is a Global Administrator in your Office 365 organization , and then click Next.
- On the Connect your directories page, select the Active Directory forest that contains the Exchange organization you want to configure for hybrid deployment, and then enter the username and password for a user account that’s a member of the Enterprise Administrators group in that forest. Click Next.
- On the Domain and OU filtering page, select Sync all domains and OUs if you want to synchronize all of your on-premises Active Directory users to Office 365. If you want to select a specific organizational unit (OU), select Sync selected domains and OUs, and then select the Active Directory domains and OUs you want to synchronize. Click Next.
- On the Uniquely identifying your users page, make sure that Users are represented only once across all directories is selected, and then click Next.
- On the Filter users and devices page, make sure that Synchronize all users and devices is selected, and then click Next.
- On the Optional Features page, select Exchange hybrid deployment, and then click Next.
- On the AD FS farm page, select Configure a new Windows server 2016 AD FS farm.
- In the Certificate File field, browse to the third-party certificate that includes a subject alternative name (SAN) that matches the external FQDN of the AD FS server. This certificate needs to include a private key. In the Subject Name field, select the SAN you want to use, for example sts.domain.com. Click Next.
- On the AD FS Servers page, click Browse, select the name of the server where you’re installing Azure AD Connect with AD FS, and then click Add.
- On the Web application proxy servers page, click Browse, select the name of the server that will act as a web proxy for external connections, and then click Add.
- On the Proxy trust credentials page, enter the username and password of a user account that can access the certificate store on the AD FS server that contains the certificate you specified earlier in these steps, and then click Next.
- On the AD FS service account page, select Create a group Managed Service Account, enter the username and password for a user that’s a member of the Enterprise Admins group, and then click Next.
- On the Azure AD Domain page, select the domain that matches the custom domain that you added to your Office 365 organization and matches the User Principal Name users with which users will log in. For example, if you added the custom domain domain.com, and usernames are @domain.com, select domain.com from the list. Click Next.
- On the Ready to configure page, select Start the synchronization process as soon as the configuration completes, and then click Next.
- On the Configuration complete page, click Exit.
- Make sure that your firewall is configured to allow connections on TCP port 443 from external sources to your AD FS web proxy server.
- At this point, Azure AD Connect will synchronize your on-premises user accounts and their information to your Office 365 organization. Depending on how many accounts need to be synchronized, this might take a while.
Step4: Create Federation with Azure Active Directory
Remote into the Primary ADFS Server, Run the below cmdlets
Connect-MsolService
Set-MsolAdfsContext -Computer “adfsserver.domain.com”
Convert-MsolDomainToFederated -Domain “domain.com” -SupportMultipleDomain
If you have multiple userprincipalname, you have run the below cmdlets to federate with Azure AD.
Convert-MsolDomainToFederated -Domain “domain1.com” -SupportMultipleDomain
Convert-MsolDomainToFederated -Domain “domain2.com” -SupportMultipleDomain
Update-MsolFederatedDomain -Domain “domain1.com” -SupportMultipleDomain
Update-MsolFederatedDomain -Domain “domain2.com” -SupportMultipleDomain
Further reading ADFS Configuration Guide
Step5: Verify tenant configuration
To create a mailbox in the Exchange Online organization, do the following:
- Open Active Directory Users and Computers on an Active Directory domain controller in your on-premises organization.
- Expand the container or organizational unit (OU) where you want to create a new Active Directory user.
- Click Action in the menu bar, and then click New > User.
- Enter the required user information. Because this user will be associated with a test mailbox, we recommend that you clearly identify the user as such. For example, name the user “Test User”.
- In the User logon name field, provide the user name that the user should specify when logging into their user account. This user name, combined with the user principal name (UPN) in the drop-down box next to the User logon name field, makes up the Microsoft Online Identity of the user. The Microsoft Online Identity typically matches the user’s email address, and the domain suffix chosen should match the federated domain configured in Active Directory Federation Services. For example, testuser@domain.com. Click Next.
- Enter a password for the new user, specify any options you want to set, and then click Next.
- Click Finish.
- Run delta synchronization to synchronize the new user to the Office 365 organization using this PowerShell Cmdlet. Start-ADSyncSyncCycle -PolicyType Delta
- Log on to: Office 365 service administration portal
- Assign a E1 or E3 license to the new user.
Step6: Install Edge Transport server
The Edge Transport server role is typically deployed on a computer located in an Exchange organization’s perimeter network and is designed to minimize the attack surface of the organization. The Edge Transport server role handles all Internet-facing mail flow, which provides SMTP relay and smart host services for the on-premises Exchange organization. Use Edge Transport servers if you don’t want to expose internal Exchange 2016 Mailbox servers directly to the Internet.
If you already have an Edge Transport server deployed in your on-premises organization, you can skip this checklist step unless you’d like to install additional Edge Transport servers.
Step7: Configure Edge servers
After installing the Exchange 2016 Edge Transport server, or if you already have an Edge Transport server in your on-premises Exchange organization, you must configure the following services and parameters to enable the Edge Transport server to handle secure communications between the on-premises Exchange servers, clients, and Office 365. If you already have an Edge Transport Server, skip this step.
Follow additional guidelines to Edge Transport Server.
Further References on Edge Transport Server.
Step8: Configure DNS
| Hybrid requirement |
DNS record |
Record type |
Value |
| Required for all hybrid deployments |
autodiscover.domain.com |
CNAME or A |
If using CNAME DNS: mail.domain.com
If using Host A DNS: External IP address of an Exchange 2016 Mailbox server or firewall |
| Recommended as a best practice for all hybrid deployments |
SPF |
TXT |
v=spf1 include:spf.protection.outlook.com ~all |
| ADFS Public record |
sts.domain.com |
A |
Public IP address of the AD FS web proxy server or firewall |
| Internal record by editing Hosts File located %SystemRoot%\system32\drivers\etc\HOSTS of WAP server |
sts.domain.com |
A |
Internal IP address of the AD FS Servers |
Step9: Firewall Configuration
If your organization uses Office 365 and restricts computers on your network from connecting to the Internet, below you’ll find the endpoints (FQDNs, Ports, URLs, IPv4, and IPv6 address ranges) that you should include in your outbound allow lists to ensure your computers can successfully use Office 365.
Hybrid deployment configuration changes may require you to modify security settings for your on-premises network and protection solutions. Exchange 2016 Mailbox servers must be accessible on TCP port 443, and Edge Transport and Mailbox servers must be accessible on TCP port 25. Other Office 365 services, such as SharePoint Online and Lync Online, may require additional network security configuration changes. If you’re using Microsoft Threat Management Gateway (TMG) in your on-premises organization, additional configuration steps will also be needed to allow full Office 365 integration in the hybrid deployment.
Step10: Configure Exchange Web Services
The external fully qualified domain name (FQDN) of your Internet-facing Exchange 2016 Mailbox server needs to be configured on several virtual directories for a hybrid deployment. By completing this checklist step, the external URL on the Exchange Web Services (EWS), Outlook Address Book (OAB), Outlook Web App (OWA), Exchange Control Panel (ECP), and the Exchange ActiveSync (Microsoft-Server-ActiveSync) virtual directories will be reset to the external FQDN of your Internet-facing Exchange 2016 Mailbox server.
Follow additional guidelines to configure web services.
Further References on Web Services.
Step11: Configure MRS Proxy
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.
Get–WebServicesVirtualDirectory –ADPropertiesOnly | Where {$_.MRSProxyEnabled –ne $true} | Set–WebServicesVirtualDirectory –MRSProxyEnabled $true
Step12: Configure Exchange certificates
Digital certificates are an important requirement for secure communications between on-premises Exchange 2016 servers, clients, and Office 365. You need to obtain a certificate that will be installed on Mailbox and Edge Transport servers from a third-party trusted certificate authority (CA).
Before you can configure certificates on Exchange servers, you need to get a certificate from a trusted CA. Complete the following task on an Exchange 2016 Mailbox server if you need to generate a request for a new certificate for use with the hybrid deployment.
Follow additional guidelines to install certificates.
Further References on Exchange Certificates.
Step13: Run Hybrid Configuration wizard
The Hybrid Configuration wizard helps you establish your hybrid deployment by creating the HybridConfiguration object in your on-premises Active Directory and gathering existing Exchange and Active Directory topology configuration data. The Hybrid Configuration wizard also enables you to define and configure several organization parameters for your hybrid deployment, including secure mail transport options.
You can use the Hybrid Configuration wizard in the EAC on an Exchange 2016 server in your on-premises organization to create and configure the hybrid deployment.
- In the EAC on an Exchange 2016 server in your on-premises organization, navigate to the Hybrid, In the Hybrid node, click Configure to enter your Office 365 credentials.
At the prompt to log in to Office 365, select sign in to Office 365 and enter the account credentials. The account you log into needs to be a Global Administrator in Office 365.
- Click Configure again to start the Hybrid Configuration wizard.
- On the Microsoft Office 365 Hybrid Configuration Wizard Download page, click Click here to download wizard. When you’re prompted, click Install on the Application Install, Click Next, and then, in the On-premises Exchange Server Organization section, select Detect a server running Exchange 2013 CAS or Exchange 2016. The wizard will attempt to detect an on-premises Exchange 2016 server. If the wizard doesn’t detect an Exchange 2016 server, or if you want to use a different server, select Specify a server running Exchange 2013 CAS or Exchange 2016 and then specify the internal FQDN of an Exchange 2016 Mailbox server.
- In the Office 365 Exchange Online section, select Microsoft Office 365 and then click Next.
- On the Credentials page, in the Enter your on-premises account credentials section, specify a different set of credentials, specify the username and password an Active Directory account you want to use. Whichever selection you choose, the account used needs to be a member of the Enterprise Admins security group.
- In the Enter your Office 365 credentials section, specify the username and password of an Office 365 account that has Global Administrator permissions. Click Next.
- On the Validating Connections and Credentials page, the wizard will connect to both your on-premises organization and your Office 365 organization to validate credentials and examine the current configuration of both organizations. Click Next when it’s done.
- On the Hybrid Features page, select Full Hybrid Configuration and then click Next.
- On the Hybrid Domains, select the domain or multiple accepted domains you want to include in your hybrid deployment. In most deployments you can leave the Auto Discover column set to False for each domain. Only select True next to a domain if you need to force the wizard to use the Autodiscover information from a specific domain.
- Click Next.
- On the Federation Trust page, click Enable and click then Next.
- On the Domain Ownership page, click Click copy to clipboard to copy the domain proof token information for the domains you’ve selected to include in the hybrid deployment. Open a text editor such as Notepad and paste the token information for these domains. Before continuing in the Hybrid Configuration wizard, you must use this info to create a TXT record for each domain in your public DNS.
- Click Next after the TXT records have been created and the DNS records have replicated.
- On the Hybrid Configuration page, select the Configure my Edge Transport servers for secure mail transport option to configure your on-premises Edge Transport servers for secure mail transport with Office 365. Click Next.
- If you want Office 365 to send all outbound messages to external recipients to your on-premises transport servers, select the Enable centralized mail transport check box in the More options section.The on-premises transport servers will be responsible for delivering the messages to external recipients. This approach is helpful in compliance scenarios where all mail to and from the Internet must be processed by on-premises servers. If this check box is not selected, Office 365 will bypass the on-premises organization and deliver messages to external recipients directly using the recipient’s external DNS settings.You select this option if you want to use your own Spam Filter.
- On the Edge Transport Servers page, select the Edge Transport server you want to configure for secure mail transport. click Next. In this section, you have to provide the public IP addresses of edge servers or public FQDN of edge servers.
- On the Transport Certificate page, in the Select a reference server field, select Exchange 2016 Mailbox server that has the certificate you configured earlier in the checklist.
- In the Select a certificate field, select the certificate to use for secure mail transport. This list displays the digital certificates issued by a third-party certificate authority (CA) installed on the Mailbox server selected in the previous step. Click Next.
- On the Organization FQDN page, enter the externally accessible FQDN for your Internet-facing Exchange 2016 Mailbox server. Office 365 uses this FQDN to configure the service connectors for secure mail transport between your Exchange organizations. For example, enter “mail.domain.com”. Click Next.
- The hybrid deployment configuration selections have been updated, and you’re ready to start the Exchange services changes and the hybrid deployment configuration. Click Update to start the configuration process. While the hybrid configuration process is running, the wizard displays the feature and service areas that are being configured for the hybrid deployment as they are updated.
- When the wizard has completed all of the tasks it can perform automatically, it’ll list any tasks that you need to address manually before your hybrid deployment configuration is complete.
- The wizard displays a completion message and the Close button is displayed. Click Close to complete the hybrid deployment configuration process and to close the wizard.
- You’ll probably need to configure the Receive connector on your Edge Transport server by doing the following.
Open the Exchange Management Shell on your Exchange 2016 Edge Transport server.
Run the following command to list the Receive connectors on your Edge Transport server. Make note of the Receive connector that’s listening on TCP port 25.Get-ReceiveConnectorRun the following command to configure the Receive connector. Replace the name of the Receive connector in the following command with the name of the connector you identified in the previous step.Set-ReceiveConnector “Edge\Default internal receive connector Edge” -TlsDomainCapabilities mail.protection.outlook.com:AcceptOorgProtocol -Fqdn “mail.domain.com”24. Additional Steps for Centralised Mailflow or Route all inbound-outbound emails through on-premises servers. You need to enable remote mailbox using enable-remotemailbox and set target address using set-remotemailbox for this each mailbox as user1@domain.mail.onmicrosoft.com where domain is your domain name in Office 365. You must run full sync after this on the AAD Connect Server. You must run start-edgesynchronization –Server EXCH2016MailboxServer on the Edge Transport 2016 Server
Step14: Send Connector and Receive Connector Configuration on the on-premises server
Use the EAC to create an Internet Send connector
- In the EAC, navigate to Mail flow > Send connectors, and then click Add . This starts the New Send connector
- On the first page, enter the following information: Name: To Office 365 and Type: Internet When you are finished, click Next.
- On the next page, verify that MX record associated with recipient domain is selected. When you are finished, click Next.
- On the next page, In the Address space section, click Add . In the Add domain dialog box that appears, in Fully Qualified Domain Name (FQDN), enter an asterisk (*), and then click Save. This value indicates that the Send connector applies to messages addressed to all external domains. When you are finished, click Next.
- On the next page, in the Source server section, click Add . In the Select a Server dialog box that appears, select one or more Edge Transport Servers if you route email through Edge Server if not enter mailbox servers that you want to use to send mail to the Internet. If you have multiple Mailbox servers in your environment, select the ones that can route mail to the Internet. If you have only one Mailbox server, select that one. After you’ve selected at least one Mailbox server, click Add, click OK, and then click Finish.
Use the EAC to Create a Receive Connector to Receive Secure Messages from a Partner
- In the EAC, navigate to Mail flow > Receive connectors. Click Add to create a new Receive connector.
- On the New receive connector page, specify a name for the Receive connector and then select Frontend Transport for the Role. Since you are receiving mail from a partner in this case, we recommend that you initially route mail to your front end server to simplify and consolidate your mail flow.
- Choose Partner for the type. The Receive connector will receive mail from a trusted third party.
- For the Network adapter bindings, observe that All available IPV4 is listed in the IP addresses list and the Port is 25. (Simple Mail Transfer Protocol uses port 25.) This indicates that the connector listens for connections on all IP addresses assigned to network adapters on the local server. Click Next.
- If the Remote network settings page lists 0.0.0.0-255.255.255.255, which means that the Receive connector receives connections from all IP addresses, click Remove 0.0.0-255.255.255.255 to remove it. Click Add EOP IP Addresses, and Datacentre IP Addresses add the IP address for your partner’s server, and click Save.
- Click Finish to create the connector.
- Run the below Cmdlets in Mailbox Server
Get-ReceiveConnector “Inbound from Office 365“ | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “ms-Exch-SMTP-Accept-Any-Recipient”
- Verify Receive Connector using below Cmdlets
Get-ADPermission -Identity “ Inbound from Office 365” -User “NT AUTHORITY\ ANONYMOUS LOGON” | where {($_.Deny -eq $false) -and ($_.IsInherited -eq $false)} | Format-Table User,ExtendedRights
- Add Datacentre IP Addresses using this Link
- Troubleshoot using this link
Step14: Create a test mailbox
You can use the Office 365 Mailbox wizard in the EAC on an Exchange server to create a test mailbox in Office 365. If you want to create more than one test mailbox, you’ll have to use this wizard for each test mailbox. You can’t use the wizard to create multiple test mailboxes.
- Log into the EAC on an on-premises Exchange 2016 server.
- In the EAC, navigate to Enterprise > Recipients > Mailboxes.
- Expand the menu at the Add control and select Office 365 mailbox.
- On the New Office 365 mailbox page, specify the following settings:
- First Name Type the first name of the new user.
- Initials Type the initials of the new user.
- Last Name Type the last name of the new user.
- User logon name Type the user logon name of the new user and select the primary SMTP domain used for your other on-premises users. For example, @domain.com.
- Mailbox type Choose the type of mailbox to create. For example, User mailbox.
- Password Type the password.
- Confirm password Retype the password.
- Make sure the Create an archive mailbox check box is not selected.
- Click Save to continue.
- Start-ADSyncSyncCycle -PolicyType Delta
Step15: Move or create mailboxes
You can use the remote move migration wizard in the Office 365 tab in the Exchange admin center (EAC) on an Exchange server to move existing user mailboxes in the on-premises organization to Office 365:
- Open the EAC and navigate to Office 365 > Recipients > migration.
- Click Add and select Migrate to Exchange Online.
- On the Select a migration type page, select Remote move migration and then click Next.
- On the Select the users page, click Add , select the on-premises users to move to Office 365 and click Add, and then click OK. Click Next.
- On the Enter the Windows user account credential page, enter the on-premises administrator account name in the On-premises administrator name text field and enter the associated password for this account in the On-premises administrator password text field. For example, “Domain\administrator” and a password. Click Next.
- On the Confirm the migration endpoint page, verify that the FDQN of your on-premises Mailbox server is listed when the wizard confirms the migration endpoint. For example, “mail.domain.com”. Click Next.
- On the Move configuration page, enter a name for the migration batch in the New migration batch name text field. Use the down arrow to select the target delivery domain for the mailboxes that are migrating to Office 365. In most hybrid deployments, this will be the primary SMTP domain used for both on-premises and Office 365 mailboxes. For example, user@domain.com. Verify that the Move primary mailbox along with archive mailbox option is selected, and then click Next.
- On the Start the batch page, select at least one recipient to receive the batch complete report. Verify that the Automatically start the batch and Automatically complete the migration batch options are selected. Click New.
- While the mailboxes are being moved, you will see a status of Synching in the migration status for each mailbox moved to Office 365. After the mailbox move request reaches a status of Completed, the mailbox migration process is complete.
Step16: Test hybrid deployment connectivity
Testing the external connectivity for critical Exchange 2016 and Office 365 features is an important step in ensuring that your hybrid deployment features are functioning correctly. The Microsoft Remote Connectivity Analyzer is a free online web service that you can use to analyze, and run tests for, several Exchange 2016 and Office 365 services, including Exchange Web Services, Outlook, Exchange ActiveSync, and Internet email connectivity.
Like this:
Like Loading...
