You mentioned you're using TLS 1.2, which is good. Just double-check that it's enabled correctly. You can do this using the registry or PowerShell, but it’s also important to ensure that TLS 1.0 and 1.1 are disabled. Additionally, check the SSL certificate, it should be up-to-date. After this try running the HCW again to see if it works. For more details on Federation Trust issues and their solutions, you may also refer to https://techcommunity.microsoft.com/blog/exchange/how-to-address-federation-trust-issues-in-hybrid-configuration-wizard-hcw/1144285
Let me know if you face any issue.
Hybrid Configuration Wizard Exchange 2010
Hello,
I am trying to use the Hybrid Configuration Wizard on Exchange 2010; but, I ran into a Federation Trust Failed issue when trying to enable Federation Trust.
It says Federation Trust Failed: Unable to access the Federation Metadata document from the federation partner.
I am on Exchange 2010 SP3, up to date on Server 2012, TLS 1.2, and .Netframework 4.5 / 3.5
Any help would be much appreciated!
Anyone know how to resolve this?
-
Amit Singh 5,221 Reputation points
2025-01-17T04:41:35.0833333+00:00
2 additional answers
Sort by: Most helpful
-
Bruce Jing-MSFT 10,075 Reputation points Microsoft External Staff
2025-01-17T07:35:40.33+00:00 As per as research, you can try to run PowerShell as Administrator to update the FederationTrust with cmdlet:
Update-AdfsRelyingPartyTrust -TargetName "trustname" -Metadatafile FederationMetadata.xml.
If it doesn't work, please run the Exchange Hybrid Wizard and make sure the federation metadata URL is accessible. If there are more error messages, please feel free to let us know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
-
Guan, Raymond 20 Reputation points
2025-03-06T20:03:40.0366667+00:00 Disabled TLS 1.0 and 1.1 worked; but, I had to enable TLS for .NETFramework 3.5 for our OWA to be fully functioning.