Microsoft 365 Migrations
In most situations, CloudM Migrate requires both Application Impersonation configured within Exchange Online, and Global Admin permissions within Microsoft 365.
Please ensure that your specified Migration Admin account does not have SSO or Multi-Factor Authentication (MFA) enabled and is not subject to Conditional Access policies.
There are some situations where these permissions may not be able to be granted due to client or platform restrictions, described below are the specific permissions that CloudM Migrate requires for migration scenarios.
Mail Migrations
Exchange Application Impersonation must be configured for all mailboxes you wish to migrate data into or from.
Application Impersonation can be configured using the "Setup Administrative Permissions" button from the Destination platform configuration page
Alternatively, you can configure Application Impersonation manually by following this article: Setting up Application Impersonation.
For situations where you are migrating a subset of your users, or Application Impersonation can't be configured for the whole user base, an Exchange Write scope can be configured, prior to configuring Application Impersonation. See the following article: Setting up an Exchange Write Scope
Sharepoint / OneDrive Migrations
CloudM Migrate requires Site Collection administrator rights over the objects you are migrating into or from. In most situations, this can be achieved by granting your migration Admin account "SharePoint Administrator" within Office 365.
More information on configuring this can be found here, from Microsoft: About the SharePoint admin role in Microsoft 365.
For situations where this is not possible, you are able to manually assign Site Collection Administrator rights to Sharepoint objects. Please see this article for more information: Assigning Site Collection Permission Manually
Google Workspace Migrations
CloudM Migrate requires a service account to be configured within Google Workspace.
See this article for more information: Setting up the Service Account and enable the APIs within Google Workspace for CloudM Migrate
Comments
0 comments
Article is closed for comments.