Hi,

At the final step of the Hybrid Wizard (Validating Hybrid Agent for Exchange usage), I am getting this error message. I've searched for this error and cannot find the correct fix. Thanks.

The log files show his error:
*ERROR* 10349 [Client=UX, Page=HybridConnectorInstall, Thread=15] 
                                      The connection to the server 'fdde59f1-85fd-48b6-bbe4-0bf434e02b29.resource.mailboxmigration.his.msappproxy.net' could not be completed., The call to 'https://fdde59f1-85fd-48b6-bbe4-0bf434e02b29.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' timed out. Error details: The request channel timed out attempting to send after 00:00:00.0077217. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. --> The HTTP request to 'https://fdde59f1-85fd-48b6-bbe4-0bf434e02b29.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0077217. The time allotted to this operation may have been a portion of a longer timeout., The request channel timed out attempting to send after 00:00:00.0077217. Increase the timeout value passed to the call
                                       to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout., The HTTP request to 'https://fdde59f1-85fd-48b6-bbe4-0bf434e02b29.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0077217. The time allotted to this operation may have been a portion of a longer timeout.

Hi Team - Is the limit of running 50 parallel hybrid's a hard limit or just how many Microsoft support?

Is there a roadmap to increase this number in the future. We are looking to create a hybrid to 100+ tenants and not sure if we should proceed. Thanks 

Hi everyone,

I have an issue with this wizard, the version detected isn't the same as the real version of my exchange 2016 server so it prevents me to perform any update/upgrade.



Do you have any idea about how to fix it ?

Thanks

I am stuck with the following error trying to configure modern hybrid. Support is not being much help and I am hitting a wall with this. Could you please tell me where this duplicate value is coming from and how to clear it?

2023.09.17 15:06:27.204 10333 [Client=UX, fn=SendAsync, Thread=20] FINISH Time=194.0ms Results=BadRequest {"error":{"code":"InternalUrl_Duplicate","message":"Internal url 'https://ex.atomicdata.com/' is invalid since it is already in use","innerError":{"date":"2023-09-17T15:06:28","request-id":"30096340-e0a8-4d9e-9ac1-7a69035ff785","client-request-id":"30096340-e0a8-4d9e-9ac1-7a69035ff785"}}}
2023.09.17 15:06:27.210 10407 [Client=UX, Thread=20] Updating Local Client Configuration File
2023.09.17 15:06:27.225 10341 [Client=UX, Page=HybridConnectorInstall, Step=ConfigOrgRoute, Thread=20] FINISH Time=231.0ms Results=Failed
2023.09.17 15:06:38.809 10062 [Client=UX, Page=HybridConnectorInstall, Thread=1] [Close/Cancel] Pushed: True
2023.09.17 15:06:38.813 10266 [Client=UX, Page=HybridConnectorInstall, Thread=1] FINISH Time=11.8s

RayC567netau : HCW supports hybrid with Exchange CU13. Its just that in our logs, it doesn't tell that CU13 is supported, we will rectify this in next version of HCW.

Rio316 thanks for sharing the solution.

Solution

Set-User -identity email address removed for privacy reasons -RemotePowerShellEnabled $True

Bad Request when connecting to Exchange Online PowerShell - Exchange | Microsoft Learn

Brilliant documented ...

Tried:
-Timezone set to utc and then we got

Value cannot be null. Parameter name ipString 

-- there is only 1 nic

-Granted user global admin permissions but the same error.

-Updated exchangemanagement module to 3.3 (latest)

-pressed f12 and opened exchange online powershell 

got the error 

New-Pssession : [outlook.office365.com] Connecting to remote server outlook.office365.com failed with the following
error message : Bad Request For more information, see the about_Remote_Troubleshooting Help topic.

which finally helped solving the issue

When is HCW going to be updated to support Exchange 2019 CU13? Its over 4 months since it was released now.

Latest HCW only supports CU12, and refuses to connect to O365. 

Get weird errors:

• The UTC represented when the offset is applied must be between 0 and 10,000. Parameter name offset.
• Value cannot be null. Parameter name ipString. Get this after adjusting time to UTC or UTC+1.

After using F12 and checking log in HCW, find that CU12 is latest 2019 version supported.

Need to run this to update certificates which are due to expire shortly, or will have to resort to manually applying them to connectors.

Or is there a separate link to an updated HCW?

wazcal No you don't need to upgrade HCW, if you have already configured Hybrid in past as is your case.

In future, if you plan to re-run HCW, only then you should use the latest HCW to configure Hybrid.

"We recommend that all customers download the latest version" does this mean that all environments with HCW currently deployed need to upgrade to this new version? Or will the current version continue to work fine and action is only required if you need the REST-based APIs? For example we have two separate on prem Exchange 2019 environments (fully patched) with Hybrid AD/Exchange configurations with 365 - do we need to upgrade the HCW on both of these? What is the impact if we do not? Thanks in advance for your response.