Changes to OneDrive errors

There are no descriptions for the OneDrive errors. Instead, what we thought were descriptions were in fact the error messages. Reverted editorial changes.

Author: KCCross

Microsoft365/admin/admin/orchestrated-migration/resolve-orchestrated-migration-errors.md

@@ -9,7 +9,7 @@ ms.topic: troubleshooting
 ms.reviewer: v-kccross, rewood
 appliesto: 
   - Microsoft 365
-ms.date: 12/09/2025
+ms.date: 12/15/2025
 ---
 
 # Resolve errors during orchestrated migration (preview)
@@ -53,7 +53,7 @@ This article provides lists of errors that you might see during user data migrat
 | **Error code** | **Error message** | **Description** | **Action** |
 |---|---|---|---|
 | **EXCH-07** | No valid migration endpoints for the remote tenant. | Either there's a misspelling in the migration endpoint name provided in the input JSON file, or the target tenant doesn't have a tenant-to-tenant mailbox migration endpoint configured for the remote source tenant. | Confirm that the migration endpoint name provided is correct and follow the setup documentation to create a tenant-to-tenant migration endpoint if necessary. |
-| **EXCH-08** | Setup validation failed. Contact your admin.<br><br>Or<br><br>The connection to the server `outlook.office.com` could not be completed. Please make sure source mailbox is in the migration scope, scope identifier is set in Organization Relationship, and migration setup between source mailbox and target mail user is correct.<br><br>Or<br><br>`Test-MigrationServerAvailability` failed with: {0} | `Test-MigrationServerAvailability -Endpoint \<endpoint> -TestMailbox [[email protected]](mailto:[email protected])>` failed. The `Test-MigrationServerAvailability` check is a high-level validation method used for tenant-to-tenant migration. Failing this check can indicate one or more of the following issues:<br><br>- The target object isn't found.<br><br>- The source object or source organization has litigation hold enabled and can't be migrated cross-tenant without being added to the exception list.<br><br>- The source object wasn't added to the migration scope.<br><br>- The source mailbox exceeds the quota and can't be migrated cross-tenant.<br><br>- There's a mismatch on the `ExchangeGuid` stamped on the source and target objects.<br><br>- The source mailbox's `MailboxMoveRemoteHostName` isn't empty, which means either it was being moved in another batch or the `MailboxMoveRemoteHostName` wasn't cleared when the previous request was cleaned. Use `Set-Mailbox -AttributesToClear MailboxMoveRemoteHostName`, then retry migration.<br><br>- The OAuth setup was completed incorrectly. Use this script to troubleshoot the issue: [Cross Tenant Mailbox Migration Validation](https://microsoft.github.io/CSS-Exchange/Admin/CrossTenantMailboxMigrationValidation/).<br><br>- None of the source or target objects have a cross-tenant mailbox migration license assigned. Assign the license and retry. The target object is either missing an `ExchangeGuid` or an `ArchiveGuid`.<br><br>- Either the source or target objects have a soft deleted user. Use `Get-Mailbox -IncludeSoftDeletedMailbox/Get-MailUser -SoftDeletedMailUser` to find the soft deleted users and remove them. | You can avoid most of the issues by:<br><br>- Completing a correct identity mapping.<br><br>- Setting up the non-Microsoft OAuth app correctly, and their Exchange objects such as `OrgRel` (organization relationship) and `MigrationEndpoint`. Use this script to find the root cause of the issue: [Cross Tenant Mailbox Migration Validation](https://microsoft.github.io/CSS-Exchange/Admin/CrossTenantMailboxMigrationValidation/). |
+| **EXCH-08** | Setup validation failed. Contact your admin.<br><br>Or<br><br>The connection to the server `outlook.office.com` could not be completed. Please make sure source mailbox is in the migration scope, scope identifier is set in Organization Relationship, and migration setup between source mailbox and target mail user is correct.<br><br>Or<br><br>`Test-MigrationServerAvailability` failed with: {0} | `Test-MigrationServerAvailability -Endpoint \<endpoint> -TestMailbox [[email protected]](mailto:[email protected])>` failed. The `Test-MigrationServerAvailability` check is a high-level validation method used for tenant-to-tenant migration. Failing this check can indicate one or more of the following issues:<br><br><ul><li> The target object isn't found.<br><br><li> The source object or source organization has litigation hold enabled and can't be migrated cross-tenant without being added to the exception list.<br><br><li> The source object wasn't added to the migration scope.<br><br><li> The source mailbox exceeds the quota and can't be migrated cross-tenant.<br><br><li> There's a mismatch on the `ExchangeGuid` stamped on the source and target objects.<br><br><li> The source mailbox's `MailboxMoveRemoteHostName` isn't empty, which means either it was being moved in another batch or the `MailboxMoveRemoteHostName` wasn't cleared when the previous request was cleaned. Use `Set-Mailbox -AttributesToClear MailboxMoveRemoteHostName`, then retry migration.<br><br><li> The OAuth setup was completed incorrectly. Use this script to troubleshoot the issue: [Cross Tenant Mailbox Migration Validation](https://microsoft.github.io/CSS-Exchange/Admin/CrossTenantMailboxMigrationValidation/).<br><br><li> None of the source or target objects have a cross-tenant mailbox migration license assigned. Assign the license and retry. The target object is either missing an `ExchangeGuid` or an `ArchiveGuid`.<br><br><li> Either the source or target objects have a soft deleted user. Use `Get-Mailbox -IncludeSoftDeletedMailbox/Get-MailUser -SoftDeletedMailUser` to find the soft deleted users and remove them. | You can avoid most of the issues by:<br><br><li> Completing a correct identity mapping.<br><br><li> Setting up the non-Microsoft OAuth app correctly, and their Exchange objects such as `OrgRel` (organization relationship) and `MigrationEndpoint`. Use this script to find the root cause of the issue: [Cross Tenant Mailbox Migration Validation](https://microsoft.github.io/CSS-Exchange/Admin/CrossTenantMailboxMigrationValidation/). |
 | **EXCH-15** | Max retry for user with id {0} reached. | The maximum number of retries on `EXOHandler` is reached. A server-side issue might be going on. Retry by creating a new migration batch. And if the issue persists, contact Microsoft Support for help. | Create a new migration batch. |
 
 ## Teams chat migration errors
@@ -75,7 +75,7 @@ This article provides lists of errors that you might see during user data migrat
 | **CTTM-013** | Teams migration failed. The user {0} from source tenant {1} isn't authorized to migrate to user {2} from target tenant {3}. Refer to documentation for identity mapping and retry migration. | If the user isn't authorized, then they need to be added in the security group within the Scope field of the organization relationship or added to identity mapping. | Add the user to the security group associated with the scope of the Organization Relationship. [Run identity mapping](/microsoft-365/enterprise/migration-orchestrator-4-user-prep.md#run-identity-mapping) again, then retry migration. |
 | **CTTM-014** | Teams migration failed. The tenant {0} does not exist. Check the tenant Id and retry migration. | If the tenant doesn't exist, it might have been mistyped on submission or improperly configured. | Review the common parameters used in the [syntax of running migration](/microsoft-365/enterprise/migration-orchestrator-5-running-migration.md#common-parameters). |
 | **CTTM-015** | Teams migration for user {0} failed. The user {0} in tenant {1} does not exist. Check the user Id and retry migration. | If the user doesn't exist, it might be that the user ID when submitted was incorrect. | Review the common parameters used in the [submission syntax for running the migration](/microsoft-365/enterprise/migration-orchestrator-5-running-migration.md#common-parameters). |
-| **CTTM-016** | Teams migration failed. The tenant failed a pre-migration validation step. Refer to tenant configuration documentation and retry validation. | All checks need to pass successfully before the user content can migrate. | Refer to the [list of prevalidation-checks](/microsoft-365/enterprise/migration-orchestrator-2-planning-prerequisites.md#prevalidation-checks) to determine what failed. |
+| **CTTM-016** | Teams migration failed. The tenant failed a pre-migration validation step. Refer to tenant configuration documentation and retry validation. | All checks need to pass successfully before the user content can migrate. | Refer to the [list of prevalidation checks](/microsoft-365/enterprise/migration-orchestrator-2-planning-prerequisites.md#prevalidation-checks) to determine what failed. |
 | **CTTM-017** | Teams migration for user {0} completed with errors, {1} chat messages couldn't be imported. Correlation Id: {2} | This error indicates that some messages failed to migrate for the user {0}. The total number of messages that failed is {1}. Some messages fail to migrate because the content type is unsupported, such as Loop messages. | Determine if you want to attempt to retry migration. If yes, you can resubmit migration for the user. |
 | **CTTM-018** | Teams migration failed. The user {0} in tenant {1} does not have a SIP address. Refer to user configuration documentation for instructions on how to assign a SIP address and retry migration. | This error indicates that the user doesn't have a SIP domain assigned to it, which is required for migration. | Assign a SIP address to the user. For information, see [user license requirements](/microsoft-365/enterprise/migration-orchestrator-4-user-prep.md#user-license-requirements), then retry the migration. |
 | **CTTM-019** | Teams migration failed. The Cross-Tenant Teams Migration app isn't properly configured to allow the service to check for the SIP address for user {0} in tenant {1}. Refer to tenant configuration documentation and retry migration. | The Teams Migration app must have the appropriate app roles and service principals assigned. | Go to the [tenant configuration for Teams](/microsoft-365/enterprise/migration-orchestrator-3-tenant-config.md#prepare-both-tenants-for-teams-chat-and-meeting-migration) in the source or in the target. |
@@ -102,32 +102,32 @@ This article provides lists of errors that you might see during user data migrat
 
 | **Error code** | **Error message** |
 |---|---|
-| `FeatureIsNotEnabled` | Cross-tenant content move [{0}] is not enabled for this tenant. |
+| `FeatureIsNotEnabled` | The Cross-Tenant content move [{0}] feature is not enabled for this tenant. |
 | `MnATrustNoSetupForPartner` | There is no Cross-Tenant relationship established for partner [{0}]. |
 | `MnAReverseTrustNeedsRequiredPartnerRole` | Provide the `RequiredPartnerRole` for the cmdlet. |
-| `MnATrustWrongCmdletUsage` | You can't use this cmdlet with a partner with [Source] cross-tenant relationship configuration [{0}]. |
+| `MnATrustWrongCmdletUsage` | You can't use this cmdlet with a partner with [Source] Cross-Tenant relationship configuration [{0}]. |
 | `MnAOdbFailedToGetUrlForSourceUPN` | Unable to get a OneDrive URL for source user UPN [{0}]. Error: {1}. |
-| `MnAOdbForSourceUPNDoesNotExist` | OneDrive site for source user UPN [{0}] doesn't exist. |
-| `MnAOdbForSourceUPNDoesNotExistYet` | OneDrive site for source user UPN [{0}] doesn't yet exist. Current URL - [{1}]. |
-| `MnAIdentityMapEntryDoesNotExistsForSourceUPN` | Identity map entry for source UPN [{0}] doesn't exist on the target tenant. |
+| `MnAOdbForSourceUPNDoesNotExist` | OneDrive site for source user UPN [{0}] does not exist. |
+| `MnAOdbForSourceUPNDoesNotExistYet` | OneDrive site for source user UPN [{0}] does not yet exist. Current URL - [{1}]. |
+| `MnAIdentityMapEntryDoesNotExistsForSourceUPN` | Identity map entry for source UPN [{0}] does not exist on the target tenant. |
 | `MnAIdentityMapEntryTooManyForSourceUPN` | There is more than one identity map entry for source UPN [{0}]. |
 | `MnAIdentityMapEntryDoesNotMatchRequest` | The identity map entry for source UPN [{0}] doesn't correspond to the requested target UPN [{1}]. |
-| `MnAOdbUsersAreNotLicensed` | The source UPN [{0}] and target UPN [{1}] aren't licensed for cross-tenant OneDrive migration. |
-| `MnATargetUpnIsInvalid` | The target UPN '{0}' is invalid. Correct this issue and try again. |
+| `MnAOdbUsersAreNotLicensed` | Neither source UPN [{0}], nor target UPN [{1}] are licensed for Cross-tenant OneDrive migration. |
+| `MnATargetUpnIsInvalid` | The target UPN '{0}' is invalid. Please correct this issue and try again. |
 | `MnATargetDomainIsAlreadyInSourceSiteUsers` | The source ODB '{0}' contains users with the target tenant domain '{1}' in their UPN, such as [{2}]. |
 | `MnATargetUserDoesNotExist` | Target user [{0}] does not exist on the target side. |
 | `MnATargetUserIsNotSpoEnabled` | Target user [{0}] is not allowed to have any SharePoint resources, including OneDrive. |
-| `MnAMoveJobWasNotCreated` | The cross-tenant content move job was not created for the source site [{0}]. |
+| `MnAMoveJobWasNotCreated` | The Cross-Tenant content move job was not created for the source site [{0}]. |
 | `MnAMoveJobCreationFailed` | The Cross-Tenant content move job creation for the source object id [{0}] has failed. Error: [{1}] |
 | `MnASiteMoveTargetUrlHasWriteConflict` | The target tenant has a conflict for the site provided. Check whether site with url from the `TargetSiteUrl` property of this job already exists on the target. |
 | `MnAOdbOwnerUrlMismatch` | The OneDrive site '{0}' has a site owner '{1}' that doesn't match the owner of the OneDrive. |
 | `MnATargetUrlNotValidForRename` | For site Source url '{0}', target url '{1}', including files and folders, exceeds the character limit of the destination. |
 | `MnAFatalErrorAdminSiteCouldNotBeUsedAsMySiteHost` | Cross-tenant moves are blocked because the `TargetCrossTenantHostUrl` value is incorrect. |
-| `MnABYOKEnabledOnSourceTenant` | Blocking cross-tenant moves because bring your own key (BYOK) is enabled for the source tenant. |
-| `MnAPartnersOnTheSameFarm` | It has been detected that partners reside in the same SharePoint location that prevents them from migrating. |
+| `MnABYOKEnabledOnSourceTenant` | Blocking Cross-Tenant moves because 'Bring Your Own Key' (BYOK) is enabled for the Source tenant. |
+| `MnAPartnersOnTheSameFarm` | It has been detected that partners reside in the same SPO location that prevents them from migrating. |
 | `MnATargetSideEnvironmentHasConditionsThatBlockTheMove` | Cross-tenant moves are blocked because the target environment has conditions that prevent the move. |
 | `MnASiteMoveIsInprogressOrFinished` | Failed to initiate cross-tenant move because another move job for the same source URL [{0}] is already in progress or has finished. |
-| `MnAPartnersFarmsAreIncompatible` | Verify the compatibility status before running the migration. In case of incompatible tenants, we recommend waiting for a minimum of 48 hours. |
+| `MnAPartnersFarmsAreIncompatible` | Please verify the compatibility status before running the migration. In case of incompatible tenants, we recommend waiting for a minimum of 48 hours. |
 
 ## Identity mapping errors