Without site collection admin permissions, many interactions with the SharePoint APIs will fail, causing unpredictable issues. Site collection admin permissions are also required when running most operations in ShareGate Desktop, even if you have global admin or SharePoint admin permissions.

Site collection admin (Microsoft 365 and SharePoint on-premises) You will experience limitations with Teams and Microsoft 365 Groups and may experience throttling in Microsoft 365 if you do not consent the app. Note: When working with ShareGate Desktop, the only difference between global admin and SharePoint admin is that a global admin can consent to the Azure ShareGate Desktop application.

Perform migrations of multiple site collections (requires a connection to your admin center).

Connect to your Microsoft 365 SharePoint admin center.

Global admin and SharePoint admin (Microsoft 365)

Auto-assign as site collection administrator.

Site collection admin (Microsoft 365 and SharePoint on-premises).

Global admin and SharePoint admin (Microsoft 365).

For more information on Microsoft 365 roles, see the Microsoft article, About admin roles. Tip: For a quick reference of all these permissions, see Permissions reference tables - Migrations and Permissions reference tables - Explorer and reports.

In this article, you will find details about each administrative permission and why they are needed. These permissions are required for the app to interact with your Microsoft environment and ensure that your connection is secure.įor example, for a Teams migration, you need Teams admin permissions to migrate the team and SharePoint admin permissions to migrate the associated SharePoint site. You will need certain Microsoft administrative permissions to perform actions using ShareGate Desktop.

You need permission from desktop