Testing in production with custom domains and Azure Front Door

German Diaz de Rada 116 Reputation points
2021-06-01T10:05:00.73+00:00

Hi there,

We're having issues with testing in production using traffic routing and a stage slot. The main problem is that the cookies x-ms-routing-name, ARRAffinity, ARRAffinitySameSite and TiPMix don't get set due to being blocked because the cookie domain doesn't match the current host (custom domain set in Front Door).

The question is, how can we configure those cookies to use the domain as opposed to the app service/slot domain?

Thanks

Azure Front Door
Azure Front Door

An Azure service that provides a cloud content delivery network with threat protection.

Azure Traffic Manager
Azure Traffic Manager

An Azure service that is used to route incoming network traffic for high performance and availability.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jacobs, Brian 0 Reputation points
    2025-08-01T20:38:32.52+00:00

    So in our case we are running into this issue, but we can't use the custom Domain because we are using Azure Front Door to route between multiple App Services on the same domain.

    Ideally

    Front Door WAF
    Front Door
    App Service 1 App Service 2 App Service 3
    Beta Beta Beta
    Canary Canary Canary

    This should be an acceptable use case behind the Front Door.

    There is a setting for the Session Affinity Cookies to inherit from the host, and Cookies set manually by the Apps inherit the Front door host. It follows that this should be a valid configuration.

    Was this answer helpful?

    0 comments
  2. Chris Procter 16 Reputation points
    2022-04-05T00:25:11.643+00:00

    We had a similar problem that was fixed by adjusting the Origin host header on the Front Door origin group to be the custom domain rather than the app service domain. Likely the backend App Service would have to have the same Custom Domain bound (as @RaviVarmanMSFT mentions)

    Was this answer helpful?

    0 comments
  3. RaviVarmanMSFT 626 Reputation points Microsoft Employee Moderator
    2021-06-07T04:42:35.62+00:00

    Hi @German Diaz de Rada

    When backend app services do not have the same custom domain as AFD (Azure Font door), App service session cookies are not passed back to the browser. Therefore session affinity is broken.

    There is a workaround that involves pointing the custom domain used in AFD to the app services and register the domain.

    • Open app service--> Under Settings --> Custom Domain
    • Add Custom Domain --> Enter the custom domain name
    • Get the TXT value and create TXT record in your Domain Ex: www.contoso.com Host (asuid.www) Value (Custom Domain Verification ID)
    • Once the record is created click on validate to complete the Domain ownership verification.

    Ref: https://learn.microsoft.com/en-gb/azure/app-service/app-service-web-tutorial-custom-domain?tabs=cname

    Hope this was helpful. Please let us know in case of any additional questions or concerns.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.