This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 32%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Hello! We are unable to set the networking/ IP Access settings to our DEV slot because it says that we are 'Testing in Production' and must do it on the Prod slot, which helps us not one bit, the prod access does not work on the dev slot. We have a dev who cannot access the dev slot because of this.
How does one disable TIP for a slot when it is already at 0%?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
@Mark Perry , Firstly , apologies for the delay in responding here. [1/2]
To better assist you on this and just to clarify, are you mentioning that your dev engineer doesn’t have staging slot/URL access (however, has access to prod URL)? What level of resource/subscription permissions do they have? OR you’re referring, for the dev engineer (when access as a user), the traffic is not routed to staging URL)?
On staging slot/URL, you are routing to staging URL (the URL you asked for) – and “Testing in Production” doesn’t change in staging, it only changes production.
Kindly see this demo -Testing in production with Azure App Service (8:20 – 8:40)
If you’re looking at access restrictions, to have an Identity assigned to each environment.
Deployment slot has a different URL than your production slot, although users don’t notice that when they are routed through the Testing in Production feature.
It is important to note that once a client is automatically routed to a specific slot, it will be "pinned" to that slot for the life of that client session. This done using a cookie to pin the user session. If you inspect the HTTP requests, you will find a TipMix cookie in every subsequent request.
@Mark Perry , Addiing more info: [2/2]
When you want your users to be able to opt-into or opt-out of your beta app. You may use the x-ms-routing-name query parameter.
To reroute users to a specific slot using x-ms-routing-name, you must make sure that the slot is already added to the Traffic Routing list. Since you want to route to a slot explicitly, the actual routing percentage you set doesn't matter.
Typically, with no access restrictions applied, user would be able to access both sites when automatic routing kicks-in.
Also, note some settings can be made stick to the slot. Kindly see settings that are swapped/unswapped.
See this blog for more info: Traffic Percentage for Web Apps with Azure App Service
If the issue still persists, kindly let us know with additional information (share any screenshot after concealing any PII data), I'll be more than happy to assist you further.
Thanks for you patience!
I'm only talking about the Network portion of the properties for the dev slot specifically. We want to add an IP, but when we try to change a previous record or add a new one, it says that we can't because we are 'testing in production', but we have no idea how it got into that state or how to remove it from that state such that we can manage the IPs that have access to that specific dev slot that exists at its own URL. Basically, we can no longer manage the firewall for the 'dev' slot directly.
How do you even manage the 'testing in production' feature?
We are not having problems with routing. We are having problems editing 'networking' for the dev slot, like we used to be able to do without issue.
The traffic is and has been set at 0 for dev, it's always had it's own URL, we have never routed anything except production as 100%, so how is it 'testing in production' and how do I make it not be 'testing in production'? Sorry, just want to be super clear.
We have also already set the needed IP as open in production, which is what the Dev networking told us to do, and it made no difference for dev. So, we can't edit for dev, and editing for production doesn't give the access we need...we have a dev locked out of their own app.
MarkPerry-2079, Thanks for the follow-up and sharing additional info.
As for as managing the feature - By default, all your traffic is routed to the production slot (100%). By setting the traffic percentage to 10% on the staging slot. Then click Save. With that simple change, a tenth of your production traffic will now go to the new build.
You add a % of the traffic to route to other slots thus distributing the traffic. The feature allows you to route production traffic to one of those deployment slots.
To investigate this further, I would need your WebApp and subscription details (PII data), for this I'll reach out you privately.
PS: Please do not share any PII data on the public forum.
To benefit the community, updating the offline discussion/ticket.
Without much changes, the settings started working as expected. In case, the issue reoccurs, we will follow-up offline for RCA (with more supporting logs).
MarkPerry-2079, Thanks for your patience and co-operation.