The Azure application allows ShareGate's migration tool 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 and Microsoft 365. It also grants the ShareGate migration tool rights to use certain Microsoft functionality, such as the Graph API.
The ShareGate migration tool can then use the permissions granted and delegated through the consent process to access your Azure resources as the user.
The ShareGate migration tool will have the same access to Azure resources as the logged-in user.
As with all operations in the ShareGate migration tool, your data remains secure.
Users can consent to the Azure ShareGate migration app within the migration tool. The migration tool will prompt you to consent as soon as you log in to your environment. You can change this setting anytime in the permissions settings. 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 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 normal (there is no way to consent to the Azure ShareGate migration app through PowerShell).
Note: The Azure ShareGate migration app requires global administrator permissions to consent to the app. If your account is not a global administrator, you can request that the global administrator consents for you. The Azure ShareGate migration app is not supported in GCC or GCC High environments.
For more information, see How can a global admin grant consent to the Azure ShareGate migration app for all users? and Which permissions does the Azure ShareGate migration tool application need?