#Migration to Microsoft 365 Groups

Refer to the table below to view the supported and unsupported object types for Microsoft 365 Groups Migration.

√ – Supported; × – Unsupported.

#Microsoft 365 Group

Object Type	Sub Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Files	New	√	√
Files	Upload	√	√
Privacy	-	Partially Supported	Partially Supported	If the destination Group is created by Fly during the migration, Fly will migrate the privacy of the source Group. If the destination Group already exists, Fly will keep the privacy of the destination Group and will not migrate the privacy of the source Group.
Members	Member	√	√
Members	Owner	√	√
Members	Update Role	Partially Supported	Partially Supported	The group owners cannot be updated to members during the migration due to Microsoft API limitations.
Membership Type	Dynamic User	√	√	If the membership type of the source Group is Dynamic User, refer to the note below the table.
Membership Type	Assigned	×	×
Notebook	-	√	√
Planner	-	Partially Supported	Partially Supported	Premium planners are not supported in the migration.
Settings	Let people outside the organization email this team	×	√	Make sure the source and destination service accounts/delegated app profiles’ consent users have the Microsoft 365 Global Administrator or Exchange Administrator role.
Settings	Send copies of team emails and events to team member's inboxes	×	√	Make sure the source and destination service accounts/delegated app profiles’ consent users have the Microsoft 365 Global Administrator or Exchange Administrator role.
Settings	Don’t show team email address in Outlook	×	√	Make sure the source and destination service accounts/delegated app profiles’ consent users have the Microsoft 365 Global Administrator or Exchange Administrator role.
Settings	External file sharing	√	√	To migrate the setting, data in SharePoint sites must be migrated together with Groups.
Description	-	√	√
Connectors	-	×	×

#Microsoft 365 Group Mailbox

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Mails	√	√
Calendar	√	√	If you enable the Replace the meeting links with the destination information setting in the Microsoft 365 Groups migration policy to replace the source meeting link with a destination link, make sure you have configured user mappings for the source meeting organizers, and some notes need your attention. Refer to the Notes when Replacing Meeting Links section below for details.

#Notes when Replacing Meeting Links

If you enable the Replace meeting links with the destination information setting to replace the source meeting link with a destination link, some issues may occur in the following situations:

1. Due to API limitations, some features may be different from the source after users join the meeting with the new links.

   • If destination organizers join the meeting via Teams on the web:

     • Chat, Apps, Record and translation, and Meeting notes actions are not available. 

     • The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info. 

     • The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options. 

     • Only the current user will be displayed in the meeting. 

     • The meeting duration will not be displayed.

     • The options in Meeting options displayed in More > Settings will not be displayed. 

   • If destination attendees join the meeting via Teams on the web:

     • Chat, Apps, Record and translation, and Meeting notes actions are not available. 

     • The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info. 

     • The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options. 

     • Only the current user will be displayed in the meeting. 

     • The meeting duration will not be displayed.

   • If destination organizers join the meeting via the Teams app:

     • Chat, Apps, Record and translation, and Meeting notes actions are not available. 

     • Only the current user will be displayed in the meeting. 

     • The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info. 

     • The meeting duration will not be displayed.

     • The options in Meeting options displayed in More > Settings will not be displayed.

   • If destination attendees join the meeting via the Teams app: 

     • Chat, Apps, Record and translation, and Meeting notes actions are not available. 

     • Only the current user will be displayed in the meeting. 

     • The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info. 

     • The meeting duration will not be displayed.

2. The Meeting options link in the calendar cannot be opened. 

3. The Join on the web link in the source calendar item cannot be replaced with the destination information. After you map the source meeting attendees to the destination, when the mapped attendees click the Join on the web link and use the meeting ID and passcode to join the meeting via Microsoft Teams on the web, they will wait in the lobby until the meeting organizer allows the user to enter the meeting.

4. The source tenant ID in the meeting link will be replaced with the destination information. If some users in your organization have been migrated to the destination and the meeting participants contain source users and users who have been migrated to the destination, when the source and destination participants click the meeting links in the email, they will enter two different meetings.

5. The source tenant ID in the meeting link will be replaced with the destination information. If the meeting participants contain external users, the destination meeting organizer needs to update the meeting after the migration to update the meeting link for external users. Otherwise, when external users click the link to attend the meeting, they will be redirected to the source meeting.

6. When you enable the Safe Links settings for email addresses in Microsoft 365 Defender for Office 365, the source meeting links cannot be replaced with the destination information. When the external/destination user clicks the source meeting link to attend the meeting, they will wait in the lobby until the meeting organizer allows the user to enter the meeting.

If your meeting meets the situation 4, 5, or 6 above, we recommend that you do not enable the Replace meeting links with the destination information setting and configure the ChangeTeamsMeetingScopeAsEveryone=true customized feature string in the migration policy to publish the source meeting link to everyone. Also, you need to note the following:

• Make sure you have configured an app profile for the source tenant, and the app has the permissions below to publish the source meeting link:

  • Make sure you have assigned the access policy for the AvePoint Fly app or custom Azure app. Refer to access policy for details.

  • If you use a custom Azure app, make sure you have assigned the Microsoft Graph API > OnlineMeetings.ReadWrite.All permission to the app.

• If destination user joins the meeting via Teams on the web:

  • Apps, Record and translation, and Meeting notes actions will not be displayed.

  • Source organizer will be displayed as a guest and source attendees will be displayed as external users in the destination.

  • End meeting action will not be displayed.

  • The options in Meeting options and Mute notifications action displayed in More > Settings will not be displayed.

  • Manage permissions, Download attendance list and Lock the meeting actions displayed in Participants will not be displayed.

  • Together mode action in View is not available.

  • Destination users cannot save the meeting recording. The meeting recording saved by the source user will be displayed in the meeting chat of destination users rather than meeting files. When destination users click the recording, a window appears with the recording link. Destination users do not have permissions to access the recording via the recording link since the link is a source link.

• If destination user joins the meeting via Teams app:

  • Rooms, Apps, Record and translation, and Meeting notes actions will not be displayed.

  • Source organizer will be displayed as an external user in the destination.

  • End meeting action will not be displayed.

  • The options in Meeting options displayed in More > Settings will not be displayed.

  • Manage permissions, Download attendance list and Lock the meeting actions displayed in Participants will not be displayed.

  • Together mode action in View is not available.

  • Destination users cannot save the meeting recording. The meeting recording saved by the source user will be displayed in the meeting chat of destination users rather than meeting files. When destination users click the recording, a window appears with the recording link. Destination users do not have permissions to access the recording via the recording link since the link is a source link.

For whether to enable the Replace meeting links with the destination information setting in the migration policy, we have recommendations based on different migration methods:

• For big bang migrations (migrate all objects at a time), the situations above may not occur, and we recommend that you enable the Replace meeting links with the destination information setting to replace the source meeting link with a destination link.

• For wave-based migrations (split the migration into multiple waves), to avoid the situations above, we recommend that you do not enable the Replace meeting links with the destination information setting and refer to the solutions provided above.

#Group Team Site

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Files	√	√
Sites	√	√	If the destination Groups are newly created during the migration, Fly will keep the language of the source team site to the destination.

#Support Lists for Planner Data Types

Refer to the table below for the support details.

√ – Supported; × –Unsupported.

Data Type	Sub Type	App Profile Support Status	Service Account Authentication Support Status	Comment
Plan	-	Partially Supported	Partially Supported	Only plans added to the Group can be migrated.Premium planners are not supported in the migration.
Bucket	-	√	√
Task	Task Member	√	√
Task	Progress	√	√
Task	Start Time	√	√
Task	Due Date	√	√
Task	Notes	√	√	The format of links migrated to the destination is different from that of the source.
Task	Checklist	√	√
Task	Attachment	√	√
Task	Comments	√	√
Task	Label	√	√
Task	Priority	√	√
Task	Repeat	×	×
Chart	Status	√	√
Chart	Members	√	√

#Unsupported Elements by Service Account Authentication or App Profile

Refer to the table below for the unsupported elements if you use the service account authentication and/or app profile authentication in the source or destination connection:

	Source App Profile	Source Service Account Authentication	Source App Profile and Service Account Authentication
Destination App Profile	Group settings	Group settings	Group settings
Destination Service Account Authentication	None (all supported)	None (all supported)	None (all supported)
Destination App Profile and Service Account Authentication	None (all supported)	None (all supported)	None (all supported)