SSO Doctor

All troubleshooting guides

AADSTS50011 with SAML: troubleshoot an Entra reply URL mismatch

By SSO Doctor · Technical guide

For a SAML integration, AADSTS50011 indicates that the request’s AssertionConsumerServiceURL does not match an accepted Reply URL in Microsoft Entra ID. First establish the application’s correct callback endpoint; do not approve a URL solely because it appears in an error.

Confirm this is the SAML flow

This guide covers SAML enterprise applications. An OAuth/OIDC redirect URI error needs its own app-registration investigation. Record the protocol, tenant, application identifier, error time, and the sign-in route that failed.

Build a three-way comparison

Record each value independently. Check scheme, host, port, path, and trailing slash. Also check whether a proxy or stale environment setting is generating the request. Keep Entity ID and Reply URL in separate rows of your notes.

Worked example: an old application hostname

Requested ACS: https://old-payroll.example.com/saml/acs
Configured Reply URL: https://payroll.example.com/saml/acs
Vendor-confirmed production ACS: https://payroll.example.com/saml/acs

All values here are synthetic. The request differs from both the configured and confirmed endpoint. Investigate why the application still generates the old hostname before adding another Reply URL. Adding it could preserve an obsolete route.

Apply the smallest justified correction

  1. Identify the exact enterprise application involved in the failed request.
  2. Save the current relevant configuration and agree on a rollback.
  3. If the request uses the correct, approved endpoint but Entra lacks it, update the appropriate Reply URL configuration. If the request is wrong, correct the SP configuration that generates it.
  4. Start a fresh sign-in through the original failing route.
  5. Confirm the mismatch error is gone and the application establishes the expected session. Record any subsequent error separately.

Do not add a wildcard or an unverified endpoint to make the error disappear. Do not alter signing trust, audience, or NameID without separate evidence. A successful redirect alone does not prove application access is correct.

Keep evidence organized in SSO Doctor

Use SSO Doctor to inspect supported SAML evidence and document explicit endpoint expectations. The free SAML Decoder is available from Free Tools in the application. A decoded request does not expose Entra’s current administrative configuration; collect that separately.

Reference

Microsoft’s SAML AADSTS50011 troubleshooting article explains the request ACS and configured Reply URL comparison. Follow application-vendor guidance for the authoritative endpoint.

Related guides