1. BitTitan Help Center
  2. Perform a Migration
  3. Microsoft 365 Migrations
  4. Microsoft Teams Migrations

Teams Troubleshooting & Error Lookup

This article covers some errors that are specific to Teams and provides troubleshooting steps. General MigrationWiz errors can be found in Error Lookup. 

Source Credential Failure

Message: Your migration failed while checking source credentials. Could not authenticate with either MigrationWiz-Teams-FullControl or MigrationWiz-Teams-ReadOnly Azure App as user has not consented to use either.

Cause: Did not consent to Teams application permission

Solution: Enable app permissions using the steps below.

Source Destination

These are the steps to enable permission level at the source only. This authentication process gives you control over who is entitled to use the source.

  1. Ensure you are signed in as a Global Admin in the Microsoft 365 Admin Portal.

  2. Go to either MigrationWiz-Teams-ReadOnly or to MigrationWiz-Teams-FullControl and consent to the app access when prompted. If choosing the Teams-ReadOnlyApp option, you will need to disable AMR via "DisableAsynchronousMetadataRead=1", due to Microsoft API limitation.

  3. Create a new Security Group named “MigrationWiz” on the Microsoft 365 Admin Portal. If you have not created a security group before, follow Microsoft's instructions.

  4. Create a new user. This user must have an active Teams license applied.

  5. Add a new user to the previously created security group as a member.

    Important

    ADFS and MFA must be turned off for this user.

  6. Create MigrationWiz project.
  7. When creating the endpoints, enter the new user credentials.

MigrationWiz-Teams-FullControl may be used on both source and destination tenants and will export document permissions. Teams-ReadOnly can only be used on the source tenant, and will not export document permissions.

Post-Migration Steps

  1. Remove the newly created user.
  2. Remove the MigrationWiz Security Group created in Step 3.
  3. To remove the app from the source or destination, perform the following steps:
    1. Launch PowerShell.
    2. Connect PowerShell to Microsoft 365.
    3. Enter the command: Connect-AzureAD
    4. Enter the admin credentials in the prompt.
    5. Enter the command: Get-AzureADServicePrincipal -SearchString Migration
    6. Look for the ObjectId of the app you want to remove and enter the following command: Remove-AzureADServicePrincipal -objectId <the object id>

Invalid User - Security Group

Message: Your migration failed while checking source credentials. Invalid User. The user needs to be a member of a security group named MigrationWiz

Cause: The user wasn’t added to the security group.

Solution:  Follow Microsoft's instructions to add the user to the MigrationWiz security group. 

Source Credentials - Teams API

Message: Your migration failed while checking source credentials. Failed to access Microsoft Teams API. Please try again later.

Possible causes:

  • The tenant has ADFS set up and the user is recently created and not synced to the cloud
  • MigrationWiz worker has some installation issues.

Solution: In most cases when seeing this error, retrying the migration later will solve the issue

Migration Failure - Endpoint Failed to Respond

Message: This migration has failed because the source or destination endpoint failed to respond.

Cause: Sometimes, AMR (Asynchronized Metadata Read) API from SharePoint takes very very long to complete. Retrying at a later time may help

Solution: Either re-run the migration at a later time or set the Advanced Option “InitializationTimeout” to a higher value than 10800000 (3 hours).

Failed to Create Team Channel

Message: Failed to create channel for team XXX. Failed to create channel XXX/YYY. Code: BadRequest Message

Cause: This appears to be a temporary Teams issue. 

Solution: Research on this solution is still ongoing. It may work to migrate to a new team in the destination (reset the line item, change the destination mail nickname). However, because this is an issue in Teams, we do not guarantee success.

File Already Exists

Message: File Already Exists: <file path>

Cause: The worker restarted halfway through the migration, so it tried to re-migrate some files and failed.

Solution: No action is needed. The migration of that file was successful.

OneNote Error

Message: “Cannot apply auto-mapping for default OneNote in team: <TeamName> Code: 10026 Message: One or more of the document libraries on the user or group’s OneDrive contains more than 20,000 OneNote items”

Cause: Microsoft limitation of not being able to support more than 20,000 items being indexed.

Solution: Try adding the OneNote tab manually at the destination

Bucket Creation

Message:  This issue has two possible messages "Couldn't create bucket {BucketName} under plan {PlanName}. Error: {error}" or "Couldn't create bucket {BucketName} under plan {PlanName}. This could be because of throttling issues. Please reset errors only and rerun Planner migration to migrate this bucket."

Cause: This could be caused by throttling issues.

Solution: Reset errors only after the migration has been completed, then rerun the Planner migration

Tasks Creation

This issue has different possible messages:

Throttling Issues

Possible messages:

  • "Couldn't create task {Taskname} under plan {planName}. This could be because of throttling issues. Please reset errors only and rerun Planner migration to migrate this task."
  • "Couldn't create task {Taskname} under plan {planName}. This could be because of throttling issues. Error: {error}."

Cause: This could be because of throttling issues.

Solution: Reset errors only after the migration has been completed, then rerun the Planner migration.

Destination Bucket Issues

Message: "Couldn't create task {TaskName} under plan {PlanName}. The destination bucket under which the task {TaskName} has to be created is not found. Please reset errors and rerun migration to migrate the bucket and the tasks under it."

Cause: The destination bucket under which the task has to be created is not found

Solution: Reset errors only after the migration has completed and rerun Planner migration. The buckets and tasks that were not created previously should be recreated.

Maximum Task Limit Issues

Message: "Migration has failed. The maximum number of Planner tasks that can be created per user has been reached."

Cause: The maximum number of Planner tasks that can be created per user has been reached.

Solution: Switch to another Office 365 migration user account via ‘Edit Project > ‘Destination Settings'. Ensure this user has also been added to the MigrationWiz security group, then rerun the Planner migration to migrate the remaining Planner tasks.

Plan

Message: "Plan not found in the destination. Please contact support to resolve this issue."

Cause: The Plan was not found in the destination.

Solution: Contact BitTitan Support

Was this article helpful?
0 out of 4 found this helpful

Articles in this section

See more