There is no error displayed in the User interface. However, the wizard is stuck in an endless loop until the connector is exited.
Review of the Merge1 logs show the following:
2022-03-03 16:51:01,873 [16] INFO Merge1.Portal.Controllers.ConfigurationController - OAuthCallback started...
2022-03-03 16:51:01,873 [16] INFO Merge1.Portal.Controllers.ConfigurationController - State: ''
2022-03-03 16:51:01,873 [16] ERROR Merge1.Portal.Controllers.ConfigurationController - Can't find current connector.
2022-03-03 16:51:01,877 [16] ERROR Merge1.Portal.Controllers.ConfigurationController - Error on OAuthCallback. UserID=0, RequestRawURL=/Configuration/OAuthCallback?admin_consent=True&tenant=788b1984-3887-4f80-b53d-2b98d513f61b
System.InvalidOperationException: Unexpected error, connector should not be null at Merge1.Portal.Controllers.ConfigurationController.OAuthCallback()
2022-03-03 16:51:01,878 [16] INFO Merge1.Portal.Controllers.ConfigurationController - Ending OAuthCallback...
This issue can be caused when the Admin Console is being accessed via a different URL than what was configured during application registration for the Redirect URI.
For Example:
The Admin Console is being accessed via URL https://192.168.2.107/Configuration.

The Redirect URI configured in Azure Active Directory during application registration is using https://MergeSRV.Merge1.com/Configuration.

To resolve this issue access the Admin Console using the same URL that is configured in the Redirect URI during application registration in Azure.