Merge pull request #96781 from MicrosoftDocs/master

11/21 AM Publish

Author: huypub

articles/app-service/deploy-staging-slots.md

@@ -15,6 +15,7 @@ ms.tgt_pltfrm: na
 ms.topic: article
 ms.date: 09/19/2019
 ms.author: cephalin
+ms.custom: fasttrack-edit
 
 ---
 # Set up staging environments in Azure App Service
@@ -245,6 +246,10 @@ After the setting is saved, the specified percentage of clients is randomly rout
 
 After a client is automatically routed to a specific slot, it's "pinned" to that slot for the life of that client session. 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`.
 
+   > [!NOTE]
+   > Next to the Azure Portal, you can also use the [`az webapp traffic-routing set`](/cli/azure/webapp/traffic-routing.md#az-webapp-traffic-routing-set) command in the Azure CLI to set the routing percentages from CI/CD tools like DevOps pipelines or other automation systems.
+   > 
+
 ### Route production traffic manually
 
 In addition to automatic traffic routing, App Service can route requests to a specific slot. This is useful when you want your users to be able to opt in to or opt out of your beta app. To route production traffic manually, you use the `x-ms-routing-name` query parameter.