Is deployment slot automatic traffic routing sticky across sessions?

Question

We were recently disappointed to learn that we cannot use Azure Deployment Slots manual traffic routing because we use custom domains with our Azure hosted app services. So we are having to re-evaluate our soft launch plans and are wondering how we might make use of automated traffic routing between slots by percentages. Is that automatic routing, which would send say 10% of traffic to our new version of the site, sticky across sessions so that a user who experiences the new version in one session will continue to see the new version going forward?

Answer 1

Hi - Thanks for the question
The answer is yes REF https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots?tabs=portal#route-production-traffic-automatically

Quoting "After a client is automatically routed to a specific slot, it's "pinned" to that slot for one hour or until the cookies are deleted. On the client browser, you can see which slot your session is pinned to by looking at the x-ms-routing-name cookie in your HTTP headers. A request that's routed to the "staging" slot has the cookie x-ms-routing-name=staging. A request that's routed to the production slot has the cookie x-ms-routing-name=self."