We are implementing URL hardening in Azure PaaS. We have added Azure front door urls to CM app. We have updated


on CM server with new url for identity server and


on identity server with the new urls for Sitecore CM. But still the identity server redirects back to the old CM server url only and not to the Azure front door url for CM. Any inputs on what are we missing here?

  • Are you trying to implement Azure AD login integration ?
    – D J
    Commented Mar 3, 2020 at 12:01
  • No, we are not implementing Azure AD login integration.We are simply trying to redirect from Identity server to Azure front door url instead of CM url after login.
    – Ghan
    Commented Mar 4, 2020 at 3:53

1 Answer 1


We figured out the problem. AFD url simply forwards request to the Sitecore CM webapp url. This means identity server receives request from Sitecore CM URL and not AFD url (even though we see AFD url in browser). So after user gets logged in, identity server redirects user back to Sitecore CM url only and not to AFD url. To fix this, we have added custom domain to Sitecore CM webapp instead of AFD url.

  • Hi, can you expand on your solution a little? As I read it, you ended up not using AFD? Or have you used the same custom domain name for both the AFD frontend URL and the app service? I can't see how that would work. Commented Apr 2, 2020 at 8:37
  • Ah just found this answer which sounds similar: sitecore.stackexchange.com/questions/24177/… I think the missing part of the puzzle for me was overriding the host header in the AFD backend. Commented Apr 2, 2020 at 8:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.