update

Author: mumian

articles/azure-resource-manager/templates/create-multiple-instances.md

@@ -65,11 +65,11 @@ The resource to create several times takes the following format:
         "name": "Standard_LRS"
       },
       "kind": "Storage",
-      "properties": {},
       "copy": {
         "name": "storagecopy",
         "count": 3
-      }
+      },
+      "properties": {}
     }
   ],
   "outputs": {}
@@ -151,13 +151,13 @@ For example, to serially deploy storage accounts two at a time, use:
         "name": "Standard_LRS"
       },
       "kind": "Storage",
-      "properties": {},
       "copy": {
         "name": "storagecopy",
         "count": 4,
         "mode": "serial",
         "batchSize": 2
-      }
+      },
+      "properties": {}
     }
   ],
   "outputs": {}
@@ -433,11 +433,11 @@ You specify that a resource is deployed after another resource by using the `dep
         "name": "Standard_LRS"
       },
       "kind": "Storage",
-      "properties": {},
       "copy": {
         "name": "storagecopy",
         "count": 3
-      }
+      },
+      "properties": {}
     },
     {
       "type": "Microsoft.Compute/virtualMachines",

articles/azure-resource-manager/templates/define-resource-dependency.md

@@ -118,11 +118,11 @@ In the following example, a CDN endpoint explicitly depends on the CDN profile,
     "type": "endpoints",
     "location": "[resourceGroup().location]",
     "dependsOn": [
-            "[variables('profileName')]"
+      "[variables('profileName')]"
     ],
     "properties": {
-        "originHostHeader": "[reference(variables('webAppName')).hostNames[0]]",
-        ...
+      "originHostHeader": "[reference(variables('webAppName')).hostNames[0]]",
+      ...
     }
 ```
 

articles/azure-resource-manager/templates/linked-templates.md

@@ -28,8 +28,8 @@ To nest a template, add a [deployments resource](/azure/templates/microsoft.reso
   "variables": {},
   "resources": [
     {
-      "apiVersion": "2017-05-10",
       "name": "nestedTemplate1",
+      "apiVersion": "2017-05-10",
       "type": "Microsoft.Resources/deployments",
       "properties": {
         "mode": "Incremental",
@@ -71,10 +71,10 @@ The following example deploys a storage account through a nested template.
               "apiVersion": "2019-04-01",
               "name": "[parameters('storageAccountName')]",
               "location": "West US",
-              "kind": "StorageV2",
               "sku": {
                 "name": "Standard_LRS"
-              }
+              },
+              "kind": "StorageV2"
             }
           ]
         }
@@ -386,10 +386,10 @@ The following example template shows how to use copy with a nested template.
       "apiVersion": "2019-04-01",
       "name": "[concat(variables('storageName'), copyIndex())]",
       "location": "West US",
-      "kind": "StorageV2",
       "sku": {
         "name": "Standard_LRS"
-      }
+      },
+      "kind": "StorageV2"
       // Copy works here when scope is inner
       // But, when scope is default or outer, you get an error
       //"copy":{

articles/azure-resource-manager/templates/template-syntax.md

@@ -185,12 +185,6 @@ You define resources with the following structure:
       "name": "<name-of-the-resource>",
       "comments": "<your-reference-notes>",
       "location": "<location-of-resource>",
-      "copy": {
-          "name": "<name-of-copy-loop>",
-          "count": <number-of-iterations>,
-          "mode": "<serial-or-parallel>",
-          "batchSize": <number-to-deploy-serially>
-      },
       "dependsOn": [
           "<array-of-related-resource-names>"
       ],
@@ -206,6 +200,12 @@ You define resources with the following structure:
           "capacity": <sku-capacity>
       },
       "kind": "<type-of-resource>",
+      "copy": {
+          "name": "<name-of-copy-loop>",
+          "count": <number-of-iterations>,
+          "mode": "<serial-or-parallel>",
+          "batchSize": <number-to-deploy-serially>
+      },
       "plan": {
           "name": "<plan-name>",
           "promotionCode": "<plan-promotion-code>",
@@ -240,9 +240,9 @@ You define resources with the following structure:
 | location |Varies |Supported geo-locations of the provided resource. You can select any of the available locations, but typically it makes sense to pick one that is close to your users. Usually, it also makes sense to place resources that interact with each other in the same region. Most resource types require a location, but some types (such as a role assignment) don't require a location. See [Set resource location](resource-location.md). |
 | dependsOn |No |Resources that must be deployed before this resource is deployed. Resource Manager evaluates the dependencies between resources and deploys them in the correct order. When resources aren't dependent on each other, they're deployed in parallel. The value can be a comma-separated list of a resource names or resource unique identifiers. Only list resources that are deployed in this template. Resources that aren't defined in this template must already exist. Avoid adding unnecessary dependencies as they can slow your deployment and create circular dependencies. For guidance on setting dependencies, see [Defining dependencies in Azure Resource Manager templates](define-resource-dependency.md). |
 | tags |No |Tags that are associated with the resource. Apply tags to logically organize resources across your subscription. |
-| copy |No |If more than one instance is needed, the number of resources to create. The default mode is parallel. Specify serial mode when you don't want all or the resources to deploy at the same time. For more information, see [Create several instances of resources in Azure Resource Manager](create-multiple-instances.md). |
 | sku | No | Some resources allow values that define the SKU to deploy. For example, you can specify the type of redundancy for a storage account. |
 | kind | No | Some resources allow a value that defines the type of resource you deploy. For example, you can specify the type of Cosmos DB to create. |
+| copy |No |If more than one instance is needed, the number of resources to create. The default mode is parallel. Specify serial mode when you don't want all or the resources to deploy at the same time. For more information, see [Create several instances of resources in Azure Resource Manager](create-multiple-instances.md). |
 | plan | No | Some resources allow values that define the plan to deploy. For example, you can specify the marketplace image for a virtual machine. |
 | properties |No |Resource-specific configuration settings. The values for the properties are the same as the values you provide in the request body for the REST API operation (PUT method) to create the resource. You can also specify a copy array to create several instances of a property. To determine available values, see [template reference](/azure/templates/). |
 | resources |No |Child resources that depend on the resource being defined. Only provide resource types that are permitted by the schema of the parent resource. Dependency on the parent resource isn't implied. You must explicitly define that dependency. See [Set name and type for child resources](child-resource-name-type.md). |