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 via the steps below.

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 Office 365 Admin Portal.

  2. Go to either Teams-ReadOnlyApp or to Teams-FullControlApp 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 new Security Group named “MigrationWiz” on the Office 365 Admin Portal. If you have not created a security group before, follow Microsoft's instructions.

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

  5. Add new user to 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.

Steps to enable permission level at the destination:

  1. Ensure you are signed in as a Global Admin.

  2. Go to Teams-FullControlApp and consent to the app access when prompted.

  3. Create new Security Group named “MigrationWiz” on the Office 365 Admin Portal.

  4. Create new user. Important: ADFS and MFA must be turned off for this user.

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

  6. Create MigrationWiz project.

  7. When creating the endpoints, enter the new user credentials.

Teams-FullControlApp may be used on both source and destination tenant 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 Office 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. User needs to be a member of a security group named MigrationWiz

Cause: 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:

  • 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 case 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: Sometime, AMR (Asynchronized Metadata Read) API from SharePoint takes very very long to complete. Retrying in 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 mailnickname). 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 remigrate some files and failed.

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

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