Warning
This guide describes changes related to an upcoming security update that has not yet been released. The steps outlined here may be completed in advance and will be required prior to the deployment. Additional details are available in the maintenance announcement.
Permissions Consent
Permissions Consent plays a critical role in ensuring secure and authorized access during your migration. Depending on your migration scenario, the types of permissions required and how they are granted vary. These permissions fall into two categories:
- Delegated Permissions. Granted when an application acts on behalf of a signed-in user. The service account used as the delegated user must complete the consent process. This account must have, at minimum, the Application Administrator role to perform the consent.
- Application Permissions. Granted directly to the application without user interaction. A Global Administrator role is required to consent this permissions.
After you complete the creation of your project, the interface will display a summary containing key details about your selected migration scenario. At this point, MigrationWiz will prompt you to provide the necessary permission consent to proceed.
Pre-Consent Considerations
Prior to granting consent permissions for your migration, consider the following requirements:
- The administrator role is required to grant consent (authorize) the BitTitan application on the source/destination tenant only for the consent process. After all endpoints across all related projects have successfully been consented, the role can be removed from the service account.
- When multiple projects use the same endpoints, you must still complete the consent process for each endpoint within every project’s Project Summary page. This requirement also applies to any projects created through cloning.
- When multiple projects share the same endpoints, editing the admin user in one of the projects causes the Consent button to change to Reconsent, and the Consent Banner will no longer appear.
The following section explains how permission consent is handled across different migration scenarios. The following examples will demonstrate how permission consent is managed across the migration scenarios.
Consent Status
Regardless of whether your migration uses Application or Delegate Permissions, the Project Summary section displays the permission status, using color indicator to provide clear guidance.
The following status colors may appear:
- Light Blue. Permissions require consent. Select the button to grant the necessary permissions.
- Grey. Permissions have already been consented, but you can click the button to re-consent if needed.
Warning
When multiple projects share the same endpoint, the consent button and consent banner may not update correctly after editing the admin user one of the projects. This can cause migration to fail with the error: Your migration failed while checking source/destination credentials. O365 User does not exist.
Teams Migration Consent
For Teams Migrations, MigrationWiz will ask for Delegate Consent in both Source and Destination Endpoint as shown below:
Important
Please consider that the option of Application Permissions for the source endpoint is available. However, if this option was selected, some limitations might occur while migrating your project, like not being able to migrate Planner, OneNote, and message history posting.
Teams Private Chat Migration Consent
For Teams Private Migrations, MigrationWiz will ask for Application Consent for the Source and both Application and Delegate Permissions for the Destination Endpoint as shown below:
Documents (OneDrive and SharePoint) Migration Consent
For Document (OneDrive and SharePoint) Migrations, both Application and Delegate Consent can be selected for the Source and the Destination Endpoints as shown below:
Authorization Banner
The banner is displayed within the main content section of the page. It appears at the top of all internal project pages, ensuring consistent visibility across the application as shown below:
Authorization Process
After the project creation, you need to select whether you Authorize Now to continue with your migration or you can select to Skip (Authorize Later) so you can continue setting up your migration. Follow the listed steps below once you decide to Authorize:
- After clicking the Authorize button, you will be redirected to the Microsoft login page.
- If your account has Multi-Factor Authentication (MFA) enabled, you may be prompted to complete one of the following verification steps:
- Enter a code sent via SMS or email.
- Approve a notification from the Microsoft Authenticator app.
- Use a hardware token or biometric verification.
- Answer security questions (if configured).
- Microsoft will display a list of scopes and permissions that will be shared with BitTitan. Review these carefully.
- Grant Access.
- Click Authorize to proceed.
- Upon successful authorization, you will be redirected back to BitTitan. If the process fails, an error message will be displayed with details.