How to fix the reply URL mismatch error in Entra ID - Microsoft Identity Platform

Jeevan Manoj explains how to fix “AADSTS50011 The reply URL specified in the request does not match the reply URLs configured for the application” error.

► Follow us on social:

#AzureAD #MicrosoftSecurity

[Bloedwraakje]

So in the netherlands we don't call it IT we call it "ICT" which stands for "Information, Communication, Technology"...
But mostly the "C" is forgotten by professionals, good to see a manager that doesn't and knows how its done ...

Great video, awesome explanaition... Shot and to the point and easy to understand....
Easy to watch, can you make more ??? ;)

[XDWolf]

For the record and for everyone who still can't login, I was struggling until I realized the reply URL is case sensitive.

[PaulShadwell]

This is an excellent explanation. I have often had to deal with this but never sure where to fix it.

[dominikrein]

I've had no reply URL in these URLs during the login, but I was able to solve it:

Download the Secure-Sign-In-Extension (Chrome, Firefox didn't work) and use the "Sign in as someone else" in the "Test this application" on the Single sign-on page in Azure Enterprise Application. After you entered the credential you get back and can download the SAML request as xml which contains all information like reply URL.

[FredFernandes]

This is a great explanation. However, I am getting this error and verified that the Redirect URI is the same in both places. Where to go from that?

[EduardoOliveira-ysfb]

Thank you. that was very useful and saved a few hours of learning curve.

[kaling]

Very helpfull. You saved few hours of my working time, which I will invest in cat videos now! :)

[NM-trii]

This is a short but excellent explanation of the problem and the solution. Outstanding!

[zimmy]

So clear and to the point..THANK YOU SO MUCH. App developers always getting in the way with their lack of communication.

[oshadhalakruwan]

After long time but this video helps me a lot. Thank You

[TheCameltotem]

Wow look it solved the issue. Can't believe it almost. Thanks.

[tuyenpham]

Hello guys, How to configuration URL for .Net Application?

[rubenslima]

Thank you Jeevan, it was very very usefull on the product I'm developing.

[amust]

Wish it was always that simple ... I've recently dealt with having just changed the clientid in the config which broke authentication no matter what I put in the redirect url for the app with the matching clientid. Reverted my changes and the app stopped working with the original clientid and associated application as well. Following the exact steps in this video did not resolve the error either. The only fix was to start from scratch with a new project and copy all the files into the new project.

Still seems like there's some undocumented features in this process... especially since the new project is automatically adding the redirect URL to the application registration every time the port changes in development, and the url never includes the "/signin-oidc".

[niteeshpulletikurthi]

I am having a doubt, when should we prefer creating application from enterprise applications and creating from app registration

[sdbyrd]

Yes, but what if the URL passed IS in the list of registered redirect_uris and this still happens? This is the context of an Office Addin.

[gasy]

Thank you Jeevan Manoj, it's very helpful for me

[mattwynn]

Thank you Jeevan. That was really useful!

[JoshuaCBrown]

This didn't work trying to log into my app registration through Windows Admin center. I could not get a proper redirect URI or it was the same as the one I was attempting to connect. I did fix it by going to + Add a platform -> choosing Mobile and desktop applications -> then selecting all three login redirect weblinks.

[spicy]

didn't fix anything what the fuck is going on....