Exchange Online migration with the Hybrid Agent

Mailbox Migration

Test Connection

Once the hybrid connection has been set up, you need to test a number of features. First, check email transport by sending messages back and forth between local and online mailboxes. You will also want to test accessibility from an external source.

Next, try creating mailboxes. You can now create mailboxes for Exchange Online in the local EAC (Figure 3), although you may experience a short delay before the account becomes available in Office 365. First, you need to assign a license to the account so that the user can log in to the mailbox. Second, migrate some mailboxes in Office 365 from your local environment to Exchange Online. To do this, go to the Exchange Online EAC and select recipients | migration and then Migrate to Exchange Online . Third, test the client experience by checking the available/busy information for mailboxes from different environments in a new event.

Figure 3: After successfully connecting the environments, mailboxes in Exchange Online can be set up using the local environment.

Between Two Worlds

Admins need to be aware that the two Exchange organizations are independent of each other in terms of configuration. In the EAC, you can quickly switch between the two worlds with the Enterprise and Office 365 tabs. Basically, policies such as the Retention Policy, OWA Policy, or Mobile Device Policy need to be created and configured separately. The Organization Configuration Transfer (OCT) wizard helps you migrate the settings. The first OCT version was released in June 2018 and only supported the guidelines at that time. The next version (released in October 2018) added features, such as Active Sync Device Access Rule, Address List, and Policy Tip Config.

The first version only supported the initial transfer; in other words, if the wizard saw a setting with an identical name, it was just ignored. The second version now overwrites settings in Exchange Online. Although this is not the same as synchronization, it is an easy way to transfer settings quickly. OCT requires the latest cumulative update locally and supports Exchange Server 2010 or newer. OCT is part of the HCW; you select the transfer during hybrid configuration.

The Last Exchange Server Standing

Once all the mailboxes have been migrated to Exchange Online, you can uninstall the last Exchange server, but only if you will not be synchronizing the users with Azure Active Directory (AD) Connect, which integrates your local directories into Azure AD, giving users a single identity. Because it is not a prerequisite for the use of a hybrid configuration, I won't discuss it in detail here.

If you use this function, you need an Exchange server to maintain the local Exchange attributes. If no local Exchange server is available, the Exchange extensions for the AD objects, which are essential for smooth hybrid operation with Office 365, are missing. As a result of this requirement, you need to continue to import Exchange updates, including potential schema extensions.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy ADMIN Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Exchange Server through 2025
    The next generation of Exchange 2019 was announced for the second half of 2021, but the release plan was revoked in 2022, and the next Exchange was postponed until 2025. We take an in-depth look at the current timetable.
  • Safely integrating and running Office 365
    A few simple steps can greatly improve the security of cloud applications through encryption, multifactor authentication, and other safeguards.
  • Exchange Web Services for Mailbox Access
    Exchange Web Services (EWS) is an important interface that lets applications access Exchange content. You can access the EWS mailbox via PowerShell or create your own tools.
  • Use PowerShell to manage Exchange Online
    Exchange Online in Office 365 can be managed just like its local counterpart with similar, sometimes identical, PowerShell cmdlets.
  • The Azure Arc multicloud and on-premises management platform
    The Azure Arc cloud service supports centralized management of Windows and Linux servers, Kubernetes clusters, and SQL servers that are not themselves running in Azure, extending Azure management capabilities to servers in traditional data centers or any other cloud environment. We show you how to get Azure Arc up and running and look at its key features.
comments powered by Disqus
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs

Support Our Work

ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.

Learn More”>


		<div class=