Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration Troubleshooting Finalizing the Migration

Migrating distribution lists with group delegations

On Demand migrates distribution lists with group delegations (SendAs and SendOnBehalf). Scenarios where the distribution list in the target exists or does not exist, exists and does or does not have group delegations, are all supported. When the distribution list with group delegations exists in the target then only newly added group delegations are migrated, group delegations are ignored if anything is deleted at the source. Existing SendAs and SendOnBehalf group delegations on the target, either preexisting before On Demand migration or migrated by On Demand will be left intact and merged with the one migrated from the source.

Objects are migrated as follows:

  Mail User Mail Box Mail Enabled Security Group Distribution List
SendAs Y Y Y  
SendOnBehalf Y Y Y Y

 

NOTE: Microsoft does not support these objects in group delegations so they do not apply to the migration.

  • For SendAS: AAD User, External/Guest User, Distribution List, Security Group
  • For SendOnBehalf: AAD User, External / Guest User, Security Group

 

Guest User Migration

TIP: Guest user accounts have specific icon to distinguish them from the domain members.

On Demand migration can process all guest user types supported by Microsoft.

Before adding a guest user account to the migration task, please consider the following:

  • Guest user account cannot be migrated if an original account for this guest user is already in the target tenant. The guest user account should be matched but not migrated.
  • Guest user account cannot be migrated in case a guest user account of the same original account is already in the target tenant. To update the target guest user account properties create a matching task to pair these guest user accounts and then migrate the source guest user account again
  • Guest user account cannot be migrated in case the invitation procedure in source domain is not finished yet. In case acceptance procedure was skipped (this case is deprecated now, but such guest users still exist), and the acceptance status is empty, guest user can be migrated successfully.

Domain Coexistence

Mergers and acquisitions are often accompanied by the unification of brands and corporate identities, including the unification of email addresses. However, the full transition from source to target tenant might take a considerable amount of time. To close this gap, On Demand Migration offers the domain coexistence services, allowing your employees to send mail from new addresses and access cross-tenant data before the migration is finished. The following services are currently available on account migration dashboard:

  • Address Rewrite Service seamlessly changes the source users' email flow, as if they're already fully migrated to the target tenant. The outgoing mail addresses are substituted with the target ones, while all incoming mail is automatically redirected to the source mailbox. The address rewriting can be started once the account is matched or migrated, giving you time to prepare and migrate mailboxes without a rush. Address Rewrite Service requires additional licensing.
  • Calendar Sharing allows users from the source and target tenants to see each other's free/busy information.

Address Rewrite Service

Address Rewrite Service substitutes the "From", "To" , and "Cc" addresses in the outgoing emails with the addresses from the target or source tenant depending on selected address rewriting scenario. All incoming mail is automatically redirected to the source or target mailbox according to specified mail forwarding direction. You can specify the users that are processed by the service, for example, only turn it on for Sales and Marketing team members. Address Rewrite Service requires additional licensing.

IMPORTANT: The service only works with accounts that have pairs in the target tenant. Mailbox provisioning is not required, mail users are also supported. Check the documentation on matching or migrating accounts.

Basic Address Rewriting workflow consists of the following steps:

# Step
1 Select Scenario for Address Rewriting
2 Provision Address Rewrite Service
3 Add mailboxes to address rewriting
4 Optionally: add Address Rewrite Service's IP address to the target DNS SPF record
5 Enable address rewriting. You can disable address rewriting at any time or turn off address rewriting for individual mailboxes
Address Rewrite Service Workflow

Address Rewrite Service is intended for creating a coexistence space for domains in which all the email messages coming from the source or target mail domain will look alike they was send from the unified mail domain according the selected settings. Address Rewrite Service will take all the necessary steps for creating this coexistence space in Exchange online environment including creating and managing all necessary connectors, mail flow rules, mail-enabled users and groups both in source and target environments, leaving on behalf of administrator only adding or removing source mail user to this coexistence space and activating / deactivating Address Rewrite Service.

The basic mail message flow in domain coexistence with Address Rewrite Service looks like:

Unified mail domain on the target tenant

  1. When user sends an email as user@source domain mail user it redirected to Address Rewrite Service server in case it is addressed to the external recipients.
  2. Address Rewrite Service receives email from user@source domain, check mail user eligibility to make address rewriting and then process it by rewriting @source mail domain to @target mail domain for every address of users added to coexistence space. These addresses in "From", "To" and "Cc" of the email message are rewritten for all external recipients. Then Address Rewrite Service pass the processed email message to target Exchange Online environment. Internal recipients that reside in source receive this email message with unchanged addresses.
  3. Target Exchange Online sends message to external recipients as it was sent by user from @target mail domain, all addresses of users added to coexistence scope in "From", "To" and "Cc" are rewritten for external recipients.
  4. External recipient doesn’t aware about @source and replies (or create a new email) to the @target mail user.
  5. When the reply or a new mail arrives to target mail domain it will be forwarded to the source. Source recipient gets message as it was natively forwarded from target Exchange online environment from corresponding user@target email user

Unified mail domain on the source tenant

  1. When user sends an email as user@target domain mail user, it redirected to Address Rewrite Service server in case it is addressed to the external recipients.
  2. Address Rewrite Service receives email from user@target domain, check mail user eligibility to make address rewriting and then process it by rewriting @target mail domain to @source mail domain for every address of users added to coexistence space. These addresses in "From", "To" and "Cc" of the email message are rewritten for all external recipients. Then Address Rewrite Service pass the processed email message to source Exchange Online environment. Internal recipients that reside in source receive this email message with unchanged addresses.
  3. Source Exchange Online sends message to external recipients as it was sent by user from @source mail domain, all addresses of users added to coexistence scope in "From", "To" and "Cc" are rewritten for external recipients.
  4. External recipient doesn’t aware about @target and replies (or create a new email) to the @source mail user.
  5. When the reply or a new mail arrives to source mail domain it will be forwarded to the target. Target recipient gets message as it was natively forwarded from source Exchange online environment from corresponding user@source mail user

TIP: If Exchange Server Integration failed, click Try to fix button and Quest try to help you resolve the issue.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation