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:

1. Failed to configure Exchange Online outbound connector (problems with remote operations in PowerShell)
2. Access Denied
3. Parameter count mismatch
4. Exchange Online inbound connector is created in a disabled state

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:

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

or

Connecting to remote server ps.outlook.com failed with the following error message : For more information, see the about_Remote_Troubleshooting Help topic.

Solution

Microsoft suddenly updated their policies in Exchange Online and started blocking the Remote PowerShell (RPS) connections for all Microsoft 365 tenants created on or after April 1, 2023. The RPS protocol is also used by our connectors configuration wizard. 

To fix this, you can re-enable RPS in your Microsoft 365 tenant by following these steps.

You can also configure CodeTwo Exchange Online connectors manually in the Exchange admin center of your tenant. See the following articles for more information:

• Manual configuration of Exchange Online connectors
• How to manually remove connectors and transport rule in Microsoft 365

Re-enable RPS in the Microsoft 365 admin center

To re-enable the Remote PowerShell (RPS) protocol for your tenant, complete the following steps:

1. Click this link provided by Microsoft to access the RPS self-service tool. If you're not signed-in, sign in using your global admin credentials when prompted.
2. The Microsoft 365 admin center will show up with the RPS self-service tool displayed in the pane on the right. Click Run Tests (Fig. 1.) to check the RPS status for your tenant.

Fig. 1. Running the tests to check the current RPS status for your tenant.

3. Once the tests have completed, you'll see the result indicating whether Microsoft has disabled or hasn't disabled the RPS protocol for your tenant. To re-enable the protocol (or temporarily opt out of RPS disablement), select the checkbox and click Update (Fig. 3.).

Fig. 3. Temporarily opting out of the disablement of the RPS protocol.

More information about the RPS deprecation

Microsoft first planned to retire the RPS protocol for all Microsoft 365 tenants in June 2023. However, on March 27, 2023, Microsoft published info that starting April 1, 2023, they will start blocking RPS connections for all tenants created on or after April 1, 2023. It is still possible to re-enable RPS in those tenants* by using the RPS self-service tool (as described above). However, the self-service tool will be retired on September 1, 2023, and Microsoft will begin turning off RPS in all Microsoft 365 tenants starting October 1, 2023. 

CodeTwo is currently working on a new method of configuring Exchange Online connectors automatically in CodeTwo Admin Panel. The new method will no longer use the RPS protocol and will be available well in advance before the scheduled RPS deprecation.

Troubleshooting the 'Access Denied' error

You are not able to configure Exchange Online connectors by using the program’s wizard. The following (or similar) error is displayed:

Connecting to remote server ps.outlook.com failed with the following error message : [ClientAccessServer=XXXXX,BackEndServer=YYYYY,RequestId=ZZZZZ, TimeStamp=MM/DD/YYYY H:MM:SS PM] Access Denied For more information, see the about_Remote_Troubleshooting Help topic.

A similar problem occurs when you try to deregister your tenant from CodeTwo Admin Panel.

Solution

Our software connects to Microsoft 365 tenants via PowerShell and uses PowerShell commands to manage Exchange Online connectors. The above error means that our program could not access your tenant with the credentials you provided. The most probable cause is that you used the credentials of an account that does not have enough permissions. You need to sign in as a global admin of your Microsoft 365 tenant (learn more).

Troubleshooting the 'Parameter count mismatch' error

You are not able to create an inbound connector for your Microsoft 365 tenant - you get the following error:

Parameter count mismatch.

This error may occur when you configure a connector in Exchange admin center (Fig. 4.), via PowerShell (Fig. 5.) or when you set connectors automatically in CodeTwo Admin Panel (Fig. 6.).

Fig. 4. The Parameter count mismatch error in EAC.

Fig. 5. The Parameter count mismatch error in PowerShell.

Fig. 6. The Parameter count mismatch error in CodeTwo Admin Panel.

Solution

You might have encountered a rare Microsoft datacenter problem, caused by a recent update to Microsoft 365. This issue, referred to by Microsoft as Service Degradation EX102579, is not related to our software. Microsoft has already deployed the fix and claims that all services are now restored.

If, despite the above, you are still experiencing the 'Parameter count mismatch' error, we advise you to contact Microsoft support. 

To check the current status of your Microsoft 365 services, 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 the above-mentioned problem still occurs, it will be displayed in the Exchange Online service category.