From 477c43723ed06a34ac7c3c93fb13287f6f335ee6 Mon Sep 17 00:00:00 2001 From: Sriraman M S <45987684+msbemba@users.noreply.github.com> Date: Mon, 24 Jul 2023 19:17:13 +0530 Subject: [PATCH 1/2] Update cross-tenant-onedrive-migration-step5.md Moved the compatibility step to the top as it needs to be checked first. Fixes https://github.com/MicrosoftDocs/microsoft-365-docs/issues/12482 --- .../cross-tenant-onedrive-migration-step5.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md b/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md index 03455a906ce..0e271f810e9 100644 --- a/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md +++ b/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md @@ -29,6 +29,28 @@ This is Step 5 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) +## Verify cross-tenant compatibility status + +Before starting any cross-tenant migrations, make sure that both SharePoint database schemas are up to date and compatible between source and target. + +To perform this check, run the below cmdlet on your Source tenant. + +```powershell +Get-SPOCrossTenantCompatibilityStatus -PartnerCrossTenantHostURL [Target tenant hostname] + +Get-SPOCrossTenantCompatibilityStatus -PartnerCrossTenantHostURL https://m365x12395529-my.sharepoint.com +``` + +- If the tenant status shows as **Compatible** or **Warning**, you can then proceed with the next step of starting cross-tenant migrations. +- If the tenant status shows as **Incompatible**, your tenants will need to be patched/updated to ensure compatibility. + +|Status|Can proceed with migration| +|---|---| +|Compatible|Yes| +|Warning|Yes| +|Incompatible|No| + + ## Create the identity mapping file In this step of the cross-tenant migration process, you're going to create a single CSV (comma separated values) file that contains the mapping of the users and groups on the source tenant to their corresponding users and groups on the target tenant. From e5e0a44f977921d2d97153748486433bd6b1b99d Mon Sep 17 00:00:00 2001 From: Sriraman M S <45987684+msbemba@users.noreply.github.com> Date: Mon, 24 Jul 2023 20:59:53 +0530 Subject: [PATCH 2/2] Update microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../enterprise/cross-tenant-onedrive-migration-step5.md | 1 - 1 file changed, 1 deletion(-) diff --git a/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md b/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md index 0e271f810e9..5c2b800301f 100644 --- a/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md +++ b/microsoft-365/enterprise/cross-tenant-onedrive-migration-step5.md @@ -50,7 +50,6 @@ Get-SPOCrossTenantCompatibilityStatus -PartnerCrossTenantHostURL https://m365x12 |Warning|Yes| |Incompatible|No| - ## Create the identity mapping file In this step of the cross-tenant migration process, you're going to create a single CSV (comma separated values) file that contains the mapping of the users and groups on the source tenant to their corresponding users and groups on the target tenant.