#Microsoft Teams Related Codes

#TM-AllowEmployeesViewOpenShiftIsOff

Issue:

The open shift failed in the migration with the following error:

Details:

The Allow employees on this team to view and request open shifts on the schedule setting of the source team schedule is turned off.

Recommendations:

If you want to migrate the open shift, turn on the setting for the source Team schedule, and rerun the migration job.

#TM-CannotCreateHiddenMemberShipTeam

Issue:

The object failed in the migration with the following error:

Details:

Teams with hidden membership cannot be created due to Microsoft API limitations.

Recommendations:

Choose one of the following options to resolve this issue:

#TM-CannotCreateTeamByGroupSinceNonLicenseOwner

Issue:

The object failed in the migration with the following error:

Details:

Failed to create the team from the existing group since the group owner does not have sufficient license to create a team.

Recommendations:

Ensure all group owners have the Microsoft Teams license and run an incremental or "Retry error objects" migration job to resolve this issue.

#TM-CanNotFoundConsentUser

Issue:

The private channel / shared channel failed in the migration with the following error:

Details:

The consent user of the destination app profile does not exist. Therefore, there is no user that can be ensured as the destination private channel / shared channel owner.

Recommendations:

Consent the destination app profile with an existing user or provide a service account for the destination connection. Then, rerun the migration job.

#TM-CannotGetTheChannelDrive

Issue:

The object failed in the migration with the following error:

Details:

Failed to retrieve data from the source channel drive. The error may occur when the tenant domain does not match the SharePoint Online admin center URL domain configured in AvePoint Online Services.

Recommendations:

Update the SharePoint Online admin center URL domain in AvePoint Online Services to match your tenant domain. Then, run an incremental or "Retry error objects" migration job to resolve this issue.

#TM-CanNotSetGCCHSiteLanguageWithAppOnly

Issue:

The Group/Team failed in the migration with the following error:

Details:

The destination is a Microsoft 365 Government GCC High tenant. You have configured a language using the customized feature for destination team sites, but you only use the app profile to connect to the destination. In this case, Fly will not create Teams/Groups in the destination.

Recommendations:

Provide a service account for the destination connection, and run an incremental job.

#TM-ChannelFolderNotReady

Issue:

The channel failed in the migration with the following error:

Details:

The channel failed to be migrated since the site collection/folder of the destination channel cannot be retrieved.

Recommendations:

Rerun the migration job to migrate the failed channel.

#TM-ChannelNameAlreadyExist

Issue:

The channel failed in the migration with the following error:

Details:

The channel failed to be migrated since Fly checked that there is a channel using the same name in the destination, and it has been deleted.

Recommendations:

Create a new mapping or update the existing channel mapping to map the source channel to a different destination channel. Then rerun an incremental or "Retry error objects" migration job.

#TM-ChannelNameIsTooLong

Issue:

The channel failed in the migration / Aviator job with the following error:

Details:

Recommendations:

#TM-ChanneIsNotExistForMergeChannel

Issue:

The channel failed in the Aviator job with the following error:

Details:

You select to merge source and destination channels in the Aviator job, but the destination channel does not exist. Aviator requires existing channels for the Merge action.

Recommendations:

Here are two options to resolve this issue:

#TM-ChannelNotReady

Issue:

The object failed in the migration with the following error:

Details:

The destination channel has not been initialized.

Recommendations:

Rerun an incremental or "Retry error objects" migration job later.

#TM-ChannelPreconditionFailed

Issue:

The channel failed in the migration with the following error:

Details:

The channel cannot be created due to frequent requests or bad network.

Recommendations:

Rerun the migration job later.

#TM-ChannelSiteNotExist

Issue:

The shared channel failed in the migration with the following error:

Details:

The site collection of the shared channel does not exist.

Recommendations:

If the site collection has not been initialized, click the "Files" tab of the channel in the Teams interface to initialize the site collection, and rerun the migration job.

#TM-DestinationChannelIsArchived

Issue:

The channel failed in the migration with the following error:

Details:

The source channel cannot be migrated since the mapped destination channel is archived.

Recommendations:

Unarchive the destination channel and rerun the migration job.

#TM-DestinationChannelDuplicateMap

Issue:

The channel failed in the migration with the following error:

#TM-DestinationUserNotTeamMember

Issue:

The schedule group member/shift/time off failed in the migration with the following error:

Details:

The mapped user of the source assignee/member does not exist in the destination Team.

Recommendations:

#TM-DisabledUnifiedGroupCreation

Issue:

The Group/Team failed in the migration with the following error:

Details:

The Group/Team cannot be created in the destination since the group creation is disabled on your destination tenant.

Recommendations:

Make sure the group creation is enabled on your destination tenant, and rerun a full migration job.

#TM-EDUServiceAccountNotReady

Issue:

The Team failed in the migration with the following error:

Details:

The destination is a Microsoft Education tenant, and the destination service account has not logged into the destination Class Team.

Recommendations:

Log in to the destination Class Team with the destination service account, wait about 12 hours, and rerun the migration job.

#TM-ExternalAuthenticatedUserCannotBeAddedToShareChannel

Issue:

The Team failed in the migration with the following error:

Details:

Recommendations:

You can ignore this error. If you want to migrate these users, consider mapping them to internal users.

#TM-GroupCreationLimitExceeded

Issue:

The Group/Team failed in the migration with the following error:

Details:

The number of Groups/Teams created by the destination service account will exceed Microsoft’s allowed limit.

Recommendations:

To create the Group/Team during the migration, use a different destination service account, and rerun an incremental or "Retry error objects" migration job.

#TM-GuestUserCanNotToBeOwner

Issue:

The channel/Team owner failed in the migration with the following error:

Details:

The channel/Team owner failed to be migrated since the destination user is a guest user and cannot be added as the Team/channel owner. This is a native limitation of Teams.

Recommendations:

#TM-MaxChannelLimitExceeded

Issue:

The channel failed in the migration with the following error:

Details:

The error indicates that the number of channels created for the destination Team will exceed Microsoft’s allowed limit.

Recommendations:

Delete several channels from the destination Team or create a new Team mapping to create the channel in a different destination Team, and rerun an incremental or "Retry error objects" migration job.

#TM-MaximumAssigneesInTasks

Issue:

The task failed in the migration with the following error:

Details:

The number of assignees in the task has exceeded the allowed limit of 20.

Recommendations:

Check the source and destination task assignees and remove the invalid assignees. Then rerun the migration job.

#TM-MaximumChecklistItemsOnTask

Issue:

The task failed in the migration with the following error:

Details:

The error may occur as follows:

The task has been migrated to the destination in previous migrations. After that migration, users may add checklist items to the source or destination task. In this migration, Fly checked that if the task is migrated to the destination, the total number of checklist items will exceed the task’s limit of “20”. Then Fly will not migrate the task.

Recommendations:

Delete several checklist items from the source task or the destination task, and rerun an incremental or "Retry error objects" migration job.

#TM-MaximumReferencesOnTask

Issue:

The task failed in the migration with the following error:

Details:

The error may occur as follows:

The task has been migrated to the destination in previous migrations. After that migration, users may add attachments to the source or destination task. In this migration, Fly checked that if the task is migrated to the destination, the total number of attachments will exceed the task’s limit of “15”. Then Fly will not migrate the task.

Recommendations:

Delete several attachments from the source task or the destination task, and rerun an incremental or "Retry error objects" migration job.

#TM-MaximumTabsInChannel

Issue:

The channel tab failed in the migration with the following error:

Details:

The maximum number of tabs allowed for a channel is 50. This error occurs when the number of tabs in the destination reaches this limitation.

Recommendations:

Check the source and destination channels and remove the unnecessary tabs. Make sure the number of destination tabs does not exceed 50 after the migration. Then, rerun an incremental or "Retry error objects" migration job later to resolve this issue.

#TM-MaxPrivateChannelLimitExceeded

Issue:

The channel failed in the migration with the following error:

Details:

The error indicates that the number of private channels created for the destination Team will exceed Microsoft’s allowed limit.

Recommendations:

Create the channel as a standard channel or delete several private channels from the destination Team, and rerun an incremental or "Retry error objects" migration job.

#TM-MemberInTagLimit

Issue:

The member failed in the migration with the following error:

Details:

The tag failed to be assigned to the destination user since the number of users in the tag will exceed Microsoft’s allowed limit.

Recommendations:

If you want to assign the tag to the user, remove several existing users from the tag, and rerun an incremental or "Retry error objects" migration job.

#TM-MissingPrefixSuffix

Issue:

The Team/Group failed in the migration with the following error:

Details:

The destination Team/Group name does not meet the requirements of your organization's group naming policy configured in the Microsoft Entra admin center.

Recommendations:

Delete the group naming policy or update the destination Team/Group name in the migration mapping to meet the requirements, and rerun the migration job.

#TM-NeedSA

Issue:

The object failed in the migration with the following error:

Details:

You may only use the app profile authentication to connect to the destination Microsoft 365 tenant, but the object cannot be migrated due to the limitations of an app profile.

For the limitations in Microsoft Teams migrations, refer to .

For the limitations in Microsoft 365 Group migrations, refer to .

Recommendations:

Provide a service account in the corresponding connection, and rerun an incremental or "Retry error objects" migration job.

#TM-NeedSAAndAPP

Issue:

The sensitivity label failed in the migration with the following error:

Details:

The error may occur as follows:

You want to apply a destination sensitivity label to the destination Team by selecting Apply same label in the destination or configuring a label mapping for the Team in the migration policy, and you only use the app profile or service account to connect to the destination. In this case, the destination sensitivity label failed to be applied to the Team since the function requires both the app profile and service account.

Recommendations:

To apply the destination sensitivity label to the destination Team, use both the app profile and service account to connect to the destination tenant. Then rerun an incremental or "Retry error objects" migration job.

#TM-NeedSPAdmin

Issue:

The channel failed in the migration with the following error:

Recommendations:

For situation 1, grant the service account or the consent user of the delegated app profile the Site Collection Administrator of the site. Alternatively, they should have the SharePoint Administrator or Global Administrator role.

For situation 2, grant the app profile permissions to access the site.

#TM-PermissionDelay

Issue:

The object failed in the migration with the following error:

Details:

There is a permission delay after the destination service account is added to the destination Group/Team/channel.

Recommendations:

Wait a few hours, and rerun an incremental or "Retry error objects" migration job.

#TM-PrivateChannelSiteNotExist

Issue:

The private channel failed in the migration with the following error:

Details:

The error may occur as follows:

You may only use the app profile authentication to connect to the destination Microsoft 365 tenant. The private channel is created in the destination during the migration, but the corresponding site collection of the private channel cannot be initialized. In that case, objects of the source Team cannot be migrated.

Recommendations:

Refer to the following methods to resolve this issue:

#TM-SACanNotAddChannelOwner

Issue:

The channel failed in the migration / Aviator job with the following error:

Details:

The destination service account cannot be added as the destination channel owner since the destination service account is not the destination team owner, Teams Administrator, or Global Administrator.

Recommendations:

Manually add the destination service account as the destination team owner, Teams Administrator, or Global Administrator. Then, rerun the migration job or restart the Aviator job.

#TM-SAHasNoLicense

Issue:

The Team failed in the migration with the following error:

Details:

The source or destination service account does not have a Microsoft Teams or Exchange Online license.

Recommendations:

#TM-SAOrDelegateAppConsentUserCannotGetChannelTab

Issue:

The channel tab failed in the migration with the following error:

Details:

The error indicates that the source/destination service account or delegated app profile's consent user does not have sufficient permissions to manage tabs.

Recommendations:

Refer to to add sufficient permissions for the service account or delegated app profile's consent user. Then, rerun an incremental or "Retry error objects" migration job later to resolve this issue.

#TM-SharedChannelNotSupportGuestUser

Issue:

The shared channel member failed in the migration with the following error:

Details:

The destination user is a guest user that is not supported by shared channels.

Recommendations:

#TM-ShiftDoesNotSupportGuestUser

Issue:

The schedule group member failed in the migration with the following error:

Details:

The mapped user of the source schedule group member is a guest user and cannot be added to the destination schedule group.

Recommendations:

#TM-SourceChannelNameNotFound

Issue:

The channel failed in the migration with the following error:

Details:

The source channel configured in the channel mapping does not exist.

Recommendations:

You can delete the invalid channel mapping from the migration project. Alternatively, check to make sure the source channel exists, and rerun the migration job.

#TM-SPSitesSelectedPermissionAccessDenied

Issue:

The object failed in the migration with the following error:

Details:

The app profile was granted the Sites.Selected permission to only access specific sites. However, the site is not within the accessible scope of the app profile.

Recommendations:

Refer to the user guide to grant the app profile permissions to access the site and then rerun the migration job.

#TM-TagExceedUserLimit

Issue:

The tag failed in the migration with the following error:

Details:

The tag failed to be created in the destination. No destination users can be assigned with the tag since the number of tags assigned to the destination users will all exceed Microsoft’s allowed limit.

Recommendations:

You can ignore this error to not migrate the source tag, or remove several tags from the destination users and rerun an incremental or "Retry error objects" migration job.

#TM-TagMaxCountLimit

Issue:

The tag failed in the migration with the following error:

Details:

The tag failed to be created in the destination since the number of tags added for the destination Team will exceed Microsoft’s allowed limit.

Recommendations:

Delete several tags that are not needed from the destination Team, and rerun an incremental or "Retry error objects" migration job.

#TM-TagNameOccupied

Issue:

The tag failed in the migration with the following error:

Details:

The tag failed to be created in the destination since a tag with the same name already exists in the destination.

Recommendations:

Rename or delete the destination tag, and rerun an incremental or "Retry error objects" migration job.

#TM-TagNoMappedUser

Issue:

The tag failed in the migration with the following error:

Details:

The tag failed to be created in the destination. The mapped users for source members in the tag do not exist in the destination. Therefore, there are no users in the destination that can be assigned with the tag.

Recommendations:

Configure user mappings to map the source members to existing destination users, and rerun an incremental or "Retry error objects" migration job.

#TM-TagUserMaxCountLimit

Issue:

The member failed in the migration with the following error:

Details:

The tag failed to be assigned to the destination user since the number of tags that are assigned to the user will exceed Microsoft’s allowed limit.

Recommendations:

Remove the destination user from several tags, and rerun an incremental or "Retry error objects" migration job.

#TM-TargetNotUseDefaultDomain

Issue:

The Team/Group failed in the migration with the following error:

Details:

The destination Team/Group cannot be created since the domain of the destination Team/Group is not the default domain of the destination tenant.

Recommendations:

Update the domain of the destination Team/Group to the default domain, and rerun an incremental or "Retry error objects" migration job.

#TM-TargetSiteExceedLimitStorage

Issue:

The object failed in the migration with the following error:

Details:

There is no available storage in the destination team site.

Recommendations:

You can manually delete some data in the destination site to release the storage and rerun the migration job.

#TM-TargetTeamNickNameExceedLengthLimit

Issue:

The Team/Group failed in the migration with the following error:

Details:

The destination Team's/Group's mailnickname has exceeded the length limit.

Recommendations:

Modify the destination Team's/Group's mailnickname to be less than 60 characters. For example, if the destination Team's/Group's email address is MailNickName@onmicrosoft.contoso.com, the length of the MailNickName part needs to be less than 60 characters. Then rerun the migration job.

#TM-TargetTeamNickNameOccupied

Issue:

The Team failed in the migration with the following error:

Details:

The mailnickname of the destination Team is occupied by other mailboxes, distribution lists, or security groups in the same destination tenant.

Recommendations:

Check the mailbox, distribution list, or security group that occupies the mailnickname in the destination Microsoft 365 admin center, and resolve this issue as follows:

#TM-TeamAppBlocked

Issue:

The app failed in the migration with the following error:

Details:

The app is blocked in the Microsoft Teams admin center of the destination tenant.

Recommendations:

#TM-TeamArchived

Issue:

The Team failed in the migration with the following error:

Details:

The destination Team is archived.

Recommendations:

#TM-TeamMemberNotMigrate

Issue:

The channel member failed in the migration / Aviator job with the following error:

Details:

Recommendations:

#TM-TeamNotExist

Issue:

The Team failed in the migration with the following error:

Details:

The source email address configured in the Team mapping is a Microsoft Group that does not have a Team associated.

Recommendations:

#TM-TeamsAppIsDeprecated

Issue:

The app failed in the migration with the following error:

Details:

The app has been deprecated in Microsoft Teams.

Recommendations:

Install the app manually, and rerun an incremental or "Retry error objects" migration job.

#TM-TimeOffRequestHasBeenDeleted

Issue:

The time off failed in the migration with the following error:

Details:

The reason of the source time off has been deleted.

Recommendations:

Select a different reason for the source time off, and rerun an incremental or "Retry error objects" migration job.

#TM-TooManyRequests

Issue:

The object failed in the migration with the following error:

Details:

The error indicates that the Microsoft Graph service is busy, and requests to the Microsoft Graph service are throttled.

Recommendations:

#TM-UnableToResolveTheRecipient

Issue:

The member failed in the migration with the following error:

Details:

The member is an external user and cannot be added to the destination shared channel since the user is blocked by the destination tenant.

Recommendations:

1. Log in to the Microsoft Entra ID admin center.

2. Click External Identities.

3. Click Cross-tenant access settings.

4. Click Add organization under the Organization settings tab.

5. In the Add organization panel, enter the tenant ID or domain name of the tenant for which you want to allow the member, and click Add.

   Then after about 24 hours, you can manually add the member to the destination shared channel.

#TM-UnsupportChannelName

Issue:

The channel failed in the migration with the following error:

Details:

The destination channel name contains characters that are not allowed in Microsoft 365. Refer to for details about characters not allowed in channel names.

Recommendations:

Update the destination channel name in channel mapping to remove the invalid characters, and rerun an incremental or "Retry error objects" migration job.

#TM-UserCanNotAddChannelMember

Issue:

The shared channel member failed in the migration with the following error:

Details:

The destination user of the channel member cannot be added to the destination shared channel since the user has been deleted from the destination or does not have a Microsoft 365 license.

Recommendations:

Make sure the destination user is an existing user with a Microsoft 365 license assigned, and rerun the migration job. Or try to manually add the destination user to the destination shared channel. If the attempts fails, contact Microsoft Support for assistance.

#TM-UserIsBlockSignIn

Issue:

The Team member failed in the migration with the following error:

Details:

The mapped user of the source user has its sign-in blocked by the destination tenant, and cannot be added to the destination Team.

Recommendations:

Unblock the sign-in for the mapped user in the Microsoft 365 admin center, and rerun an incremental or "Retry error objects" migration job.

#TM-UserIsNotAllowedToCreateChannel

Issue:

The private/shared channel failed in the migration with the following error:

Details:

The destination Team has the Teams policy configured to not allow the creation of shared channels/private channels.

Recommendations:

Update the destination Teams policy to allow users to create private or shared channels and wait about 2 hours. Then, run an incremental job.

#TM-UserViolatePolicy

Issue:

The user failed in the migration with the following error:

Recommendations:

You can ignore this error. If you want to add the user, you may need to disable these policies.