The Azure application allows ShareGate's migration tool and Cloud copy to identify to Microsoft 365 that it is running operations on your tenant through an access token. This will reduce throttling and improve performance on tasks between the ShareGate migration tool or Cloud copy and Microsoft 365. It also grants ShareGate rights to use certain Microsoft functionality, such as the Graph API.
The ShareGate migration tool and Cloud copy can then use the permissions granted and delegated through the consent process to access your Azure resources as the user.
The ShareGate migration tool and Cloud copy will have the same access to Azure resources as the logged-in user.
As with all operations in the ShareGate migration tool and Cloud copy, your data remains secure.
Users with a global admin account can consent to the Azure ShareGate migration tool app within the migration tool and Cloud copy. They will prompt you to consent as soon as you log in to your environment. You can change this setting anytime in the permissions settings of the migration tool or directly in your Azure portal. When you consent, it allows the migration tool to 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 migration tool's settings.
If you run your operations on PowerShell, open the ShareGate migration tool to consent, then continue operations as usual (there is no way to 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 not supported 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?