[Microsoft] Error AADSTS50011 - Incorrect redirect URI

Amy Ma
Amy Ma
  • Updated

Problem Symptoms

You or one of your users receive the following error message when you try to sign in:

Error AADSTS50011 - The redirect URI <Redirect URI> specified in the request does not match the redirect URIs configured for the application <GUID>. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate tohttps://aka.ms/redirectUriMismatchErrorto learn more about how to fix this.

 

Description

This error occurs if theredirect URIthat the Nylas application sent doesn't match any of the redirect URIs that are registered on the Azure application.

 

Resolution

  1. Copy the <GUID> value from the error message. This is your application (client) ID.

  2. Go to theAuthenticationblade of your application in the Azure portal. You can open the page directly by inserting your application ID as the GUID value in one of the following links:

    1. If this app is owned by an organization (Azure AD tenant), usehttps://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationMenuBlade/Authentication/appId/<GUID>. Make sure that you sign in to the portal by using an administrator account for that organization, or an account that owns the application.
    2. If this app is owned by your personal Microsoft (MSA) account, usehttps://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationMenuBlade/Authentication/appId/<GUID>/isMSAApp/true. Make sure that you sign in to the portal by using your personal Microsoft account.
  3. Copy the <redirect URI> value from the error message.

  4. Add the redirect URI to the appropriate platform configuration. This might be the web, single page app, or some public/native client platform. Make sure to save the input after the redirect URI is added.

  5. Wait a few minutes, and then send the log-in request again. You should now be able to sign in to the application.

 

Resources

Error AADSTS50011: The redirect URI specified in the request does not match

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.