Migration to a Destination Multi-Geo Tenant
The following sections detail where Fly will create the Microsoft 365 objects in the destination Microsoft 365 multi-geo tenant for each migration type.
Exchange Online Migration
If the destination is a multi-geo tenant, make sure the destination mailboxes configured in migration mappings already exist before the migration.
Microsoft 365 Groups Migration
- If you define a specific location for destination Groups in the connection, the Groups will be created in that location during the migration.
- > ***Note**: If the connection is configured with only a delegated app profile, Groups cannot be created in that location. You can change to use a custom delegated app profile to create Groups. Refer to [Delegated App Profile Permissions](#missing-link) for details.
- If you do not define any location, the Groups will be created as follows according to your source tenant:
- If your source tenant is a multi-geo tenant, Fly will create the Groups in the same destination location as the source.
- If your source tenant is not a multi-geo tenant, Fly will create the Groups in the central location of the destination tenant.
Microsoft Teams Migration
- If you define a specific location for destination Teams in the connection, the Teams will be created in that location during the migration.
> ***Note**: The destination service account and the migration time will be displayed respectively as the sender and the send time of the migrated channel conversation messages in the destination. The source sender and send time of source conversation messages will be migrated as the message content.
> ***Note**: If the connection is configured with only a delegated app profile, Teams cannot be created in that location. You can change to use a custom delegated app profile to create Teams. Refer to [Delegated App Profile Permissions](#missing-link) for details.
- If you do not define any location, the Teams will be created as follows according to your source tenant:
- If your source tenant is a multi-geo tenant, Fly will create the Teams in the same destination location as the source.
- If your source tenant is not a multi-geo tenant, Fly will create the Teams in the central location of the destination tenant.
In the two cases above, if the destination location is the central location of the destination tenant and you provide an app profile in the destination connection, Fly can keep the original sender and send time of source conversation messages to the destination.
OneDrive Migration
Fly does not support creating OneDrive sites in multi-geo tenants. If the destination is a multi-geo tenant, we recommend that you pre-provision all OneDrive sites using the PowerShell: before the migration. An alternative approach is for each user to log into OneDrive to initiate the site collection creation.
SharePoint Online Migration
Fly will create the site collections in the same location as the SharePoint Online admin center URL defined in the destination service account or app profile. If both are provided, the site collections will be created in the location of the SharePoint Online admin center URL defined in the service account.
*Note: Make sure the SharePoint Online admin center URL and destination site collection URLs in the migration mappings are in the same location.
