We are using the SharePoint Online created by Teams and all other cool Apps like Planner, Flow and One Note. However, in order to use also Yammer we currently need to create a new Yammer group (that creates a new SharePoint and so on).

It would be great if from one O365 Group you could manage ALL apps, regardless where this group was created from. This would enable us to manage our SharePoint integration with Yammer seamlessly.

A very useful addition to the SharePoint Migration Tool from Microsoft would be support for SharePoint Online to SharePoint Online migrations. There are many scenarios where this is commonly needed for some customers who must restructure or realign and be able to migrate from one area of SharePoint Online to another. Just in general as well this would be a handy option to have.

Could this please be considered as a future improvement to the SharePoint Migration Tool including support with bulk migrations for SharePoint Online as a source. Thanks.

Currently, when migrating a list with a lookup field using the SharePoint Migration Tool 2.0, a failure occurs stating that the list with the GUID cannot be found. The dependency lists were migrated successfully, however, when migrating the list with the lookup fields, it is looking for a list with a GUID that doesn't exist. When the dependency lists are migrated over, they get new GUIDs.

The PowerShell cmdlets for copying Taxonomy Groups and Content Types (Copy-SPTaxonomyGroups, Copy-SPContentTypes) only support passing credentials in a legacy method, this blocks copying these items to SPO if you have conditional access (or have disabled legacy auth) enforced for your tenant.

Support for migrate from SharePoint 2010 to SPO

In SharePoint online it would be very helpful to have also the possibility to create managed paths like /projects or /departments.

add custom mime-type (such as .svg file) to IIS so that it can open directly in browser other than download it

asf

Increase the number of keywords that can be followed on SharePoint without crashing the search system.

One of the base requirements for the migration tool is 150G of available space or an SSD. Many of the organizations we support have relatively small C drives though plenty of storage on other attached storage. The migration tool seems to error out if the C drive has < 150G of available space. Please allow the admin performing the migration to specify where the migration tool can obtain it required space.

Migration Tool only supports migration to SharePoint Online, provide option to do migration to On-Premises SharePoint

Currently the Hybrid Config Wizard is unable to accept accounts which are protected by Azure MFA, including app passwords.

Please allow the use of MFA in the Hybrid Config Wizard so we can protect all elevated access accounts in O365.

BULK migration - so I don't need the users SID from AD but their email

Let the SPMT tool provisioning all the users OD4B sites - up front (BULK) - just as the Thinkscape product files to go does

We have a few SharePoint 2016 sites that we would like to have migrated to Office365 but I'm not able to find an easy way to do this. I tried to save list as template to get some of the content there but the data didn't import correctly. There needs to be a way to migrate SharePoint 2016 to O365 fully.

Dedicated Azure Storage ID should be part of each tenant. Not a free ID that is shared. We never know how long a large blob storage migration is going to take.

After Migration we are unable to open MS Project files (.MPP) from Office 365 Sharepoint online. Please fix this. There are some suggestions online on how to fix it but best would be if this was native within SharePoint Online
https://www.projectplan365.com/articles/editview-ms-project-mpp-files-from-office-365-sharepoint-online/

I know this has been raised before but the inability to rename our SP Online tenant with our updated business name is the single issue holding us back. Telling our management team that the new version of SharePoint will be based around a name we stopped using over 3 years ago makes IT look extremely unprofessional. We had been hoping for the last 2 years that this would be implemented by now.

Add support for Wiki Page Library to SharePoint Migration Tool v2