Sign-in issues for One Web Application Only

Question

Sign-in issues for One Web Application Only

Ben Fraser 0

When I try to access my azure web app with its default URL, I get the error message "We couldn't sign you in. Please try again." Repeated sign in attempts do not resolve the issue. I am able to use the same account and credentials to log into outlook, Teams, etc, as well as my other similar web applications.

I had another person reproduce this on a different machine using a different Microsoft login.

In the Azure app registration, I have two redirect URIs configured: one for the application URL, and one for a localhost number I use when running the application source code. Running the application from source causes no problems. Additionally, I have other web apps configured the same way, and I have no issues with them either.

What might be causing only this application redirect URI to be unable to sign anyone in?

Anonymous

2025-12-18T21:07:08.99+00:00

Hi @Ben Fraser

Thank you for posting on Microsoft Q&A.

A common cause for this behavior is App Service Authentication (Easy Auth) being enabled on this specific web app. When Easy Auth is turned on, it can intercept the authentication flow and conflict with the Azure AD app registration, causing sign-in to fail only for the deployed URL. Please check App Service → Authentication → Identity providers and ensure the settings align with your app registration, or disable Easy Auth if it’s not required.

Another frequent issue is an App ID / environment mismatch. Verify that the deployed application is using the same Client ID and Tenant ID as the app registration where the redirect URI is configured. Local sign-in often works because environment variables are correct locally, while the deployed app may be pointing to a different or outdated app registration.

Hope this helps in resolving the issue further.
Supriya Funde 0 Reputation points

2026-02-26T22:06:11.89+00:00

We are experiencing a similar kind of sign-in issue with one of our Azure web application following its migration from Windows 2016 to Windows 2022 servers. The application previously functioned as expected on Windows 2016. However, after migration we are unable to sign in and receive the error message: "We couldn't sign you in. Please try again." Multiple sign-in attempts, including clearing the browser cache, have not resolved the issue.

Notably, I am able to use the same account and credentials to access other services such as Outlook and Teams without any difficulties. Within the Azure app registration, we have verified the App ID (Client ID), environment, redirect URIs, and related settings. All configurations appear to be consistent, with no mismatches identified. Unfortunately, we do not have any additional Azure web application for comparison at this time.

Could you please assist in identifying potential causes for this issue that prevent users from signing in to the application after the server migration? Any guidance or recommendations would be appreciated.
Supriya Funde 0 Reputation points

2026-03-02T02:31:08.3533333+00:00

Can I get answer to my above asked question. Please help.
Aditya N 3,890 Reputation points Microsoft External Staff Moderator

2026-03-02T06:13:51.6033333+00:00

Hello @Supriya Funde

Request you to please open a new thread as these threads requires troubleshooting which needs deeper details.

Your answer

Anonymous

2025-12-18T21:07:08.99+00:00

Hi @Ben Fraser

Thank you for posting on Microsoft Q&A.

A common cause for this behavior is App Service Authentication (Easy Auth) being enabled on this specific web app. When Easy Auth is turned on, it can intercept the authentication flow and conflict with the Azure AD app registration, causing sign-in to fail only for the deployed URL. Please check App Service → Authentication → Identity providers and ensure the settings align with your app registration, or disable Easy Auth if it’s not required.

Another frequent issue is an App ID / environment mismatch. Verify that the deployed application is using the same Client ID and Tenant ID as the app registration where the redirect URI is configured. Local sign-in often works because environment variables are correct locally, while the deployed app may be pointing to a different or outdated app registration.

Hope this helps in resolving the issue further.
Supriya Funde 0 Reputation points

2026-02-26T22:06:11.89+00:00

We are experiencing a similar kind of sign-in issue with one of our Azure web application following its migration from Windows 2016 to Windows 2022 servers. The application previously functioned as expected on Windows 2016. However, after migration we are unable to sign in and receive the error message: "We couldn't sign you in. Please try again." Multiple sign-in attempts, including clearing the browser cache, have not resolved the issue.

Notably, I am able to use the same account and credentials to access other services such as Outlook and Teams without any difficulties. Within the Azure app registration, we have verified the App ID (Client ID), environment, redirect URIs, and related settings. All configurations appear to be consistent, with no mismatches identified. Unfortunately, we do not have any additional Azure web application for comparison at this time.

Could you please assist in identifying potential causes for this issue that prevent users from signing in to the application after the server migration? Any guidance or recommendations would be appreciated.
Supriya Funde 0 Reputation points

2026-03-02T02:31:08.3533333+00:00

Can I get answer to my above asked question. Please help.
Aditya N 3,890 Reputation points Microsoft External Staff Moderator

2026-03-02T06:13:51.6033333+00:00

Hello @Supriya Funde

Request you to please open a new thread as these threads requires troubleshooting which needs deeper details.