立即与支持人员聊天
与支持团队交流

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 Accounts

Caution: Don’t start the migration before the discovery task is finished.

When the matching is done, it is time to migrate source accounts that do not have the pairs on the target tenant. Create a new migration task:

  1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the account migration Dashboard, go to step 3.
  2. Click Accounts widget.
  3. Click Accounts.
  1. Select accounts / groups you want to migrate. In case you are planning to migrate Microsoft 365 Groups including content, it is recommended to perform migration using Teams as described in Migrating Groups

TIP: Use search, filtering or collections to quickly navigate through the list of accounts.

  1. Click Migrate Accounts and provide vanity domain name instead of default *.onmicrosoft.com. Typically it is a domain name of your organization.

IMPORTANT: The custom domain name must be set up on the target tenant. See Quickstart: Add a custom domain name to Azure Active Directory for details.

  1. Click Next to proceed.
  2. Schedule when the task will be started. See for details. Click Next to view the task summary.
  3. Check selected options and name the task. Click Finish to save or start the task depending on schedule option selected.

The migration task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

IMPORTANT: On Demand Migration does not synchronize end-user passwords as part of the data migration process. The migration administrator will need to reset or synchronize end-user passwords from the source tenant to the target tenant using native Office 365 tools or third-party Single Sign On tools.

Preferred Data Location

Each account may be assigned a preferred data location property in Azure Active Directory. During account migration the property is migrated from source to tenant. If the account preferred data location is set in the source then the same setting will be migrated to the target. If the preferred data location is not set in the source then it will not be set on the target. This works for General Tenant to Multi-Geo Tenant and Multi-Geo Tenant to Multi-Geo Tenant migrations.

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.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级