This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 51%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
I've an Azure Web App, with the following Single Page Application Redirect URIs:
https://dummy-portal.myorg.net/my-app
https://dummy-portal.myorg.net
https://dummy-portal.ppd.myorg.net/my-app
https://dummy-portal.ppd.myorg.net
https://dummy-portal.azure.myorg.net/my-app
https://ppd-dummy-portal.azure.myorg.net/my-app
http://localhost:8080/myApp
Once the user hits my web url, they are redirected to the MS Sign In page.
However for my preproduction deployment ppd; the user is being redirected to localhost:8080/my-app instead of the actual ppd url.
I've verified my Angular MSAL, and it's not with the code but Azure only. Please help me on the.
As of now my prod is working fine, and I'm really worried that it might get broke as well, as the preprod was also working fine for >2 years, and suddenly started this issue.
Hi.
Ensure that the redirect URIs configured in Azure Entra ID for your application match the correct ones, particularly for the preproduction (ppd) environment. Verify that your Angular application's MSAL configuration aligns with the proper URIs for each environment, avoiding redirection to localhost:8080 unless it’s during local development.
Hi friend, how did it go? Did you manage to do it?
Hi Sergio, apologies for the delay, I was stuck with something else. The issue is still there, and it has now expanded to another web application configured in Azure for the PPD environment. It's quite an odd one.
I've checked the redirect_url parameter being passed to the Azure sign-in page, and it correctly points to the PPD URL. However, the tokens are being returned to localhost. Maybe it's not an issue with the SPA RedirectURI list, but I’ll need to conduct further analysis.
I'll keep you updated as I do further analysis. Meanwhile, if you have any ideas on what other factors might be contributing to this, please let me know. Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
when your app redirects to azure to login, it passes the redirect url. azure just validates the url is on the reply list, else it gives an error. so the issue is with your app.
Entra ID doesn’t decide where to send users back; it just validates the URL your app includes in the login request. If you’re seeing it redirect to http://localhost:8080/..., that means your Angular/MSAL app is still passing that as the redirect_uri, and Entra ID allows it because it’s registered on the reply to URL list.
The best step is to check the redirectUri setting in your preprod environment files or your deployment pipeline. To confirm quickly, open the browser’s network tab, capture the login request, and see what redirect_uri is being sent. If it shows localhost, then the app is still pulling that value from its config.
