AADSTS500200

Not specified by the original author.

Fix Microsoft Graph OAuth AADSTS50011 redirect URI mismatch

TL;DR

AADSTS50011 means the redirect URI your app sent is not registered on the Entra app registration. Copy the exact redirect URI from the error and add it to the app registration's redirect URIs. Entra compares them exactly, so mind trailing slashes.

The error

AADSTS50011: The redirect URI specified in the request does not match the redirect URIs configured for the application.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=microsoft graph oauth aaddsts50011 redirect uri mismatch error"

Fix it

Step 1: Copy the redirect URI from the error page

Reproduce the login and copy the redirect_uri value shown in the AADSTS50011 error detail.

Expected: You have the exact URI the app sent.

Step 2: Open the app registration in Entra

Entra admin center -> Identity -> Applications -> App registrations -> [app] -> Authentication.

Expected: You see the registered redirect URIs list.

Step 3: Add the exact URI

Add the copied URI to the list, matching scheme, host, path, and trailing slash exactly, then save.

Expected: The URI appears in the list and saves without errors.

Step 4: Check the platform type

Make sure the URI is registered under the right platform (Web versus Single-page application).

Expected: The URI sits under the correct platform section.

Step 5: Retry the login

Run the OAuth flow again.

Expected: Login completes without AADSTS50011.

When this applies

• Microsoft Graph or Entra logins fail with AADSTS50011
• You added a new environment or changed the app URL
• The app worked locally but fails when deployed

When it doesn't

• The error is AADSTS70011 or another code (different condition)
• The redirect works but tokens are rejected (check the token config)
• You are using device code flow (no redirect URI involved)

Compatibility

Microsoft Entra ID OAuth 2.0 and OpenID Connect. App registrations as of 2026.

Variant phrasings

aadsts50011 redirect uri mismatch fix

Same error. The error page shows the offending URI; trust it over your config memory.

microsoft oauth reply url does not match

Reply URL is the older name for redirect URI. Same list, same exact-match rule.

aadsts50011 dev-machine versus production

Dev-machine URIs registered for local testing do not cover production. Register each environment separately.

Why it happens

Entra only redirects to pre-registered URIs as an anti-phishing control, and it compares them as exact strings. A deploy that changes the path, a missing trailing slash, or an http/https swap all produce AADSTS50011. The app changed; the registration did not follow.

Edge cases

• Single-page apps must register under the SPA platform or silent token renewal breaks
• Wildcard redirect URIs are not allowed; register each URI explicitly
• After adding the URI, wait a minute for propagation before retesting

If it still fails

• Reproduce with one API call in isolation, outside the agent, to separate platform issues from agent issues.
• Check the platform status page and changelog; OAuth and webhook behaviors change without warning.
• Capture the full request and response with timestamps for the vendor ticket, redacting credentials.
• Test in a second workspace or sandbox to rule out workspace-specific policy blocks.
• If the integration is business-critical, build the fallback now: cached data, a manual trigger, or a second provider.

Prevention

• Store OAuth credentials in a secrets manager with rotation reminders.
• Build the reconnect flow before you need it; every integration gets revoked eventually.
• Log token ages so expiring grants are visible ahead of time.
• Keep a sandbox integration for testing config changes.
• Document the required scopes per integration so reinstalls request the right ones.

Provenance

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

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

Thread query: microsoft graph oauth aaddsts50011 redirect uri mismatch error

TL;DR: AADSTS50011 means the redirect URI your app sent is not registered on the Entra app registration. Copy the exact redirect URI from the error and add it to the app registration's redirect URIs. Entra compares them exactly, so mind trailing slashes.

Not specified by the original author.

TL;DR

Fix this in Help center SSO by acting on the exact symptom first: launch the widget through a top level sign in redirect instead of inside the embedded frame, allow the session cookie to be sent in the widget context, and test the full path from article to widget as an SSO reader. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Help center SSO users are logged out when opening the embedded support widget

Use this when

• Work in Help center SSO shows this exact symptom: Help center SSO users are logged out when opening the embedded support widget.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help center SSO, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: launch the widget through a top level sign in redirect instead of inside the embedded frame, allow the session cookie to be sent in the widget context, and test the full path from article to widget as an SSO reader. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help center SSO that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Help center SSO users are logged out when opening the embedded support widget

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - help center SSO users logged out when opening embedded support widget

The how to phrasing for the same problem in Help center SSO. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help center SSO troubleshooting for this symptom

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

Why it happens

The embedded frame is a third party context for the session cookie, so the browser withholds it and the widget sees an anonymous reader and forces a logout and login cycle.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help center SSO at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: help center SSO users logged out when opening embedded support widget

TL;DR: Fix this in Help center SSO by acting on the exact symptom first: launch the widget through a top level sign in redirect instead of inside the embedded frame, allow the session cookie to be sent in the widget context, and test the full path from article to widget as an SSO reader. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

AADSTS90002: Tenant '[tenant-id]' not found

TL;DR

The tenant in your auth request does not exist. Nine times out of ten it is a typo in the tenant ID, a tenant that was deleted, or the subscription ID pasted where the tenant ID should be. Verify the tenant ID in the portal and fix the request.

The error

AADSTS90002: Tenant '[tenant-id]' not found. This may happen if there are no active subscriptions for the tenant. Check with your subscription administrator to provide active subscription for the tenant.

Fix it

1. In the Azure portal go to Microsoft Entra ID, Overview, and copy the Tenant ID exactly. Expected: you have the real tenant ID on your clipboard.
2. Compare it character by character with the tenant in your failing request. Expected: you find the typo or mismatch.
3. If you pasted a subscription ID where the tenant ID belongs, swap it. The subscription ID is not the tenant ID. Expected: the auth request carries the tenant ID.
4. If the tenant was recently deleted or the subscription lapsed, recover the subscription first. Expected: an active subscription backs the tenant again.
5. Retry the auth request with the corrected tenant. Expected: the error is gone.

When to use this

• An agent sees AADSTS90002 during login, token acquisition, or CLI auth.
• A script hardcodes a tenant ID that may have changed.

When NOT to use this

• AADSTS50034 (the user is missing) or AADSTS700016 (the app is missing). The tenant itself is fine in those cases.
• AADSTS50020 (the account is fine, it just is not in this tenant).

Compatibility

• Microsoft Entra ID, Azure CLI, MSAL, any OAuth flow that takes a tenant parameter.

Variant phrasings

• "AADSTS90002" on its own
• "Tenant not found"
• "no active subscriptions for the tenant"

Root cause

The tenant lookup happens before anything else in the auth pipeline. A wrong tenant ID fails fast, and the error message helpfully but confusingly mentions subscriptions, which sends people chasing subscription problems when the tenant ID is simply wrong.

Edge cases

• B2C tenants and work tenants have different ID formats in some flows. Make sure you copied the ID from the right directory.
• Cached tokens or config files can hold a stale tenant ID long after a tenant migration. Search your config for the old value.

The TROUBLESHOOTING.md in okapi-ca/ms-365-admin-mcp-server documents the AADSTS90002 pattern: the tenant specified in the authentication request cannot be found, typically because of a typo in the tenant ID or a deleted tenant, with the fix being to verify the tenant ID in the Azure portal. Microsoft's documented meaning for the code points the same way: check that the tenant exists and has an active subscription.