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 pre-existing 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.
|
Guest User Account Migration Considerations
|
|
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 in case an original account for this guest user account is already a member of the target tenant. It is not recommended to use a matching task to pair these accounts.
- 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.
Hybrid Account Migration
On Demand Migration integrates with Quest Migration Manager to process on-premises users and groups synchronized with Azure AD (hybrid accounts).
|
|
NOTE: Migration of Dynamic Distribution groups is not supported. |
Use Hybrid widget on the dashboard to configure and monitor connections to your on-premises environment.
Basic hybrid account migration workflow consists of the following steps:
Integration with Migration Manager for AD
Before you start hybrid account migration make sure the Quest Migration Manager for Active Directory is already deployed as described in Deploying Migration Manager for Active Directory.