Skip to content

Update cross-tenant-onedrive-migration.md #13879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vgaddam-pm wants to merge 1 commit into from
Closed

Update cross-tenant-onedrive-migration.md #13879

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions microsoft-365/enterprise/cross-tenant-onedrive-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,15 @@ Each OneDrive account can have a maximum of 5 TB of content or 1 million items.
>
>If you attempt to migrate any OneDrive site that exceeds the five-terabyte quota, the transfer fails.

## Multi-Geo

You can migrate sites directly into individual satellite geo instances as needed. When working with multi-geo environments additional planning and configuration will need to be considered.

- Trust configurations will need to be established between all source and target instances that will be part of the migration.
- The identity mapping file must be uploaded to every target instance.
- When migrating in multi-geo environments, each source instance will be subject to the 4000 queue size limit regardless of the number of target tenants.
- Establishing multiple trusts allows you to move sites directly into a geo instance of choice.

## Permissions

All users and groups included in the identity mapping file that you uploaded to the target tenant maintain permissions in the target tenant related to the migrated OneDrive site.
Expand Down