Since additional domains (for instance, source.local) will be used for mail redirection purposes, the corresponding Exchange connectors should be set up to establish proper mail flow.
Mail redirection from target to source on-premises organization
In order to enable mail redirection from the target to the source on-premises organization using @source.local namespace, add a new send connector on the target on-premises Exchange server with the following settings:
Specify the mail delivery options depending on your organization specifics and Exchange Server version. For details, please refer to Microsoft documentation available here.
Mail redirection from Microsoft Office 365 to source organization
Enabling mail redirection from Microsoft Office 365 to the source organization depends on the domain suffix that will be used for the cloud-related mail redirection purposes. If the domain name is publicly available (MX records are registered in public DNS and point to source Exchange server) no additional connectors are required.
In case the domain suffix is not publicly available, the corresponding connector in Microsoft Office 365 should be created to relay mail to the on-premises target Exchange server which, in its turn, should relay mail to the source Exchange server.
Migrate users from the source Active Directory domain to the target Active Directory domain (the one that is synchronized with Microsoft Office 365).
What will you achieve
How do you do that
Configure directory synchronization from the source Active Directory domain to the target Active Directory domain so that the target GAL is populated with the objects from the source domain.
For that, take the following steps:
|
Note: Ensure that the current open project is not the one that is intended for migration to Microsoft Office 365. |
Install a new Directory Synchronization Agent instance if none installed already. For details, see the Agent Manager topic of the Migration Manager for Active Directory User Guide.
Create a domain pair of the source Active Directory domain and the target Active Directory domain. For information on how to do that, see the Domain Pairs section in the Migration Manager for Active Directory User Guide.
Configure a new synchronization job for the domain pair according to the Configuring the Synchronization Job topic of the Migration Manager for Active Directory User Guide. Set the following specific options for the synchronization job:
|
Note: Since the source.local redirection domain will be also used in Microsoft Office 365, it should be publicly available, or the corresponding connectors should be created in Microsoft Office 365 to establish mail flow. |
How do you verify that step worked
Additional information
For details, see the following topics in the Migration Manager for Active Directory User Guide:
If you need to migrate some of mailboxes to the on-premises part of the target hybrid, you can do that now. For detailed information on how to do that, refer to Migration Manager for Exchange User Guide.
|
Note: Before performing on-premises mailbox migration in Migration Manager for Exchange console, ensure that the current open project is not the one that is intended for migration to Microsoft Office 365. |
Match users in the source Active Directory domain with users in the target Microsoft Office 365 tenant.
What will you achieve
How do you do that
Configure a new migration from the source Active Directory domain to Microsoft Office 365 in Migration Manager for Active Directory (Microsoft Office 365) console to match accounts.
Set up a new migration as follows:
|
Note: The source.local domain used for Directory Synchronization can be used as redirection domain if it is publicly available or corresponding connectors exist in Microsoft Office 365 tenant. If centralized mail transport is enabled in your hybrid deployment, you can use the existing on-premises connector for this purpose. |
How do you verify that step worked
To ensure that the above procedure succeeded, check that the Location property is populated for the Microsoft Office 365 users.
Additional information
For details, see the Provisioning User Accounts in Office 365 section.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy