Hi @Zheng, Huili,
Microsoft’s identity platform requires that the reply URL registered in Azure AD match exactly with what’s provided in your application’s configuration, so even a small formatting error can disrupt the login process. In your case, the URL is registered as “https//my-web-app.azurewebsites.net/auth/callback” which is missing the colon after “https”; it should be “https://my-web-app.azurewebsites.net/auth/callback”.
This precise URL must be consistently configured in both your Azure AD app registration and your application’s environment variables, as any discrepancy in protocol, path, or even a trailing slash can cause the platform to reject the redirection. While a 302-status code is a normal part of the authentication flow, it signals that the redirection target isn’t correctly recognized when there’s a formatting error.
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Let me know if you have any further Queries.