Merge pull request #113269 from tfitzmac/0429copy

PRMerger8 · web-flow · commit 543525588297 · 2020-04-29T14:09:27.000-07:00
update copy limits
diff --git a/articles/azure-resource-manager/templates/copy-outputs.md b/articles/azure-resource-manager/templates/copy-outputs.md
@@ -10,7 +10,7 @@ This article shows you how to create more than one value for an output in your A
 
 You can also use copy with [resources](copy-resources.md), [properties in a resource](copy-properties.md), and [variables](copy-variables.md).
 
-## Outputs iteration
+## Syntax
 
 The copy element has the following general format:
 
@@ -25,6 +25,21 @@ The **count** property specifies the number of iterations you want for the outpu
 
 The **input** property specifies the properties that you want to repeat. You create an array of elements constructed from the value in the **input** property. It can be a single property (like a string), or an object with several properties.
 
+## Copy limits
+
+The count can't exceed 800.
+
+The count can't be a negative number. It can be zero if you deploy the template with a recent version of Azure CLI, PowerShell, or REST API. Specifically, you must use:
+
+* Azure PowerShell **2.6** or later
+* Azure CLI **2.0.74** or later
+* REST API version **2019-05-10** or later
+* [Linked deployments](linked-templates.md) must use API version **2019-05-10** or later for the deployment resource type
+
+Earlier versions of PowerShell, CLI, and the REST API don't support zero for count.
+
+## Outputs iteration
+
 The following example creates a variable number of storage accounts and returns an endpoint for each storage account:
 
 ```json
diff --git a/articles/azure-resource-manager/templates/copy-properties.md b/articles/azure-resource-manager/templates/copy-properties.md
@@ -10,7 +10,7 @@ This article shows you how to create more than one instance of a property in you
 
 You can also use copy with [resources](copy-resources.md), [variables](copy-variables.md), and [outputs](copy-outputs.md).
 
-## Property iteration
+## Syntax
 
 The copy element has the following general format:
 
@@ -30,6 +30,21 @@ The **count** property specifies the number of iterations you want for the prope
 
 The **input** property specifies the properties that you want to repeat. You create an array of elements constructed from the value in the **input** property.
 
+## Copy limits
+
+The count can't exceed 800.
+
+The count can't be a negative number. It can be zero if you deploy the template with a recent version of Azure CLI, PowerShell, or REST API. Specifically, you must use:
+
+* Azure PowerShell **2.6** or later
+* Azure CLI **2.0.74** or later
+* REST API version **2019-05-10** or later
+* [Linked deployments](linked-templates.md) must use API version **2019-05-10** or later for the deployment resource type
+
+Earlier versions of PowerShell, CLI, and the REST API don't support zero for count.
+
+## Property iteration
+
 The following example shows how to apply `copy` to the dataDisks property on a virtual machine:
 
 ```json
@@ -227,12 +242,6 @@ You can use resource and property iteration together. Reference the property ite
 }
 ```
 
-## Copy limits
-
-The count can't exceed 800.
-
-The count can't be a negative number. If you deploy a template with Azure PowerShell 2.6 or later, Azure CLI 2.0.74 or later, or REST API version **2019-05-10** or later, you can set count to zero. Earlier versions of PowerShell, CLI, and the REST API don't support zero for count.
-
 ## Example templates
 
 The following example shows a common scenario for creating more than one value for a property.
diff --git a/articles/azure-resource-manager/templates/copy-resources.md b/articles/azure-resource-manager/templates/copy-resources.md
@@ -2,7 +2,7 @@
 title: Deploy multiple instances of resources
 description: Use copy operation and arrays in an Azure Resource Manager template to deploy resource type many times.
 ms.topic: conceptual
-ms.date: 09/27/2019
+ms.date: 04/29/2020
 ---
 # Resource iteration in ARM templates
 
@@ -12,7 +12,7 @@ You can also use copy with [properties](copy-properties.md), [variables](copy-va
 
 If you need to specify whether a resource is deployed at all, see [condition element](conditional-resource-deployment.md).
 
-## Resource iteration
+## Syntax
 
 The copy element has the following general format:
 
@@ -29,6 +29,23 @@ The **name** property is any value that identifies the loop. The **count** prope
 
 Use the **mode** and **batchSize** properties to specify if the resources are deployed in parallel or in sequence. These properties are described in [Serial or Parallel](#serial-or-parallel).
 
+## Copy limits
+
+The count can't exceed 800.
+
+The count can't be a negative number. It can be zero if you deploy the template with a recent version of Azure CLI, PowerShell, or REST API. Specifically, you must use:
+
+* Azure PowerShell **2.6** or later
+* Azure CLI **2.0.74** or later
+* REST API version **2019-05-10** or later
+* [Linked deployments](linked-templates.md) must use API version **2019-05-10** or later for the deployment resource type
+
+Earlier versions of PowerShell, CLI, and the REST API don't support zero for count.
+
+Be careful using [complete mode deployment](deployment-modes.md) with copy. If you redeploy with complete mode to a resource group, any resources that aren't specified in the template after resolving the copy loop are deleted.
+
+## Resource iteration
+
 The following example creates the number of storage accounts specified in the **storageCount** parameter.
 
 ```json
@@ -252,14 +269,6 @@ The following example shows the implementation:
 }]
 ```
 
-## Copy limits
-
-The count can't exceed 800.
-
-The count can't be a negative number. If you deploy a template with Azure PowerShell 2.6 or later, Azure CLI 2.0.74 or later, or REST API version **2019-05-10** or later, you can set count to zero. Earlier versions of PowerShell, CLI, and the REST API don't support zero for count.
-
-Be careful using [complete mode deployment](deployment-modes.md) with copy. If you redeploy with complete mode to a resource group, any resources that aren't specified in the template after resolving the copy loop are deleted.
-
 ## Example templates
 
 The following examples show common scenarios for creating more than one instance of a resource or property.
diff --git a/articles/azure-resource-manager/templates/copy-variables.md b/articles/azure-resource-manager/templates/copy-variables.md
@@ -10,7 +10,7 @@ This article shows you how to create more than one value for a variable in your
 
 You can also use copy with [resources](copy-resources.md), [properties in a resource](copy-properties.md), and [outputs](copy-outputs.md).
 
-## Variable iteration
+## Syntax
 
 The copy element has the following general format:
 
@@ -28,6 +28,21 @@ The **name** property is any value that identifies the loop. The **count** prope
 
 The **input** property specifies the properties that you want to repeat. You create an array of elements constructed from the value in the **input** property. It can be a single property (like a string), or an object with several properties.
 
+## Copy limits
+
+The count can't exceed 800.
+
+The count can't be a negative number. It can be zero if you deploy the template with a recent version of Azure CLI, PowerShell, or REST API. Specifically, you must use:
+
+* Azure PowerShell **2.6** or later
+* Azure CLI **2.0.74** or later
+* REST API version **2019-05-10** or later
+* [Linked deployments](linked-templates.md) must use API version **2019-05-10** or later for the deployment resource type
+
+Earlier versions of PowerShell, CLI, and the REST API don't support zero for count.
+
+## Variable iteration
+
 The following example shows how to create an array of string values:
 
 ```json
@@ -289,12 +304,6 @@ The next example shows the different ways you can use copy with variables.
 }
 ```
 
-## Copy limits
-
-The count can't exceed 800.
-
-The count can't be a negative number. If you deploy a template with Azure PowerShell 2.6 or later, Azure CLI 2.0.74 or later, or REST API version **2019-05-10** or later, you can set count to zero. Earlier versions of PowerShell, CLI, and the REST API don't support zero for count.
-
 ## Example templates
 
 The following examples show common scenarios for creating more than one value for a variable.
diff --git a/articles/azure-resource-manager/templates/linked-templates.md b/articles/azure-resource-manager/templates/linked-templates.md
@@ -2,7 +2,7 @@
 title: Link templates for deployment
 description: Describes how to use linked templates in an Azure Resource Manager template to create a modular template solution. Shows how to pass parameters values, specify a parameter file, and dynamically created URLs.
 ms.topic: conceptual
-ms.date: 12/11/2019
+ms.date: 04/29/2020
 ---
 # Using linked and nested templates when deploying Azure resources
 
@@ -29,7 +29,7 @@ To nest a template, add a [deployments resource](/azure/templates/microsoft.reso
   "resources": [
     {
       "name": "nestedTemplate1",
-      "apiVersion": "2017-05-10",
+      "apiVersion": "2019-10-01",
       "type": "Microsoft.Resources/deployments",
       "properties": {
         "mode": "Incremental",
@@ -58,7 +58,7 @@ The following example deploys a storage account through a nested template.
   "resources": [
     {
       "name": "nestedTemplate1",
-      "apiVersion": "2017-05-10",
+      "apiVersion": "2019-10-01",
       "type": "Microsoft.Resources/deployments",
       "properties": {
         "mode": "Incremental",
@@ -95,7 +95,7 @@ You set the scope through the `expressionEvaluationOptions` property. By default
 ```json
 {
   "type": "Microsoft.Resources/deployments",
-  "apiVersion": "2017-05-10",
+  "apiVersion": "2019-10-01",
   "name": "nestedTemplate1",
   "properties": {
   "expressionEvaluationOptions": {
@@ -118,7 +118,7 @@ The following template demonstrates how template expressions are resolved accord
   "resources": [
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2017-05-10",
+      "apiVersion": "2019-10-01",
       "name": "nestedTemplate1",
       "properties": {
         "expressionEvaluationOptions": {
@@ -202,7 +202,7 @@ The following example deploys a SQL server and retrieves a key vault secret to u
   "resources": [
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2018-05-01",
+      "apiVersion": "2019-10-01",
       "name": "dynamicSecret",
       "properties": {
         "mode": "Incremental",
@@ -286,7 +286,7 @@ To link a template, add a [deployments resource](/azure/templates/microsoft.reso
   "resources": [
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2017-05-10",
+      "apiVersion": "2019-10-01",
       "name": "linkedTemplate",
       "properties": {
         "mode": "Incremental",
@@ -323,7 +323,7 @@ You can provide the parameters for your linked template either in an external fi
 "resources": [
   {
   "type": "Microsoft.Resources/deployments",
-  "apiVersion": "2018-05-01",
+  "apiVersion": "2019-10-01",
   "name": "linkedTemplate",
   "properties": {
     "mode": "Incremental",
@@ -346,7 +346,7 @@ To pass parameter values inline, use the **parameters** property.
 "resources": [
   {
    "type": "Microsoft.Resources/deployments",
-   "apiVersion": "2018-05-01",
+   "apiVersion": "2019-10-01",
    "name": "linkedTemplate",
    "properties": {
      "mode": "Incremental",
@@ -409,7 +409,7 @@ The following example template shows how to use copy with a nested template.
 "resources": [
   {
   "type": "Microsoft.Resources/deployments",
-  "apiVersion": "2018-05-01",
+  "apiVersion": "2019-10-01",
   "name": "[concat('nestedTemplate', copyIndex())]",
   // yes, copy works here
   "copy":{
@@ -483,7 +483,7 @@ The main template deploys the linked template and gets the returned value. Notic
   "resources": [
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2018-05-01",
+      "apiVersion": "2019-10-01",
       "name": "linkedTemplate",
       "properties": {
         "mode": "Incremental",
@@ -590,7 +590,7 @@ To use the public IP address from the preceding template when deploying a load b
     },
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2018-05-01",
+      "apiVersion": "2019-10-01",
       "name": "linkedTemplate",
       "properties": {
         "mode": "Incremental",
@@ -663,7 +663,7 @@ The following template links to the preceding template. It creates three public
   "resources": [
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2018-05-01",
+      "apiVersion": "2019-10-01",
       "name": "[concat('linkedTemplate', copyIndex())]",
       "copy": {
         "count": 3,
@@ -730,7 +730,7 @@ The following example shows how to pass a SAS token when linking to a template:
   "resources": [
   {
     "type": "Microsoft.Resources/deployments",
-    "apiVersion": "2018-05-01",
+    "apiVersion": "2019-10-01",
     "name": "linkedTemplate",
     "properties": {
     "mode": "Incremental",
