How to fix problems with the configuration of CodeTwo Exchange Online connectors

Use the links below to find solutions to the most common issues related to the configuration of Exchange Online connectors in CodeTwo Admin Panel:

• Failed to configure Exchange Online inbound connector
• Failed to configure Exchange Online outbound connector
• Failed to configure Exchange Online transport rule

Failed to configure Exchange Online inbound connector

You are not able to configure the Exchange Online inbound connector by using either the tenant registration wizard or the connectors configuration wizard. The following (or similar) error is displayed:

Failed to configure Exchange Online inbound connector. Automatic configuration of Exchange Online Connectors could not be completed.

Fig. 1. Failed to configure Exchange Online inbound connector.

Solution

First, make sure that you have signed in as a global admin of your Microsoft 365 tenant after clicking the Authorize button and using the authorization code (learn more). To reattempt the connectors configuration and check your sign-in credentials, click Try again (see Fig. 1.) and repeat the configuration procedure.

If you signed in using the appropriate account but the problem persists, check the current status of your Microsoft 365 services. To do it, sign in to your Microsoft 365 admin center and choose Health > Service health from the left pane (you may need to click Show all first). If there are any ongoing problems, they will be displayed in the Exchange Online service category.

If no problems are reported for the Exchange Online service, you can also try to configure Exchange Online connectors manually. To do it, click Close this wizard for now (see Fig. 1.) and follow the instructions you can find here. And if you prefer doing things with PowerShell, you can find relevant manual configuration steps in this Knowledge Base article. 

Failed to configure Exchange Online outbound connector

You're using a wizard in CodeTwo Admin Panel to automatically configure (create, remove, update, etc.) Exchange Online connectors and you get the following error (Fig. 2.):

Failed to configure Exchange Online outbound connector. Automatic configuration of Exchange Online Connectors could not be completed.

Fig. 2. Failed to configure Exchange Online outbound connector.

Solution

This error might occur because of problems with accessing your Microsoft 365 tenant, a pending propagation of changes across your tenant, etc.

Try configuring the connectors automatically again after some time. If the problem persists, you can configure CodeTwo Exchange Online connectors manually in the Exchange admin center of your tenant - see our step-by-step guidelines.

Failed to configure Exchange Online transport rule

You're using a wizard in CodeTwo Admin Panel to automatically configure (create, remove, update, etc.) Exchange Online connectors and you get the following error (Fig. 3.):

Failed to configure Exchange Online transport rule. Automatic configuration of Exchange Online Connectors could not be completed.

Fig. 3. Failed to configure Exchange Online transport rule.

Solution

The error might occur if the value of your Display Name attribute in Entra ID (Azure AD) has more than 128 characters. This limit is imposed by Microsoft and applies to users who create mail flow (transport) rules in Exchange Online.

To verify and change your Display Name attribute’s length, sign in to the Microsoft Entra admin center with the same Global Administrator account that you used in the wizard in CodeTwo Admin Panel. Next, go to Identity > Users > All users and click your Global Administrator user on the list (Fig. 4.).

Fig. 4. Accessing your user profile in the Microsoft Entra admin center.

Finally, click Edit properties, shorten the value in the Display name field and click Save to save the changes (Fig. 5.). Wait some time for the changes to propagate.

Fig. 5. Shortening the value of the Display name attribute.

Now, go back to CodeTwo Admin Panel and re-launch the wizard – this time the configuration of Exchange Online Connectors should complete successfully.