Connecting to source Office 365
Once the installation of CodeTwo Exchange Migration is finished, you have to choose a source environment from which the data will be pulled and migrated to selected mailboxes on target Exchange Server. This article describes how to connect to source Office 365 tenant.
Info
The software accesses your source Office 365 mailboxes via Exchange Web Services (EWS). The EWS protocol is also used to migrate items to target Exchange Server.
You can create a new source connection when you configure a migration job: click Create a new migration job on the How to start card (see Fig. 1.) and select Office 365. Type the name of your job, and proceed to the Source mailboxes step. Select Add new source connection from the Source server drop-down list to open the Office 365 source server connection wizard. You can also start the wizard by clicking the Settings (
) button on the Defined source server connections card (Fig. 1.) and choosing New > Office 365 connection.
Fig. 1. Creating a new source server connection.
The Office 365 source server connection wizard opens. First, choose if you want to connect to Office 365 global or to Office 365 Germany (Fig. 2.). Since Office 365 Germany and Office 365 global (or simply Office 365) are completely independent clouds, it is not possible to use the Office 365 global credentials to log in to Office 365 Germany and vice versa. If your Office 365 email address ends with .de, for example admin@my-company.onmicrosoft.de, you’re using the Office 365 Germany cloud. Read more about Office 365 Germany.
Fig. 2. Selecting Office 365 cloud.
Next, in the Admin account step, provide credentials of an Office 365 account that will access user mailboxes on your source server (Fig. 3.). Make sure that this account is assigned the necessary management roles, as shown in the wizard, or let the program do it for you in the next step. Learn more about source Office 365 account requirements.
We also recommend to enter the primary email address from the *.onmicrosoft.com domain for this account (or *.onmicrosoft.de in the case of Office 365 Germany), for example admin@my-company.onmicrosoft.com. This will help prevent any issues if you change the domain on your source server during the migration. Learn more.
Fig. 3. Providing admin account credentials.
Important
If this admin account has multi-factor authentication (MFA) enabled, use the app password instead of the regular Office 365 password. Otherwise, the configuration will fail. Learn more.
In the next step, Configuration, the wizard will set up the connection to your target Office 365 server. Click Configure and verify the results. In case the account provided in the previous step lacks some of the necessary roles, the program will attempt to assign them automatically (Fig. 4.). Click Yes to accept.
Fig. 4. Assigning the missing management roles.
You might be prompted to provide the credentials of another account that is assigned the Global administrator role (Fig. 5.). This account will not be used to connect to the Office 365 tenant to perform the migration, but only to assign the missing roles. Learn more about the management roles.
Fig. 5. Providing credentials of an account that has appropriate roles assigned.
Important
Remember to use the app password if your Global administrator account is also MFA-enabled. Otherwise, you will not be able to assign the missing roles by using this account.
Once the setup is complete (Fig. 6.), click Finish to close the window (if you encounter any problems, see Troubleshooting). You can now move on to configure a target on-premises Exchange server of your choice.
Fig. 6. Configuration of a source connection with Office 365.
When you complete the wizard, the new connection should be displayed on the Defined server connections card (Fig. 7.).
Fig. 7. Defined source server connections.
See next
Connecting to a target Exchange server