Error message in Microsoft Remote Connectivity Analyzer Skip to main content
https://support.okta.com/help/answers?id=906f0000000i0fnia0&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
John NickellJohn Nickell 

Error message in Microsoft Remote Connectivity Analyzer

When I run the SSO connectivity test here: https://testconnectivity.microsoft.com after converting our federation to Okta, from our on prem ADFS, I always receive the error below.  While authentication seems to work, it'd be nice to undertand why I get an error now, when before (on ADFS) we got the all clear.  I don't want to hit a troubleshooting issue with M$ that they say this is causing the issue.  My searches so far haven't turned up any Okta related results.  

Error in the "Analyzing the ADFS metadata document for configuration problems." section: 
The Integrated Windows authentication endpoint is missing on the internal metadata document
Drew PadorDrew Pador (Okta, Inc.)
Hello John,

Thanks for posting in the Okta Community!

Have you already verified that the endpoint has been declared in the metadata document prooerly? It may just need to be entered so that the configuration knows where to look.

I think your issue would be best resolved if you submitted a support ticket so that a technician can take a look at your org and see if there is an issue with our end.Starting there would prevent you from having to engage MS for troublshooting.

Please let me know if you have any other comments or questions.


Regards,
Drew Pador
Technical Support Engineer
User-added image
John NickellJohn Nickell
To the best of my understanding the declaration of the endpoint is up to Okta.  the ADFS metadata information is coming from https://<ourdomain>.okta.com/app/office365/<guid>/sso/wsfed/mex.  We have no control over what's being served at this web address.  

I believe I did have a service ticket opened at one point (on a related issue) in which the technician stated that this was occuring because the testconnectivity tool is looking for strictkly ADFS responses.