Azure AD B2C Redirect URI Mismatch Error Despite Correct Configuration

Sangbuem Choo 25 Reputation points
2023-08-23T02:42:01.9166667+00:00

Hello everyone,

I've been facing an issue with Azure AD B2C where I'm getting a redirect URI mismatch error (AADB2C90006), even though I've confirmed that the redirect URI is correctly configured in the portal. Here's a brief rundown of my situation:

Error Message:

Sorry, but we're having trouble signing you in. AADB2C90006: The redirect URI 'dleo-dev.z01.azurefd.net' provided in the request is not registered for the client id '1b9096cc'.

What I've tried

  • Redirect URI: I've verified that the redirect URI https://dleo-dev.z01.azurefd.net is configured for the application with client ID 1b9096cc.
  • Audit Logs: All operations in the audit logs show "Success", with no failures related to the authentication process.

I'd really appreciate any insights or guidance on how to troubleshoot this further. Has anyone else faced a similar issue or have any suggestions on what might be causing this discrepancy?

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
21,348 questions
{count} votes

1 answer

Sort by: Most helpful
  1. James Hamil 24,296 Reputation points Microsoft Employee
    2023-08-24T23:26:17.8666667+00:00

    Hi @Sangbuem Choo , can you please check the following for me?

    1. Make sure that the redirect URI in your application code matches the one configured in the Azure portal. Even a small difference, such as a trailing slash or a different subdomain, can cause a redirect URI mismatch error.
    2. Check if there are any typos or errors in the client ID or tenant name. Double-check that you are using the correct values for these parameters.
    3. Verify that you are using the correct policy name in your authentication request. If you are using custom policies, make sure that the policy name in your request matches the one configured in the Azure portal.
    4. Check if there are any network issues that could be causing the error. For example, if you are using a custom domain, make sure that the DNS records are correctly configured and propagated.

    Please let me know if any of these help. If not I can help you further.

    Thank you,

    James

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.