The Azure application allows ShareGate Migrate to identify to Microsoft 365 that it is running operations on your tenant through an access token. This will reduce throttling and improve task performance between ShareGate Migrate and Microsoft 365. It also grants ShareGate rights to use certain Microsoft functionality, such as the Graph API.
ShareGate Migrate can then use the permissions granted and delegated through the consent process to access your Azure resources as the user.
ShareGate Migrate will have the same access to Azure resources as the logged-in user.
As with all operations in ShareGate Migrate, your data remains secure.
Users with a global admin account can consent to the Azure ShareGate migration tool app within ShareGate Migrate. Migrate will prompt you to consent once you log in to your environment. You can change this setting anytime in the permissions settings of ShareGate Migrate or directly in your Azure portal. When you consent, Migrate can create and modify Microsoft 365 Groups and Teams on behalf of any SharePoint Online administrator.
Your admins will not have new access privileges directly in SharePoint.
The Azure ShareGate migration tool app is installed automatically once you consent access to Microsoft 365 resources in the ShareGate Migrate settings.
While the default Azure ShareGate migration tool application only uses delegated permissions. You must consent to a particular version of the Azure app that includes additional application permissions to use Copy mailboxes.
If you run your operations on PowerShell, open ShareGate Migrate to consent, then continue operations as usual (you cannot consent to the Azure ShareGate migration app through a PowerShell command).
Note: The Azure ShareGate migration tool app requires consent from a global administrator. If your account is not a global administrator, you can request that a global admin consents for you. The Azure ShareGate migration tool app is unsupported in GCC or GCC High environments. If a global admin previously consented to the app and you want to know why re-consent is needed, see Why does a global admin need to re-consent the Azure ShareGate migration app?