Home > New Features and Improvements from Previous Versions > Fly June 2023
Export to PDFRelease Date for the Commercial Environment: June 11, 2023
Release Date for the U.S Government Environment: June 18, 2023
Fly now supports Gmail to Exchange Online migrations.
When creating a Microsoft 365 Groups/Microsoft Teams/SharePoint Online/OneDrive for Business connection, you can now select multiple service accounts to run the migration jobs to be less throttled.
Fly now supports migrating planner tasks using the app profile authentication method. If your connections are updated from previous release, pay attention to the following information before the migration:
If the source or destination connection has the Fly app profile configured, you need to reauthorize the Fly app profile in AvePoint Online Services.
If the source or destination connection has a custom app profile configured, you need to add the Tasks.Read.All permission to the source custom app profile, add the Tasks.ReadWrite.all permission to the destination custom app profile, and then reauthorize the app profile in AvePoint Online Services.
When configuring a Groups/Teams migration policy, you can now select whether to use a simple Groups/Teams policy or use a SharePoint and Exchange migration policy to migrate the SharePoint and Exchange data for Groups/Teams.
When configuring a destination connection for Teams Chat Migration, you are now required to provide a SharePoint admin center URL to connect to the OneDrive for Business sites of destination chat users.
When configuring a migration policy for Teams Chat, you can now choose whether to synchronize the pinned/unpinned status of source chat messages to the destination.
When configuring a connection for SharePoint Online/OneDrive for Business Migration, you are now required to provide a SharePoint admin center URL to retrieve source site collections/OneDrive sites or create site collections/OneDrive sites in the destination.
When you configure a migration policy for SharePoint Online/OneDrive for Business, you can now define a default destination user to replace the metadata of users that do not exist in the destination with the specified user during the migration.