redirect uri error prevents login to outlook on the web

Question

redirect uri error prevents login to outlook on the web

Vashi Ratnam 40

We receive the following error when we attempt to login to outlook via windows using the edge browser." Sorry, but we’re having trouble signing you in.

AADSTS50011: The redirect URI 'https://www.outlook.com/mail/' specified in the request does not match the redirect URIs configured for the application '9199bf20-a13f-4107-85dc-02114787ef48'. 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. "

We have attempted to locate the application as per the support article provided using an administrative account and also another account. The error on accessing the application location suggests that the application either does not exist or the user accounts we are using does not have access permissions. We have also reviewed the applications in the tenant and do not find the application listed in tenant. The tenant accounts however, appear to be able to sign in to entra portal, azure and microsoft 365 admin portals.

When we used Google chrome, in the first instance we were able to login but subsequent attempts we are receiving the same redirect uri error. Appreciate if someone can assist to troubleshoot the issues. One being the access to the application. Two being access to emails.

Kit Erceg 20 Reputation points

2025-11-11T21:48:43.4366667+00:00

Hi Vashi! I'm having the same issue in my Microsoft tenant and we've found that we were able to work around the issue by getting into the M365 user portal and navigating via the app waffle. Two people impacted so far so I went searching and found your question!

Fingers crossed Microsoft patch whatever they've broken haha!
Vashi Ratnam 40 Reputation points

2025-11-12T04:00:15.1166667+00:00

This is assuming a user has access to the 365 portal. I have checked and it does work- accessing outlook via the 365 portal. thanks for sharing.

Answer accepted by question author

0 additional answers

Your answer

Kit Erceg 20 Reputation points

2025-11-11T21:48:43.4366667+00:00

Hi Vashi! I'm having the same issue in my Microsoft tenant and we've found that we were able to work around the issue by getting into the M365 user portal and navigating via the app waffle. Two people impacted so far so I went searching and found your question!

Fingers crossed Microsoft patch whatever they've broken haha!
Vashi Ratnam 40 Reputation points

2025-11-12T04:00:15.1166667+00:00

This is assuming a user has access to the 365 portal. I have checked and it does work- accessing outlook via the 365 portal. thanks for sharing.

Answer 1

Dear @Vashi Ratnam,

Thank you for reaching out to Microsoft Q&A forum.
I understand you are receiving a critical AADSTS50011: The redirect URI specified in the request does not match error message when trying to log in to Outlook on the Web via the Edge browser, and this issue is now starting to appear in Chrome as well. The issue is often related to a local client problem (browser cache/cookies) or a tenant-specific setting that is incorrectly routing the sign-in. I will address each issue one by one:

Access to the Application (Issue One)

From my research, you cannot find the application with ID 9199bf20-a13f-4107-85dc-02114787ef48 in your tenant. This is because the application is owned by Microsoft (a core service), and therefore, it will not appear under "Enterprise applications" or "App registrations" that you can manage. You do not have permission to view or edit its settings.

Access to Emails (Issue Two)

This needs to be addressed through client-side clearing and verifying the correct sign-in URL:

1.Clear Browser Cache and Cookies (Essential): Since clearing your browser often forces a clean sign-in flow, this is the most likely solution given the problem appeared on Chrome only after the first successful login.

In both Edge and Chrome, completely clear all browser cache, cookies, and site data related to microsoft.com and outlook.com ( Settings > Profile > Clear browsing data).

2.Verify the Sign-in URL: Ensure users are navigating to the correct, modern Outlook URL and not a legacy or redirected one.

Direct users to sign in directly at: https://outlook.office.com.

3.Check Conditional Access Policies: While rare, a Conditional Access policy in your Entra ID tenant could be interfering with the sign-in token delivery, which sometimes results in bizarre redirect errors.

As an Administrator, check Microsoft Entra ID > Conditional Access. Look for policies targeting "Exchange Online" or "Office 365" that might be applying an unexpected restriction.

If your service is managed by a third party (like GoDaddy or another CSP), their specific domain redirection rules might be causing the conflict.

If the cache clearing fails, you may need to contact your Microsoft 365 Partner (if you have one) and ask them to verify there are no custom redirects or legacy settings applied to your service access point.

If none of the above solutions work, let me know for further investigation. Please note that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution. Thank you for your patience and understanding. I'm looking forward to your reply.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Kai-L 17,480 Reputation points Microsoft External Staff Moderator

2025-11-12T23:15:09.75+00:00

Dear @Vashi Ratnam,
It’s been a while, and I wanted to check in to see how things are going with this issue. Did the workaround suggested by @Kit Erceg resolve your problem?

If there’s anything else I can assist you with or if you need further clarification, please don’t hesitate to let me know, I’m here to help.

Looking forward to hearing from you. Wishing you a great day ahead!
Vashi Ratnam 40 Reputation points

2025-11-13T01:16:56.8633333+00:00

Your answer on Access to the Application (Issue One).

Every act that has to performed in a tenant, whether it be performed by user principle or service principle ought to be performed using a security principle instance which ought to be provisioned in the tenant.

While it is comforting to hear that the application may be owned by microsoft. This fact is not verifiable within the tenant. It is with much effort that we have establish that this is the case.

Access to Emails (Issue Two)

The issue occurred whilst using in private window and incoginito mode access, including after clearing cookies etc.

However, subsequent to the posting of the tickets, when we did use outlook.office.com, we were able to access outlook without the error.

We cannot say whether it was a url issue or the underlying issue got fixed elsewhere.

For the sake of completeness we comment below on the rest of the trouble shooting steps suggested.

Conditional Access Policies.

the policies do not appear to be the issue.

Third party management.

The tenancy is wholly managed by Microsoft and the organization has a direct relationship with Microsoft and that is what is visible on the organization end.

Since the issue appears to be resolved. Shall accept your answer as the best.

Thanks for your support.
Kai-L 17,480 Reputation points Microsoft External Staff Moderator

2025-11-13T16:51:48.7533333+00:00

Dear @Vashi Ratnam,
I’m glad I could provide helpful information to resolve this issue. If you have any further questions or need additional assistance down the road, feel free to post back. Not only I, but other professionals in the forum are always here to help. Thank you very much and I wish you all the best!