You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Microsoft365/admin/admin/orchestrated-migration/resolve-orchestrated-migration-errors.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ This article provides tables that contain lists of errors that you might see dur
23
23
|---|---|---|---|
24
24
|**HTTP 422 Unprocessable Entity**|`BadArgument` <br><br> Error in `displayName` data field `duplicateDisplayNameJob`<br><br> `displayName` already exists. Please provide a unique job `displayName`. | Each newly submitted batch (validation or migration) needs a unique batch name. | Resubmit the batch with a unique batch name. |
25
25
|**HTTP 422 Unprocessable Entity**|`BadArgument`<br><br>Error in `completeAfterDateTime` data field `minThresholdFailed` <br><br>`completeAfterDateTime` must be greater than the current time. | The `completeAfterDateTime` submitted was in the past. It should be in the future. | Resubmit the request to update the `completeAfterDateTime` to a future date. |
26
-
|**HTTP 409 Conflict**| Conflict. Cross Tenant Migration Job \<ID> must be in final state (Completed, Failed, or Cancelled) before it can be deleted.<br><br>`resourceTypeMismatch`| Jobs can be deleted, but only if the job is not in progress. | Cancel the migration and retry the deletion, or wait until it completes or fails to delete it. |
26
+
|**HTTP 409 Conflict**|`Conflict`<br><br>Cross Tenant Migration Job \<ID> must be in final state (Completed, Failed, or Cancelled) before it can be deleted.<br><br>`resourceTypeMismatch`| Jobs can be deleted, but only if the job is not in progress. | Cancel the migration and retry the deletion, or wait until it completes or fails to delete it. |
27
27
28
28
## General Errors
29
29
@@ -59,7 +59,7 @@ This article provides tables that contain lists of errors that you might see dur
|**CTTM-001**| Teams migration for user {0} failed. Correlation Id: {1}. Retry migration. | If there is any issue with the Teams Chat migration, then this error will appear once for a user. The correlation ID can help the support team diagnose the issue. If the issue happens again after retrying, then reach out to Microsoft Support. | Retry migration for the user. |
62
-
|**CTTM-002**| Teams migration failed. App {0} in tenant {1} is not provisioned, or the app is provisioned but is not enabled. Please refer to tenant configuration documentation and retry migration. | Without a correctly provisioned app on the source tenant, the migration for TMO will fail. | Go to tenant configuration for Teams in the [source](bookmark://_Prepare_the_source)or in the [target](bookmark://_Prepare_the_target_1). |
62
+
|**CTTM-002**| Teams migration failed. App {0} in tenant {1} is not provisioned, or the app is provisioned but is not enabled. Please refer to tenant configuration documentation and retry migration. | Without a correctly provisioned app on the source tenant, the migration for TMO will fail. | Go to the [tenant configuration for Teams](https://review.learn.microsoft.com/en-us//microsoft-365/enterprise/migration-orchestrator-3-tenant-config#prepare-both-tenants-for-teams-chat-and-meeting-migration) in the source or in the target. |
63
63
|**CTTM-003**| Teams migration for user {0} failed. User {1} from source tenant {2} is not mapped to an identity in target tenant {3}. Refer to documentation for identity mapping and retry migration. | The submitted users must be properly mapped through the identity mapping system. This is checked both during the "Sync" validation state and before the user is migrated. | Rerun [identity mapping](bookmark://_Run_Identity_Mapping) then retry migration. |
64
64
|**CTTM-004**| Teams migration failed. The Cross-Tenant Teams Migration app in tenant {0} does not have the required app roles to check for Teams licenses for users. Refer to tenant configuration documentation and retry migration. | The Teams Migration app must have the appropriate app roles and service principals assigned. | Go to tenant configuration for Teams in the [source](bookmark://_Prepare_the_source) or in the [target](bookmark://_Prepare_the_target_1). |
65
65
|**CTTM-005**| Teams migration failed. User {0} in tenant {1} does not have a Teams license. Assign a Teams license to the user and retry migration. | All migrating users need to have licenses providing Teams access on both the source and the target tenants. | Go to [user license requirements](bookmark://_User_License_Requirements). |
0 commit comments