AADSTS50011 on GCC High tenants

Question

Hello,

We are facing an issue with an application where the OAuth flow is successfully carried out for O365 commercial users, however, when we try to log in using a GCC High account, we get the following error:

AADSTS50011: The redirect URI 'https://xxxx.xxxx.com/auth/microsoft_graph_auth/callback' specified in the request does not match the redirect URIs configured for the application 'd9f8cc5a-xxxx-xxxx-xxxx-xxxxxxxxxxx'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this.

Please note that the redirection URL is already added to the application in the Azure portal so we believe that the error is most probably misleading.

Could you please take a deeper look and help us debug the issue?

Request Id: e80826bc-afbf-4108-9db1-13e3c0636000

Correlation Id: 7b19af2b-586a-42d4-8573-0a4588248066

Timestamp: 2024-02-28T23:11:15Z

Answer 1

Hi @Mohamed Hamed ,

I don't have the tools to look up your correlation ID without a support plan open, but if you go to the portal and search App Registrations > Search the app with App ID d9f8cc5a-xxxx-xxxx-xxxx-xxxxxxxxxxx, you can confirm whether the Redirect URI listed is https://xxxx.xxxx.com/auth/microsoft_graph_auth/callback

For GCC High tenants, it's possible that there could also be an issue with the SSO context, for example if prompt=none in the Oauth request for the sign-in. If that is the case you may try adding prompt=login to the Oauth request for interactive sign-in.

The format of the URL in your app settings needs to be exactly the same as the one in your app registration, and there cannot be an extra space or slash. You also need to make sure that the tenant ID is the same in both places.

If you still face this error after checking these settings you can send me an email at AzCommunity@microsoft.com ("Attn: Marilee Turscak") and include your subscription ID and a link to this thread, and I will open a one-time free support case to look into your issue.

If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar errors.