Forum Discussion
dgk62
Feb 13, 2023Copper Contributor
Federation Relationship issue
Hi, We have a classic Hybrid configuration with several on-premises Exchange 2019 CU12 servers. Everything works as expected but we fail with Test-FederationRelationship cmdlet. On-premises serv...
FcoManigrasso
Feb 14, 2023Iron Contributor
Hello!
Did you re-run the hybrid Wizard in order to check if it returns any error? It usually helps a lot troubleshooting such scenarios. If the Wizard also comes back with the error "Object reference not set to an instance of an object " check this please: https://learn.microsoft.com/en-us/exchange/troubleshoot/hybrid-configuration-wizard-errors/object-reference-not-set-to-an-instance-of-an-object-error
Did you re-run the hybrid Wizard in order to check if it returns any error? It usually helps a lot troubleshooting such scenarios. If the Wizard also comes back with the error "Object reference not set to an instance of an object " check this please: https://learn.microsoft.com/en-us/exchange/troubleshoot/hybrid-configuration-wizard-errors/object-reference-not-set-to-an-instance-of-an-object-error
dgk62
Feb 14, 2023Copper Contributor
Hi,
Thank you for your answer.
I've already tried the approach. Ok. I'll look again.
I have an idea, that the STS signing certificate should be installed on Exchange servers alongside with the Federation certificate. Now, it's accessible only through Federation metadata.
Regards,
Dmitry.
Thank you for your answer.
I've already tried the approach. Ok. I'll look again.
I have an idea, that the STS signing certificate should be installed on Exchange servers alongside with the Federation certificate. Now, it's accessible only through Federation metadata.
Regards,
Dmitry.
- sigfridoboSep 15, 2023Copper Contributor
dgk62 did u manage to solve the issue?
We are in the process to deploy a new exchange 2019 server into a Hybrid 365-onpremise enviroment but we keep getting an error when we run:
Test-FederationTrust -UserIdentity email address removed for privacy reasons -Verbose
on the 7th verifycation which is "token validation" we get a "Failed to validate delegation token"