Skip to content

Commit e63fabd

Browse files
authored
Update cross-tenant-onedrive-migration-step6.md
Add note about -ValidationOnly parameter
1 parent a5bf41a commit e63fabd

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

microsoft-365/enterprise/cross-tenant-onedrive-migration-step6.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,6 +67,15 @@ To Schedule a migration for a later time, you can use and append the previous co
6767

6868
These commands can be useful when planning bulk batches of OneDrive migrations. You can queue/migrate up to 4,000 OneDrive migrations per batch. If your user count exceeds 4,000, create separate batches, and schedule them to run once the current batch is close to completion.
6969

70+
To run our pre-checks on the site without actually migrating, you can use and append the command with the -ValidationOnly parameter as seen below:
71+
72+
```Powershell
73+
Start-SPOCrossTenantUserContentMove -SourceUserPrincipalName DiegoS@M365x016651.OnMicrosoft.com -TargetUserPrincipalName Test-Diego@M365x946316.OnMicrosoft.com -TargetCrossTenantHostUrl https://m365x946316-my.sharepoint.com/ -ValidationOnly
74+
```
75+
76+
> [!NOTE]
77+
> We strongly recommend running the -ValidationOnly parameter as a last step before actually migrating.
78+
7079
## OneDrive status premigration
7180

7281
Before you start the migration, the users' current source OneDrive status is similar to the following screenshot. This example is from the users' source tenant, showing their current files and folders.

0 commit comments

Comments
 (0)