revisions and redirects

Author: tfitzmac

.openpublishing.redirection.json

@@ -10068,6 +10068,31 @@
       "redirect_url": "/azure/azure-resource-manager/management/extension-resource-types",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/azure-resource-manager/bicep/loop-modules.md",
+      "redirect_url": "/azure/azure-resource-manager/bicep/loops",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-resource-manager/bicep/loop-outputs.md",
+      "redirect_url": "/azure/azure-resource-manager/bicep/loops",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-resource-manager/bicep/loop-properties.md",
+      "redirect_url": "/azure/azure-resource-manager/bicep/loops",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-resource-manager/bicep/loop-resources.md",
+      "redirect_url": "/azure/azure-resource-manager/bicep/loops",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-resource-manager/bicep/loop-variables.md",
+      "redirect_url": "/azure/azure-resource-manager/bicep/loops",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/azure-resource-manager/templates/compare-template-syntax.md",
       "redirect_url": "/azure/azure-resource-manager/bicep/compare-template-syntax",

articles/azure-resource-manager/bicep/loops.md

@@ -7,7 +7,7 @@ ms.date: 10/19/2021
 
 # Iterative loops in Bicep
 
-This article shows you how to use the `for` syntax to iterate over items in a collection. You can use loops to define multiple copies of a resource, property, variable, module, or output. Use loops to avoid repeating syntax in your Bicep file and to dynamically set the number of copies to create during deployment.
+This article shows you how to use the `for` syntax to iterate over items in a collection. You can use loops to define multiple copies of a resource, module, variable, property, or output. Use loops to avoid repeating syntax in your Bicep file and to dynamically set the number of copies to create during deployment.
 
 ### Microsoft Learn
 
@@ -17,7 +17,7 @@ To learn more about loops, and for hands-on guidance, see [Build flexible Bicep
 
 Loops can be declared by:
 
-- Using an **integer index**. This option works when your scenario is: "I want to create this many instances." The [range function](bicep-functions-array.md#range) creates an array of integers from the start index and containing the number of specified elements. Within the loop, you can use the integer index to modify values. For more information, see [Integer index](#integer-index).
+- Using an **integer index**. This option works when your scenario is: "I want to create this many instances." The [range function](bicep-functions-array.md#range) creates an array of integers that begins at the start index and contains the number of specified elements. Within the loop, you can use the integer index to modify values. For more information, see [Integer index](#integer-index).
 
   ```bicep
   [for <index> in range(<startIndex>, <numberOfElements>): {
@@ -59,15 +59,15 @@ Loops can be declared by:
 
 ## Loop limits
 
-Bicep loop has these limitations:
+Using loops in Bicep has these limitations:
 
 - Loop iterations can't be a negative number or exceed 800 iterations.
 - Can't loop a resource with nested child resources. Change the child resources to top-level resources.  See [Iteration for a child resource](#iteration-for-a-child-resource).
 - Can't loop on multiple levels of properties.
 
 ## Integer index
 
-For a simple example of using an index, create a **variable** for an array of strings.
+For a simple example of using an index, create a **variable** that contains an array of strings.
 
 ```bicep
 param itemCount int = 5
@@ -154,38 +154,7 @@ resource storageAcct 'Microsoft.Storage/storageAccounts@2021-02-01' = [for name
 
 The next example iterates over an array to define a property. It creates two subnets within a virtual network.
 
-```bicep
-param rgLocation string = resourceGroup().location
-
-var subnets = [
-  {
-    name: 'api'
-    subnetPrefix: '10.144.0.0/24'
-  }
-  {
-    name: 'worker'
-    subnetPrefix: '10.144.1.0/24'
-  }
-]
-
-resource vnet 'Microsoft.Network/virtualNetworks@2020-07-01' = {
-  name: 'vnet'
-  location: rgLocation
-  properties: {
-    addressSpace: {
-      addressPrefixes: [
-        '10.144.0.0/20'
-      ]
-    }
-    subnets: [for subnet in subnets: {
-      name: subnet.name
-      properties: {
-        addressPrefix: subnet.subnetPrefix
-      }
-    }]
-  }
-}
-```
+::: code language="bicep" source="~/azure-docs-bicep-samples/samples/loops/loopproperty.bicep" highlight="23-28" :::
 
 ## Array and index
 
@@ -254,7 +223,7 @@ output deployedNSGs array = [for (name, i) in orgNames: {
 
 ## Dictionary object
 
-When you want to iterate over elements in a dictionary object, use the [items function](bicep-functions-array.md#items) to convert the object to an array. Use the `value` property to get properties on the objects.
+To iterate over elements in a dictionary object, use the [items function](bicep-functions-array.md#items), which converts the object to an array. Use the `value` property to get properties on the objects.
 
 ```bicep
 param nsgValues object = {
@@ -278,7 +247,7 @@ resource nsg 'Microsoft.Network/networkSecurityGroups@2020-06-01' = [for nsg in
 
 For **resources and modules**, you can add an `if` expression with the loop syntax to conditionally deploy the collection.
 
-The following example shows a nested loop combined with a filtered resource loop. Filters must be expressions that evaluate to a boolean value. In this example, a single condition is applied to all instances of the module.
+The following example shows a loop combined with a condition statement. In this example, a single condition is applied to all instances of the module.
 
 ```bicep
 param location string

articles/azure-resource-manager/bicep/outputs.md

@@ -39,7 +39,7 @@ var user = {
 output stringOutput string = user['user-name']
 ```
 
-To return one of two values depending a condition in the deployment, use the the `?` operator. For more information, see [Conditional output](#conditional-output).
+When the value to return depends on a condition in the deployment, use the the `?` operator. For more information, see [Conditional output](#conditional-output).
 
 ```bicep
 output <name> <data-type> = <condition> ? <true-value> : <false-value>

articles/azure-resource-manager/bicep/resource-declaration.md

@@ -13,56 +13,52 @@ This article describes the syntax you use to add a resource to your Bicep file.
 
 ## Declaration
 
-Add a resource declaration by using the `resource` keyword. The values you provide in the declaration are described in more details in this article.
+Add a resource declaration by using the `resource` keyword. You set a symbolic name for the resource. The symbolic name isn't the same as the resource name. You use the symbolic name to reference the resource in other parts of your Bicep file.
 
 ```bicep
-resource <symbolic-name> '<resource-type>@<api-version>' = {
+resource <symbolic-name> '<full-type-name>@<api-version>' = {
   <resource-properties>
 }
 ```
 
+So, a declaration for a storage account can start with:
+
+```bicep
+resource stg 'Microsoft.Storage/storageAccounts@2021-04-01' = {
+  ...
+}
+```
+
+Symbolic names are case-sensitive.  They may contain letters, numbers, and _; but can't start with a number.
+
+For the available resource types and version, see [Bicep resource reference](/azure/templates/). Bicep doesn't support `apiProfile`, which is available in [Azure Resource Manager templates (ARM templates) JSON](../templates/syntax.md).
+
 To conditionally deploy a resource, use the `if` syntax. For more information, see [Conditional deployment in Bicep](conditional-resource-deployment.md).
 
 ```bicep
-resource <symbolic-name> '<resource-type>@<api-version>' = if (condition) {
+resource <symbolic-name> '<full-type-name>@<api-version>' = if (condition) {
   <resource-properties>
 }
 ```
 
 To deploy more than one instance of a resource, use the `for` syntax. For more information, see [Iterative loops in Bicep](loops.md).
 
 ```bicep
-resource <symbolic-name> '<resource-type>@<api-version>' = [for <item> in <collection>: {
+resource <symbolic-name> '<full-type-name>@<api-version>' = [for <item> in <collection>: {
   <properties-to-repeat>
 }]
 ```
 
 You can also use the `for` syntax on the resource properties to create an array.
 
 ```bicep
-resource <symbolic-name> '<resource-type>@<api-version>' = {
+resource <symbolic-name> '<full-type-name>@<api-version>' = {
   properties: {
     <array-property>: [for <item> in <collection>: <value-to-repeat>]
   }
 }
 ```
 
-## Resource type and version
-
-When adding a resource to your Bicep file, start by setting the resource type and API version. These values determine the other properties that are available for the resource.
-
-The following example shows how to set the resource type and API version for a storage account. The example doesn't show the full resource declaration.
-
-```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
-  ...
-}
-```
-
-You set a symbolic name for the resource. In the preceding example, the symbolic name is `stg`.  The symbolic name isn't the same as the resource name. You use the symbolic name to reference the resource in other parts of your Bicep file. Symbolic names are case-sensitive.  They may contain letters, numbers, and _; but can't start with a number.
-
-Bicep doesn't support `apiProfile`, which is available in [Azure Resource Manager templates (ARM templates) JSON](../templates/syntax.md).
-
 ## Resource name
 
 Each resource has a name. When setting the resource name, pay attention to the [rules and restrictions for resource names](../management/resource-name-rules.md).
@@ -173,7 +169,7 @@ resource vm 'Microsoft.Compute/virtualMachines@2020-06-01' = {
 
 The preceding properties are generic to most resource types. After setting those values, you need to set the properties that are specific to the resource type you're deploying.
 
-Use intellisense or [template reference](/azure/templates/) to determine which properties are available and which ones are required. The following example sets the remaining properties for a storage account.
+Use intellisense or [Bicep resource reference](/azure/templates/) to determine which properties are available and which ones are required. The following example sets the remaining properties for a storage account.
 
 ```bicep
 resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
@@ -190,8 +186,6 @@ resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
 }
 ```
 
-To assign an array to a property, use the `for` syntax.
-
 ## Dependencies
 
 When deploying resources, you may need to make sure some resources exist before other resources. For example, you need a logical SQL server before deploying a database. You establish this relationship by marking one resource as dependent on the other resource. Order of resource deployment can be influenced in two ways: [implicit dependency](#implicit-dependency) and [explicit dependency](#explicit-dependency)