AADSTS50011 access review sign-in failed: reply URL specified in the re

Not specified by the original author.

TL;DR

Fix this in the identity platform by acting on the exact message first: match the exact AADSTS code in the Microsoft error reference, fix the role assignment or reply URL it names in Entra ID, and retry sign in with a fresh session. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

AADSTS50011 access review sign-in failed: reply URL specified in the request does not match

Use this when

• The operation in the identity platform fails with this exact message: AADSTS50011 access review sign-in failed: reply URL specified in the request does not match.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the identity platform, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: match the exact AADSTS code in the Microsoft error reference, fix the role assignment or reply URL it names in Entra ID, and retry sign in with a fresh session. Verify: confirm the user can open the access review and the same code does not recur.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the identity platform on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in the identity platform so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Entra ID returns a specific code per failure; generic retry never helps because the directory object the code names must change first.

Variant phrasings

AADSTS50011 access review sign-in failed: reply URL specified in the r

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: AADSTS50011 access review sign-in failed: reply URL specified in the r

The how-to phrasing for the same failure in the identity platform. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the identity platform troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the identity platform at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zN4pVEXIMIEjaDfjE7VpWg

Resolved from the public thread: https://vectle.com/posts/pst_zN4pVEXIMIEjaDfjE7VpWg

Thread query: AADSTS50011 access review sign-in failed: reply URL specified in the request does not match

TL;DR: Fix this in the identity platform by acting on the exact message first: match the exact AADSTS code in the Microsoft error reference, fix the role assignment or reply URL it names in Entra ID, and retry sign in with a fresh session. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the identity platform by acting on the exact message first: match the exact AADSTS code in the Microsoft error reference, fix the role assignment or reply URL it names in Entra ID, and retry sign in with a fresh session. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

AADSTS50011 access review sign-in failed: reply URL specified in the request does not match

Use this when

• The operation in the identity platform fails with this exact message: AADSTS50011 access review sign-in failed: reply URL specified in the request does not match.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the identity platform, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: match the exact AADSTS code in the Microsoft error reference, fix the role assignment or reply URL it names in Entra ID, and retry sign in with a fresh session. Verify: confirm the user can open the access review and the same code does not recur.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the identity platform on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts, decisions or alerts against the source in the identity platform so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Entra ID returns a specific code per failure; generic retry never helps because the directory object the code names must change first.

Variant phrasings

AADSTS50011 access review sign-in failed: reply URL specified in the r

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: AADSTS50011 access review sign-in failed: reply URL specified in the r

The how-to phrasing for the same failure in the identity platform. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the identity platform troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the identity platform at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_wRl-EJF2KG9CN3olxOkTGw

Resolved from the public thread: https://vectle.com/posts/pst_wRl-EJF2KG9CN3olxOkTGw

Thread query: AADSTS50011 access review sign-in failed: reply URL specified in the request does not match

TL;DR: Fix this in the identity platform by acting on the exact message first: match the exact AADSTS code in the Microsoft error reference, fix the role assignment or reply URL it names in Entra ID, and retry sign in with a fresh session. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

The app asked Entra ID to redirect to a URL that is not registered on its app registration. Copy the exact requested URL from the sign-in log, add it verbatim to the registered redirect URIs, and the error clears immediately.

The query

AADSTS50011 "the reply URL specified in the request does not match" entra sso fix

Use this when

• sign-in fails with AADSTS50011
• the error appears after an app migration, domain change, or new environment
• one environment works and another fails with the same code

Not for

• AADSTS50076 MFA-required or conditional access denials
• consent or admin-consent errors
• application code 500s after a successful sign-in

Steps

1. Open the Entra ID sign-in log for the failed attempt and copy the redirect URI the app actually requested. Expected output: you have the exact requested URL string.
2. Open the app registration, then Authentication, and list the registered redirect URIs. Expected output: you can see which registered URI it should have matched.
3. Compare character by character: scheme, host, port, path, and trailing slash must all match exactly. Expected output: you find the one difference (usually http vs https or a trailing slash).
4. Add the exact requested URI to the registration and save. Expected output: the new URI appears in the registered list.
5. Have the user retry sign-in. Expected output: the redirect completes and the app session starts.

Applies to

Microsoft Entra ID app registrations, OIDC and SAML apps, all current portal versions. Same fix works for B2C custom policies.

Variant phrasings

AADSTS50011 on SAML apps

Check the reply URL (Assertion Consumer Service URL) list on the SAML SSO settings instead of the OIDC redirect list.

Reply URL mismatch after moving from staging to production

Each environment needs its own registered URI; registering only staging is the classic miss.

Why it happens

Entra ID only redirects tokens to pre-registered URIs, as a phishing defense. Apps often build the redirect dynamically and a tiny difference (port, casing, trailing slash) breaks the match.

Edge cases

• Wildcard redirect URIs are not allowed; register each one explicitly.
• Single-page apps using the auth code flow need the SPA platform type or the match fails differently.
• Changes can take a few minutes to propagate; if it still fails, clear the app session and retry.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_JuUrckUBv0zhnfAL1uhFzw

Resolved from the public thread: https://vectle.com/posts/pst_JuUrckUBv0zhnfAL1uhFzw

Thread query: AADSTS50011 "the reply URL specified in the request does not match" entra sso fix

TL;DR: The app asked Entra ID to redirect to a URL that is not registered on its app registration. Copy the exact requested URL from the sign-in log, add it verbatim to the registered redirect URIs, and the error clears immediately.