Azure-docs: Route Production traffic manually -- Azure Web app slots

[mariotzki]

Tried the x-ms-routing-name specified in the doc. It doesn't work. Is manual routing thru slots still active?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f6e09089-1ae2-8943-5ce2-9d48f458c81f
• Version Independent ID: ba780cba-f604-b0a4-a81a-23c7d2384762
• Content: Set up staging environments for web apps in Azure App Service
• Content Source: articles/app-service/deploy-staging-slots.md
• Service: app-service
• GitHub Login: @cephalin
• Microsoft Alias: cephalin

[BryanTrach-MSFT]

@mariotzki Thanks for the feedback. Have you been able to get the feature to work at all or does it work then stop working shortly after? Last I heard, the feature would sometimes stop working and the workaround was to have customers go to the app > testing in production and make a change to active the save button and then save the change.

[BryanTrach-MSFT]

@mariotzki Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.

[tuthan]

I have the same issue. Adding ?x-ms-routing-name=slotname to URL it doesn't work. Go to Deployment Slots change % traffic to 1% on the slot. The manual route works
Switch back to 0% --> it will not work anymore.
Is it the desire behavior?

[staal-it]

Is there any news on this bug? The workaround doesn’t work anymore since Deployment Slots is no longer in preview and TiP has been removed...

[capraynor]

Me too. I have the same issue even for now. 2019

[staal-it]

@BryanTrach-MSFT do you have any update on this issue?

[BryanTrach-MSFT]

@tuthan @staal-it @capraynor There is no known issue with manually routing traffic. If you are still having issues, please reach out to [email protected] with your subscription ID and the URL of this forum post so we can understand exactly what is failing.

[staal-it]

I've send an email and will post updates here

[diepnt90]

@staal-it Do you have any update?

[staal-it]

@diepnt90 Yes I do! For me it turned out to be a problem with the Azure CLI I use in my Azure DevOps deployment. You can read more about this bug following this link.

The bug has been fixed but it's not available yet I believe.

A workaround: if you're using az webapp traffic-routing set --distribution -staging=10 then make sure the name of the slot is the full name, not just 'staging'.

[oreporan]

Still can not get this to work
Any updates?

Its always routing to my production.

These are my slots:

I tried putting my URL:

https://....com/?x-ms-routing-name=xxxx-alpha
https://....com/?x-ms-routing-name=alpha

The query param stays in the URL, but the actual URL is production

[oreporan]

For those who run into the same issue.
For me I had to turn on the branch to 1% once for this to work. You can put it back to 0% after

[jeanpaulsmit]

For all getting here without understanding why the manual routing doesn't work, please read this carefully: https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots#route-production-traffic-manually
The trick is in this part, which mentions you need to set the routing % first to 0 manually (and save!) before it will work:
"By default, new slots are given a routing rule of 0%, shown in grey. When you explicitly set this value to 0% (shown in black text), your users can access the staging slot manually by using the x-ms-routing-name query parameter. But they won't be routed to the slot automatically because the routing percentage is set to 0. "