add scopetype

Author: mumian

articles/azure-resource-manager/media/resource-manager-tutorial-use-azure-pipelines/azure-resource-manager-devops-pipelines-status.png

@@ -11,7 +11,7 @@ ms.service: azure-resource-manager
 ms.workload: multiple
 ms.tgt_pltfrm: na
 ms.devlang: na
-ms.date: 06/12/2019
+ms.date: 10/15/2019
 ms.topic: tutorial
 ms.author: jgao
 ---
@@ -180,9 +180,11 @@ To create a pipeline with a step to deploy a template:
 
     ```yaml
     steps:
-    - task: AzureResourceGroupDeployment@2
+    - task: AzureResourceManagerTemplateDeployment@3
       inputs:
-        azureSubscription: '[YourServiceConnectionName]'
+        deploymentScope: 'Resource Group'
+        ConnectedServiceName: '[EnterYourServiceConnectionName]'
+        subscriptionName: '[EnterTheTargetSubscriptionID]'
         action: 'Create Or Update Resource Group'
         resourceGroupName: '[EnterANewResourceGroupName]'
         location: 'Central US'
@@ -197,14 +199,16 @@ To create a pipeline with a step to deploy a template:
 
     Make the following changes:
 
-    * **azureSubscription**: update the value with the service connection created in the previous procedure.
+    * **deloymentScope**: Select the scope of deployment from the options: `Management Group`, `Subscription` and `Resource Group`. Use **Resource Group** in this tutorial. To learn more about the scopes, see [Deployment scopes](./resource-group-template-deploy-rest.md#deployment-scope).
+    * **ConnectedServiceName**: Specify the service connection name that you created earlier.
+    * **SubscriptionName**:  Specify the target subscription ID.
     * **action**: the **Create Or Update Resource Group** action does 2 actions - 1. create a resource group if a new resource group name is provided; 2. deploy the template specified.
     * **resourceGroupName**: specify a new resource group name. For example, **AzureRmPipeline-rg**.
     * **location**: specify the location for the resource group.
     * **templateLocation**: when **Linked artifact** is specified, the task looks for the template file directly from the connected repository.
     * **csmFile** is the path to the template file. You don't need to specify a template parameters file because all of the parameters defined in the template have default values.
 
-    For more information about the task, see [Azure Resource Group Deployment task](/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment)
+    For more information about the task, see [Azure Resource Group Deployment task](/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment), and [Azure Resource Manager template deployment task](https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureResourceManagerTemplateDeploymentV3/README.md)
 1. Select **Save and run**.
 1. Select **Save and run** again. A copy of the YAML file is saved into the connected repository. You can see the YAML file by browse to your repository.
 1. Verify that the pipeline is executed successfully.

articles/azure-resource-manager/media/resource-manager-tutorial-use-azure-pipelines/azure-resource-manager-devops-pipelines-yml.png

@@ -170,6 +170,7 @@
     items:
     - name: VS project with pipelines
       href: vs-resource-groups-project-devops-pipelines.md
+      displayName: DevOps
   - name: Export template
     href: export-template-portal.md
   - name: Move