|
If the external sharing settings of the target tenant is more restrictive than the settings in the source tenant, then Office 365 groups and SharePoint items cannot be migrated tot he target tenant.
Workaround: Ensure that sharing settings in the target tenant is the same or less restrictive than the source tenant. You must create a fresh task to migrate the items. |
259757 |
| When two or more users are participants in a chat, the chat migration task event is not linked to any particular user. |
256913 |
| Planner migration: If there are more than 400 tasks in a bucket then On Demand migrates the first 400 tasks only. |
|
| On Demand cannot migrate the file if the SharePoint admin center (under Settings | Site Creation) has been used to change the default URL. |
240044 |
|
Links to files and applications in Tabs are not supported if the files and applications are located outside the default SharePoint site of the Channel. These links are not migrated to the target and should be re-added manually by the target Channel owner. |
223575 |
| File links in team chats will not work after chat migration if the files are moved to another folder in the source tenant. |
320875 |
| If you rename a tab in the source team and then re-migrate, the renamed tab will be migrated. The target will then have two tabs, one with the old name and one with the new name. |
197275 |
| Meeting links in Teams calendar items of migrated teams don't work because the links still point to source tenant. |
196069 |
| Provisioning of public teams is not supported for migration scenarios from one education tenant to another. Only private teams can be provisioned for these scenarios. |
218826 |
|
OneNote tabs migration fails if the team contains a large number of items (folders or files, some of which could be OneNote entities such as notebooks, sections or section groups) and the following error message is reported: Request failed with Forbidden status code (Forbidden). { "error": { "code": "10026", "message": "One or more of the document libraries on the user or group’s OneDrive contains more than 20,000 OneNote items (notebooks, sections, section groups). Please try again later."....
Workarounds:
Before proceeding with migration consider the following Microsoft recommendations to avoid the problem: https://docs.microsoft.com/en-us/archive/blogs/onenotedev/onenote-api-calls-fail-with-a-large-number-of-items-in-a-sharepoint-document-library
-OR-
Before proceeding with Teams migration use SharePoint migration to migrate the site collections for affected teams. Then retry Teams migration with Use previously migrated files option selected |
216192 |
|
When the team name in source tenant is different from the one in target tenant, a blank default team’s notebook (with the target team name) will be created in target tenant. The original default team’s notebook (with the source team name) will be migrated correctly by Team’s migration. This results in two default team’s notebook in target. |
N/A |
| Archived teams are not supported. In case you need to migrate these teams, you need to unarchive them in the source to migrate and then archive them again in the source and in the target. |
181522 |
|
Target team settings are not updated if you re-run the provisioning task.
Workaround: Update the target team settings manually or remove the team and re-run the provisioning task. |
N/A |
| Incremental migration migrates new messages that was created since the last migration. On Demand Migration for Teams cannot modify or delete messages on the target if they have been modified or deleted on the source. |
167428 |
|
The target tenant's Global Administrator is displayed as the owner of all migrated messages on the target: The original owner and creation time of a message are displayed in the first line of the message starting with "Originally posted by...". |
157045 |
| Channel isFavoriteByDefault property migration is not supported . Workaround: Enable Automatically show this channel in everyone’s channel listoption for the channel manually in your Teams client. |
154722 |
|
The memberships is not updated in Teams client immediately after provision. It takes a while before Microsoft synchronizes memberships between group and Teams.
Workaround: Wait for membership synchronization |
N/A |
The following warning is reported: Cannot migrate attachment ***: file not found
Workaround: Verify whether the file is not blocked or deleted in the source. File Migration task cannot migrate file in case it is not available. |
N/A |
| Target administrative account are added to source teams automatically. This is mandatory requirement for migration. The following warning is reported: Adding *** as a member of the group '***' on the source...
No action required. |
N/A |
|
The following warning is reported: Cannot add *** as group ***: User Mapping does not exists. The team member or owner was not matched or migrated by Account migration project.
Workaround:In Account Migration project match or migrate the account and then re-run provision task.
|
N/A |
| Resource processingIf EDU team group has been migrated in the Account Migration project first and then this EDU team is provisioned in the Teams Migration project, the error "Request failed with BadRequest status code (Bad Request)" is reported.
Workaround: Delete the EDU team group created by Account Migration, then perform discovery and provision with Teams Migration project. |
N/A |
| Private one-to-one chats with a Skype user are not migrated. The Microsoft Graph API List chat messages do not support querying messages of that type. |
N/A |
| If you have personalized the name of a group chat then that personalized name will not be migrated. Post migration, on the target, the group chat name will revert to that supplied by Microsoft: the list of team members in the chat. Post migration on the target you can re-enter the name you gave to the group chat if you wish. |
N/A |
| Private one-to-one chats are migrated as group chats. On the source the name of the chat is given by the other person in the chat; on the target the name of the chat is of the form " name and name - migrated". On the target the private chat becomes a group chat when the migration account granting consent to the tenant is added to the chat as a participant. This is by design to workaround Microsoft's API limitations. To preserve privacy this account is removed from the chat as soon as the chat migration is completed. |
N/A |
| On the source a member removed from a chat can still see the history of the chat in the source. On the target, members cannot see the history of chats they have been removed from. |
N/A |
| Individual messages larger than 4 MB will not migrate. Messages containing several inline messages can exceed 4MB. The chat will migrate without the large messages. An error will display in the On Demand Migration for Teams Events tab of the form: Request failed with RequestEntityTooLarge status code (Request Entity Too Large). |
N/A |
| Users deleted on the tenant are not migrated, so do not show as members of a chat on the target. Deleted users do remain visible as members of a chat on the source. 1:1 chats, where one of the users is deleted, are migrated for the user that is still a member of the tenant. |
N/A |
| Private one-to-one chats with an ‘External user’ (user from another tenant) are treated as follows. Private one-to-one chats initiated by an ‘External user’ are not migrated. Private one-to-one chats not initiated by an ‘External user’ are migrated, and in the title the external user’s real name is replaced with the text ‘External user’. |
N/A |
|
Links to attachments in chats that are migrated and archived cannot be opened from the Conversation History in the Teams client if you left-click the link.
Workaround: Right-click the attachment and select Open Link in New Tab or Open Link in New Window from the context menu. |
313562 |
| When teams are provisioned with the option to merge with an existing team in the target tenant and a new channel is created with the original name plus suffix, the SharePoint folder for the new channel retains the original name. |
345807 |
| Replies to private chats are migrated as regular chats but the reference to the original chat is not retained. |
339662 |
