For a while now we've wanted to build our own in-house management tool via PowerApps to help aid in day-to-day SharePoint Administrative tasking. Now that SG offers both scheduled reports AND exporting of said reports to a location within SharePoint it is now possible to, in theory, run multiple reports, compile them (using MS Flow), and then have a PowerApp look at the central repository of data that gets built by Flow.

The problem is, I need some sort of key in all the reports to be able to pull all the data together. Ideally, I think the Site's Object ID would be a good candidate.

A large part of this tool is dealing with permissions, and at this time, to the best of my knowledge, the Permissions Matrix Report that is OOtB is not customizable, and does not contain the Site Object ID.

I propose being able to populate the Site Object ID in most reporting capabilities to provide us with a "Key" so we can automatically tie various reports together automatically through something like MS Flow.

I would love to see a permission mapping feature in the future. Not just permission levels, but the ability to take users that are explicitly assigned at the source site and automatically add them to the destination site SharePoint site group. This would be especially useful in those cases where source site users have been given "Contribute" permissions at the site level, then we could automatically add them to the Members group of the destination "classic" SharePoint Online site. This way, when we upgrade a "classic" SharePoint Online site to an Office 365 Group, the people are automatically transferred into the Azure AD group associated with the O365 Group.

Same would apply for people that are granted explicit ‘Full Control’ permissions on the source SharePoint site. Those people would be made members of the destination “Owners” group.

We often have customers who want us to conduct SPO modern site collection (GROUP#0 template with nested O365 Groups) migrations between O365 tenants. Many times, they want us to append a suffix to the URL of each SPO site when it is migrated from the source to target O365 tenant. Currently, Sharegate Desktop allows this to be done under the "Options" menu when conducting a "Copy Structure" migration job. But it only can be done when migrating one SPO site at a time in the GUI. It can't be done in bulk. When you have 500 SPO site collections to migrate and the customer wants each to have a suffix appended to the URL when conducting the migration, this involves have to migrate each SPO site collection one at a time in the Sharegate Desktop GUI which takes days of work pointing and clicking.

We often have customers who ask us to conduct SPO migrations between O365 tenants. Most of the time, the majority of the in-scope SPO sites are modern sites with the GROUP#0 template meaning they have nested O365 Groups. Currently, the only way to accomplish this scenario is in the Sharegate Desktop GUI. It cannot be done in an automated fashion using the Sharegate Shell. When there are hundreds of modern SPO sites being migrated for a project, it can take days of work pointing and clicking within the Sharegate Desktop GUI in order to conduct these migrations. Putting in some type of automation capability for bulk migrations under this type of scenario would be quite helpful.