Hybrid Configuration Wizard Failure

During a recent migration I ran into a Hybrid Configuration Wizard Failure pointing the Exchange at a new Microsoft tenant. Firstly, these are usually these are simple a case of connectivity/ Firewall or TLS 1.2 being disabled on the server in question. Firstly this also, caused further confusion since it would connect to the previous M365 tenant with no issues. However, this problem in the case is different and is due to the HCW not containing the Exchange REST base V3.0+ module. If you receive the following error then don’t worry we have the solution below.

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

Microsoft Tech Community

After reviewing the below list of Timelines of RPS deprecation it became apparent that the new tenant I was working in was register in May 2023 but had not had the HCW ran until June 2023 which caused the issue. Firstly, Microsoft Originally the depreciation was set to if past June 1st the tenant could not reenable RPS. However, the data has been pushed further back since Microsoft Exchange team have not released a new version of HCW. Finally the good news new version will contain the required built in modules to mitigate this issue.

Timeline of RPS deprecation

TimeframeState of RPS protocol
March 2023All current WW tenants can opt-out of RPS deprecation using the diagnostic, until September 2023
April 2023WW tenants created on April 1st and newer will have RPS disabled by default, and can re-enable it (using diagnostic) until June 2023. After July 2023 onwards, new tenants thus created will not be able to re-enable RPS.
May 2023We disable RPS for WW tenants (created before April) who never used RPS and have not asked for an extension. Re-enablement of RPS is possible using the diagnostic until September 2023.
June 15, 2023 We will start disabling RPS for WW tenants who have not opted-out or re-enabled RPS yet and have used it in the past. Re-enablement of RPS using the diagnostic is possible until September 2023 (unless tenant was created after April 2023).
July 2023WW tenants created after July 1st will have RPS disabled permanently. Diagnostics cannot re-enable RPS for those tenants.Tenants created from July 1st onwards must use Exchange Online PowerShell v3 module using Connect-ExchangeOnline without the UseRPSSession parameter.
September 2023RPS opt-out / re-enablement diagnostic for WW tenants is retired.
October 2023We start blocking RPS for all tenants, no matter the tenant creation date, size, or opt-out status or cloud environment (WW, GCC, etc.) they use.All tenants must use Exchange Online PowerShell v3 module using Connect-ExchangeOnline without the UseRPSSession parameter.

How To Resolve: Hybrid Configuration Wizard Failure

Use the following Link and sign into your Microsoft Office 365 Admin Center with an account with appropriate permissions.
Firstly, the Help and support feature should automatically open. Secondly, Next click “Run Tests” after approx. Finally wait 1 minute after you get the prompt to confirm you want to Disable the restriction in your tenant.

Once the confirmation has been received, you can rerun the Exchange Hybrid Configuration Wizard and it will instantly work as expected.

Diag: Enable RPS in EXO

Please Leave a Comment

Firstly, the above has helped you in increase the efficiency or troubleshooting for Exchange tasks. If so then please let us know by leaving a comment or feel free to share the article below. Above all i you have any errors or require more details on anything covered then please comment. Lastly, you can find more Exchange articles by clicking here.

Similar Posts

One Comment

  1. Thank you this helped me so much, I had just built out a new hybrid server for a new tenant project at for the MSP I work at. Was so confused with this error till I found your guide. kudos sir you saved me on this one.

Leave a Reply

Your email address will not be published. Required fields are marked *