| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| enterprise | Cross Tenant Onedrive Migration Step1 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/cross-tenant-onedrive-migration-step1.md | This article details Step 1 in a solution designed to complete a Cross-tenant On - **Microsoft SharePoint Online Powershell**. Confirm you have the most recent version installed. If not, [Download SharePoint Online Management Shell from Official Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=35588). - Be a SharePoint Online admin or Microsoft 365 Global admin on both the source and target tenants +>[!IMPORTANT] +>Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + ### Connect to both tenants 1. Sign in to the SharePoint Management Shell as a SharePoint Online admin or Microsoft 365 Global admin. |
| enterprise | Cross Tenant Onedrive Migration Step6 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/cross-tenant-onedrive-migration-step6.md | This is Step 6 in a solution designed to complete a Cross-tenant OneDrive migrat - **Step 6: [Start a Cross-tenant OneDrive migration](cross-tenant-onedrive-migration-step6.md)** - Step 7: [Post migration steps](cross-tenant-onedrive-migration-step7.md) +>[!IMPORTANT] +>Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. + Now you're ready to start your OneDrive migration. Before starting any cross-tenant migration, do the following steps. 1. Ensure you have verified the compatibility status. If you see a status of either **Compatible** or **Warning** on your source tenant, you can continue. Run: |