0

I've been testing deployment slots for web apps. By attaching x-ms-routing-name to the query parameters you can redirect a call to a deployment slot (although you first need to manually change the traffic % for it to work).

Now I'm setting up deployment slots for Azure Functions to do the same thing. However it seems the x-ms-routing-name is not acknowledged? I also cannot change the traffic % for the deployment slots as they're disabled in the app service plan.

Can anyone confirm that x-ms-routing-name is not implemented/acknowledged for Functions?

Jean-Paul Smit
  • 300
  • 4
  • 17

1 Answers1

1

Can anyone confirm that x-ms-routing-name is not implemented/acknowledged for Functions?

I confirm with Microsoft support engineer and it seems that function deployment slot do not support to route traffic with x-ms-routing-name.

If you still want to achieve this functionality, you could give your feedback to azure function to promote this to be achieved.

Joey Cai
  • 18,968
  • 1
  • 20
  • 30
  • Thanks for this confirmation. I noticed on the Functions Live webcast there will be an overhaul of the Portal experience, making it more like App Service. Does that also mean the way deployment slots are handled will be aligned? – Jean-Paul Smit Feb 25 '20 at 09:06
  • This one has to ask the product group and I do not confirm it. You could give your feedback and wait for good news. – Joey Cai Feb 25 '20 at 11:07