Share via

2nd account not loading

Anonymous
2023-08-03T23:37:19+00:00

Request Id: 8a1aec79-2cda-4b4f-b588-62372e872b00 Correlation Id: 92915a63-5da9-8845-fc41-505fcfbc0697 Timestamp: 2023-08-03T23:16:32Z Message: AADSTS50011: The redirect URI 'https://outlook.office.com/owa/' specified in the request does not match the redirect URIs configured for the application '00000002-0000-0ff1-ce00-000000000000'. 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.

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2023-08-11T02:58:54+00:00

    Dear MetalCanary,

    Hope you are doing great.

    Sorry to disturb. As we did not get response, may I know if above reply could clarify your issue, or could you please help to confirm if anything else we may help you with?

    Moreover, kindly update reply url in the application by navigating to Azure Portal > Azure Active Directory > App Registrations > All apps > Search with client ID (aka app ID) > Under Authentication blade of the application > update the reply url with a slash at the end.

    Thanks so much for your time and patience.

    Sincerely,

    De Paul | Microsoft Community Moderator

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-08-04T02:22:39+00:00

    Dear MetalCanary,

    Good day! Thank you for posting to Microsoft Community. We are happy to help you.

    Based on your description, I understand that you have a query "2nd account not loading"

    Could you please explain clearly on this issue, what were you trying to accomplish when getting this error? Basically, the AADSTS50011 error message is returned when you try to sign into an application that uses OpenID Connect (OIDC)-based authentication with Azure Active Directory (Azure AD), and it occurs if the redirect URI (reply URL) configured in the application (code) and the Azure AD app registration don't match.

    The resolution for this is provided in this Microsoft official article: Error AADSTS50011 the redirect URI does not match the redirect URIs configured for the application - Active Directory | Microsoft Learn as follows:

    1. Copy the application ID from the error message. This is the ID of your application that has been registered in Azure AD.
    2. Go to the Azure portal. Make sure you sign into the portal by using an account that has permissions to update Azure AD Application registration.
    3. Navigate to Azure Active Directory, select App registrations, locate the application registration by using the application ID, and then open the app registration page. You can also open the page directly by using the following links: If this app is owned by an organization (Azure AD tenant), use https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationMenuBlade/Authentication/appId/. If this app is owned by your personal Microsoft (MSA) account, use https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationMenuBlade/Authentication/appId//isMSAApp/true.
    4. On the app registration page, select Authentication. In the Platform configurations section, select Add URI to add the redirect URI displayed in the error message to Azure AD.
    5. Save the changes and wait three to five minutes for the changes to take effect, and then send the login request again. You should now be able to sign into the application. If you don't see the Azure AD login page, try clearing the password cache from your browser or use InPrivate browsing.

    We look forward to hearing from you; Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. Thank you for your cooperation.

    Sincerely,

    De Paul | Microsoft Community Moderator

    Was this answer helpful?

    0 comments No comments