This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 43%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Hello,
I have been trying to run the Hybrid Configuration Wizard on our Exchange Server.
I know TLS 1.2 is running because I am able to login with my Tenant admin account(at least through IE) in the beginning of the HCW. I have checked all registry keys and they all match what I have read are correct for TLS 1.2 to be enabled...
Meaning:
Both Client and Server under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\ Disabled by Default keys are set to 0 and Enabled is set to 1.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727
and
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319
SchUseStrongCrypto and SystemDefaultTlsVersions are set to 1.
I have downloaded IISCrypto and have ran that on the server to enable TLS 1.2. Everything seems normal on that.
I cannot find any more information on this and I can only think that this is a TLS issue. I am trying to finish up a Full Hybrid environment so I can start migrating mailboxes. I don't want to migrate unless I can get some mailboxes working.
Just to have this issue in plain text...
"The underlying connection was closed. An unexpected error occurred on a send."
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 90%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAZ%3C/text%3E%3C/svg%3E)
Hello, @Matthew Turney,
It's been a long time since I've seen an update from you on this case.
Just wanted to check if the answer shared below helped. If it helped, then would request you to please "Accept the answer" as it would be helpful to others in the community as well. Should you need more help on this, you can feel free to post back.
Best Wishes,
Alex Zhang
Hello, @Matthew Turney,
Is there any update on this thread? If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.
Best Wishes,
Alex Zhang
Hello, @Matthew Turney,
It's been a long time since I've seen an update from you on this case.
Just wanted to check if the answer shared below helped. If it helped, then would request you to please "Accept the answer" as it would be helpful to others in the community as well. Should you need more help on this, you can feel free to post back.
Best Wishes,
Alex Zhang
Hello, @Matthew Turney,
Welcome to the Microsoft Q&A platform!
Notice that you have taken steps to ensure that TLS 1.2 is enabled and being used but the issue still exists. I would suggest you try the following to try and resolve the issue:
1.Check for Updates: Ensure that your Exchange Server and Windows Server are fully up-to-date with the latest updates and patches. Older versions can sometimes cause issues with the Hybrid Configuration Wizard (HCW) and Federation Trust.
2.Check Hybrid Configuration Wizard Logs: The HCW logs can provide more detailed information about where the process is failing. You can find these logs at "C:\Users<YourUsername>\AppData\Roaming\Microsoft\Exchange Hybrid Configuration" on the machine where you ran the HCW.
3.Check Firewall and Proxy Settings: Make sure that there are no firewall or proxy rules blocking the traffic between your Exchange server and the Office 365 endpoints. This can sometimes cause unexpected connection drops.
4.Service and Account Permissions: Verify that the account you are using has the necessary permissions to perform the Hybrid Configuration.
5.Testing Connectivity: Use tools like "Test-FederationTrust" and "Test-OAuthConnectivity" PowerShell cmdlets to test your federation trust and OAuth configuration. This can sometimes reveal more specific problems.
6.Re-run HCW as Administrator: Check again that you are running the HCW with administrative privileges.
What I have provided above is a routine troubleshooting for researching such issues. If your problem is still not solved, here is a document that can help you, based on the error information you provided, please focus on error 3 and its solution, hopefully this will help solve your problem.
（Document Link: https://techcommunity.microsoft.com/blog/exchange/how-to-address-federation-trust-issues-in-hybrid-configuration-wizard-hcw/1144285)
If the answer is helpful please click on ACCEPT ANSWER as it could help other members of the Microsoft Q&A community who have similar questions and are looking for solutions.
Thank you for your support and understanding.
Best Wishes,
Alex Zhang
Hello, @Matthew Turney,
Is there any update on this thread? If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.
Best Wishes,
Alex Zhang
Hello, @Matthew Turney,
Is there any update on this thread? Just checking in to see if above information was helpful. If the issue has been resolved, please mark the helpful replies as answers.
Best Wishes,
Alex Zhang