How to register the CodeTwo migration application in Azure AD
You want to manually register CodeTwo Office 365 Migration / CodeTwo Exchange Migration in your Azure Active Directory tenant.
Starting version 3.2.x, the CodeTwo migration application connects to Office 365 by using the secure OAuth 2.0 authentication. To enable this connection, first you need to register CodeTwo Office 365 Migration / CodeTwo Exchange Migration in Azure AD for all Office 365 tenants that will be used in the migration process. Next, to allow the application to access your mailboxes and perform the necessary migration tasks, you also need to grant the necessary permissions to that application.
Keep in mind that the CodeTwo migration application can perform the registration automatically. You simply need to provide an Office 365 global admin credentials in the source/target server connection wizard. To learn more, see the user's manual:
Use the links below for guidelines on how to register the CodeTwo migration application in Azure AD:
- Register a new application in Azure AD
- Configure application permissions
- Assign certificates / secrets to an app in Azure
- Sign in to your Azure Active Directory admin center.
- Navigate to Azure Active Directory > App registrations and click New registration (Fig. 1.). This opens the Register an application page.
- Enter a name for the application (e.g. CodeTwo Migration app) and click Register (Fig. 2.). You can leave the other options to their defaults.
- On the application Overview page, click View API permissions (Fig. 3.). The API permissions page will open.
- Click the Add a permission button and select Exchange (Fig. 4.).
- Click Application permissions, select full_access_as_app, and then click Add permission (Fig. 5.).
- Click Add a permission again and this time select Microsoft Graph.
- Click Application permissions and select the following permissions:
The User.ReadWrite.All and DeviceManagementServiceConfig.Read.All permissions ale necessary only for target Office 365 connections.
- Back on the API permissions page, click the Grant admin consent button (once it becomes available) and then click Yes to confirm (Fig. 6.).
You need to assign a certificate or client secret (app password) to the newly added application. This will allow the OAuth protocol to prove the application’s identity. Follow the steps below to assign a certificate or add a client secret to the CodeTwo migration application in Azure AD.
- Navigate to Azure Active Directory > App registrations and select the newly added application (in this case: CodeTwo Migration app).
- In the navigation menu, click Certificates & secrets (Fig. 7.). Now, you need to assign either a certificate or client secret to the CodeTwo migration application.
- 3a To assign a certificate, click the Upload certificate button, select your certificate file and click Add (Fig. 8.). The certificate needs to be signed with a key size of 2048 bits.
- 3b To add a client secret, click the New client secret, enter a short description (e.g. CodeTwo Migration app), select the expiration time (whichever suites your needs), and click Add (Fig. 9.).
Make sure to copy the client secret value to clipboard or use it in your CodeTwo migration application straightaway, because once you refresh the page, you will not be able to view that value again. You will have to create another client secret.
Once done, the application registration process is completed. You can now configure a connection to Office 365 in your CodeTwo migration tool. All the information that you need to provide in the Application details step of the server connection wizard (Fig. 10.) is provided in Azure AD either on the application overview page (Application (client) ID and Directory (tenant) ID; refer to Fig. 3. above) or on the Certificates & secrets page (Certificate thumbprint or Client secret).
If you have used a certificate to identify the application, you can enter the Certificate thumbprint only if the certificate associated with the CodeTwo migration application has been added to the CurrentUser\Personal store on the same machine, where the application is installed. If not, use the Import button to add the necessary certificate to that store.
For more information on how to configure server connections, refer to the user's manual: