Chat now with support
Chat with Support

Reference Materials for Migration 8.14 - Migrating to Microsoft Office 365

Introduction BeforeYou Begin Migration to Microsoft Office 365 Post-Migration Activities Tracking the Migration Progress Hybrid Migration Scenarios Advanced Migration Topics Troubleshooting Migration to Microsoft Office 365

Establish Mail Flow to Source Exchange Organization

Establish Mail Flow to Source Exchange Organization

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.

  • Add a SMTP address space with the source.local domain.

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.

On-Premises Directory Migration

On-Premises Directory Migration

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

  • Mail-enabled users that have the targetAddress attribute pointing to source mailboxes will be created.
  • Mail sent to the newly created mail-enabled users using on-premises Global Access List (GAL) will be delivered to the corresponding source mailboxes

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:

  1. Open the Migration Manager for Active Directory console.

Note: Ensure that the current open project is not the one that is intended for migration to Microsoft Office 365.

  1. 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.

  2. 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.

  3. 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:

    • Specify Source Scope: The Disable target accounts option must be cleared so that migrated accounts will be able to access target Active Directory domain as well as Microsoft Office 365 with the same password through SSO.
  • Set Security Settings:
  • The Synchronize passwords option must be selected.
  • Under User Principal Name handling, set the domain suffix of the UPNs to the appropriate domain matching federated domain used in hybrid.
  • Advanced Options:Select Use custom add-in and specify add-in located at <Migration Manager installation folder>\Active Directory\CopyTargetAddress.xml.
  • Specify Exchange Options:
  • Select the Mail-enabled users option
  • Specify the target SMTP address template (e.g. target.local)
  • Specify the source SMTP address template (e.g. source.local)

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.

  1. Start the configured directory synchronization job as described in Starting and Stopping Directory Synchronization topic of the Migration Manager for Active Directory User Guide, and wait until initial synchronization completes.

How do you verify that step worked

  1. Create a test mailbox in the target on-premises organization.
  2. Using GAL, send a test message to any mail-enabled user that was migrated by Directory Synchronization Agent (DSA).
  3. Open the source user's mailbox and check that the message is delivered successfully.
  4. Reply that message and ensure that it arrived to the target mailbox.
  5. Repeat the above steps using any mailbox outside your organization to check that original and reply messages are delivered successfully.

Additional information

For details, see the following topics in the Migration Manager for Active Directory User Guide:

  • Pre-Migration Activities
  • Directory Synchronization

On-Premises Mailbox Migration

On-Premises Mailbox Migration

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.

User Matching

User Matching

Match users in the source Active Directory domain with users in the target Microsoft Office 365 tenant.

What will you achieve

  • Mailboxes from the source Active Directory domain will be matched with the corresponding Microsoft Office 365 mail users.
  • The Location property will be populated for the Microsoft Office 365 users.

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:

  1. Install a Directory Migration Agent instance if none installed already.
  2. Configure migration pair of source Active Directory domain and target Microsoft Office 365 tenant.
  3. Specify the mail redirection domain for the migration pair. When choosing mail redirection domain, take the following into account:
    • This domain must be accepted in on-premises domain only
    • The domain must not be accepted in Microsoft Office 365.

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.

  1. Select the Empty Active Directory to Microsoft Office 365 mapping template for the migration pair.
  2. Create a static collection i including all objects from the source Active Directory domain.
  3. Start a new migration task with the following options:
    • The Create new objects on target option cleared
    • The Merge into existing objects on target option selected
    • The UPN suffix set to the corresponding federated domain in Microsoft Office 365

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.

Related Documents