Merge pull request #157932 from davidsmatlak/ds-rb-templates-0507

Removes Bicep content and code samples (PR 1)

Author: GitHubber17

articles/azure-resource-manager/templates/add-resource-extensions.md

@@ -1,13 +1,13 @@
 ---
-title: Post-deployment configuration by using extensions (Bicep)
-description: Learn how to use Azure Resource Manager template (ARM template) extensions to provide post-deployment configurations. (Bicep)
+title: Post-deployment configuration with extensions
+description: Learn how to use Azure Resource Manager template (ARM template) extensions for post-deployment configurations.
 author: mumian
 ms.topic: conceptual
 ms.date: 12/14/2018
 ms.author: jgao
 ---
 
-# Provide post-deployment configurations by using extensions (Bicep)
+# Post-deployment configurations by using extensions
 
 Azure Resource Manager template (ARM template) extensions are small applications that provide post-deployment configuration and automation tasks on Azure resources. The most popular one is virtual machine extensions. See [Virtual machine extensions and features for Windows](../../virtual-machines/extensions/features-windows.md), and [Virtual machine extensions and features for Linux](../../virtual-machines/extensions/features-linux.md).
 

articles/azure-resource-manager/templates/child-resource-name-type.md

@@ -2,7 +2,7 @@
 title: Child resources in templates
 description: Describes how to set the name and type for child resources in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 04/23/2021
+ms.date: 05/07/2021
 ---
 
 # Set name and type for child resources
@@ -11,16 +11,12 @@ Child resources are resources that exist only within the context of another reso
 
 Each parent resource accepts only certain resource types as child resources. The resource type for the child resource includes the resource type for the parent resource. For example, `Microsoft.Web/sites/config` and `Microsoft.Web/sites/extensions` are both child resources of the `Microsoft.Web/sites`. The accepted resource types are specified in the [template schema](https://github.com/Azure/azure-resource-manager-schemas) of the parent resource.
 
-[!INCLUDE [Bicep preview](../../../includes/resource-manager-bicep-preview.md)]
-
 In an Azure Resource Manager template (ARM template), you can specify the child resource either within the parent resource or outside of the parent resource. The values you provide for the resource name and resource type vary based on whether the child resource is defined inside or outside of the parent resource.
 
 ## Within parent resource
 
 The following example shows the child resource included within the resources property of the parent resource.
 
-# [JSON](#tab/json)
-
 ```json
 "resources": [
   {
@@ -78,65 +74,10 @@ The full resource type is still `Microsoft.Network/virtualNetworks/subnets`. You
 
 The child resource name is set to **Subnet1** but the full name includes the parent name. You don't provide **VNet1** because it's assumed from the parent resource.
 
-# [Bicep](#tab/bicep)
-
-```bicep
-resource <parent-resource-symbolic-name> '<resource-type>@<api-version>' = {
-  <parent-resource-properties>
-
-  resource <child-resource-symbolic-name> '<child-resource-type>' = {
-    <child-resource-properties>
-  }
-}
-```
-
-A nested resource declaration must appear at the top level of syntax of the parent resource. Declarations may be nested arbitrarily deep, as long as each level is a child type of its parent resource.
-
-When defined within the parent resource type, you format the type and name values as a single segment without slashes. The following example shows a virtual network and with a subnet. Notice that the subnet is included within the resources array for the virtual network. The name is set to **Subnet1** and the type is set to **subnets**.
-
-```bicep
-param location string
-
-resource VNet1 'Microsoft.Network/virtualNetworks@2018-10-01' = {
-  name: 'VNet1'
-  location: location
-  properties: {
-    addressSpace: {
-      addressPrefixes: [
-        '10.0.0.0/16'
-      ]
-    }
-  }
-
-  resource VNet1_Subnet1 'subnets' = {
-    name: 'Subnet1'
-    properties: {
-      addressPrefix: '10.0.0.0/24'
-    }
-  }
-}
-```
-
-The full resource type is still `Microsoft.Network/virtualNetworks/subnets`. You don't provide `Microsoft.Network/virtualNetworks/` because it's assumed from the parent resource type and version. The nested resource may optionally declare an API version using the syntax `<segment>@<version>`. If the nested resource omits the API version, the API version of the parent resource is used. If the nested resource specifies an API version, the API version specified is used.
-
-The child resource name is set to **Subnet1** but the full name includes the parent name. You don't provide VNet1 because it's assumed from the parent resource.
-
-To access the child resource symbolic name, you need to use the `::` operator. For example, to output a property from a child resource:
-
-```bicep
-output childAddressPrefix string = VNet1::VNet1_Subnet1.properties.addressPrefix
-```
-
-A nested resource can access properties of its parent resource. Other resources declared inside the body of the same parent resource can reference each other and the typical rules about cyclic-dependencies apply. A parent resource may not access properties of the resources it contains, this would cause a cyclic-dependency.
-
----
-
 ## Outside parent resource
 
 The following example shows the child resource outside of the parent resource. You might use this approach if the parent resource isn't deployed in the same template, or if want to use [copy](copy-resources.md) to create more than one child resource.
 
-# [JSON](#tab/json)
-
 ```json
 "resources": [
   {
@@ -186,47 +127,6 @@ The following example shows a virtual network and subnet that are both defined a
 ]
 ```
 
-# [Bicep](#tab/bicep)
-
-```bicep
-resource <parent-resource-symbolic-name> '<resource-type>@<api-version>' = {
-  <parent-resource-properties>
-}
-
-resource <child-resource-symbolic-name> '<child-resource-type>@<api-version>' = {
-  <child-resource-properties>
-}
-```
-
-When defined outside of the parent resource, you format the type and with slashes to include the parent type and name.
-
-The following example shows a virtual network and subnet that are both defined at the root level. Notice that the subnet isn't included within the resources array for the virtual network. The name is set to **VNet1/Subnet1** and the type is set to `Microsoft.Network/virtualNetworks/subnets`. The child resource is marked as dependent on the parent resource because the parent resource must exist before the child resource can be deployed.
-
-```bicep
-param location string
-
-resource VNet1 'Microsoft.Network/virtualNetworks@2018-10-01' = {
-  name: 'VNet1'
-  location: location
-  properties: {
-    addressSpace: {
-      addressPrefixes: [
-        '10.0.0.0/16'
-      ]
-    }
-  }
-}
-
-resource VNet1_Subnet1 'Microsoft.Network/virtualNetworks/subnets@2018-10-01' = {
-  name: '${VNet1.name}/Subnet1'
-  properties: {
-    addressPrefix: '10.0.0.0/24'
-  }
-}
-```
-
----
-
 ## Next steps
 
 * To learn about creating ARM templates, see [Understand the structure and syntax of ARM templates](template-syntax.md).

articles/azure-resource-manager/templates/conditional-resource-deployment.md

@@ -2,12 +2,12 @@
 title: Conditional deployment with templates
 description: Describes how to conditionally deploy a resource in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 03/02/2021
+ms.date: 05/07/2021
 ---
 
 # Conditional deployment in ARM templates
 
-Sometimes you need to optionally deploy a resource in an Azure Resource Manager template (ARM template) or Bicep file. For JSON templates, use the `condition` element to specify whether the resource is deployed. For Bicep, use the `if` keyword to specify whether the resource is deployed. The value for the condition resolves to true or false. When the value is true, the resource is created. When the value is false, the resource isn't created. The value can only be applied to the whole resource.
+Sometimes you need to optionally deploy a resource in an Azure Resource Manager template (ARM template). Use the `condition` element to specify whether the resource is deployed. The value for the condition resolves to true or false. When the value is true, the resource is created. When the value is false, the resource isn't created. The value can only be applied to the whole resource.
 
 > [!NOTE]
 > Conditional deployment doesn't cascade to [child resources](child-resource-name-type.md). If you want to conditionally deploy a resource and its child resources, you must apply the same condition to each resource type.
@@ -16,8 +16,6 @@ Sometimes you need to optionally deploy a resource in an Azure Resource Manager
 
 You can pass in a parameter value that indicates whether a resource is deployed. The following example conditionally deploys a DNS zone.
 
-# [JSON](#tab/json)
-
 ```json
 {
   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
@@ -40,27 +38,12 @@ You can pass in a parameter value that indicates whether a resource is deployed.
 }
 ```
 
-# [Bicep](#tab/bicep)
-
-```bicep
-param deployZone bool
-
-resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' = if (deployZone) {
-  name: 'myZone'
-  location: 'global'
-}
-```
-
----
-
-For a more complex example, see [Azure SQL logical server](https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-logical-server).
+For a more complex example, see [Azure SQL logical server](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.sql/sql-logical-server).
 
 ## New or existing resource
 
 You can use conditional deployment to create a new resource or use an existing one. The following example shows how to either deploy a new storage account or use an existing storage account.
 
-# [JSON](#tab/json)
-
 ```json
 {
   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
@@ -103,37 +86,9 @@ You can use conditional deployment to create a new resource or use an existing o
 }
 ```
 
-# [Bicep](#tab/bicep)
-
-```bicep
-param storageAccountName string
-param location string = resourceGroup().location
-
-@allowed([
-  'new'
-  'existing'
-])
-param newOrExisting string = 'new'
-
-resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' = if (newOrExisting == 'new') {
-  name: storageAccountName
-  location: location
-  sku: {
-    name: 'Standard_LRS'
-    tier: 'Standard'
-  }
-  kind: 'StorageV2'
-  properties: {
-    accessTier: 'Hot'
-  }
-}
-```
-
----
-
 When the parameter `newOrExisting` is set to **new**, the condition evaluates to true. The storage account is deployed. However, when `newOrExisting` is set to **existing**, the condition evaluates to false and the storage account isn't deployed.
 
-For a complete example template that uses the `condition` element, see [VM with a new or existing Virtual Network, Storage, and Public IP](https://github.com/Azure/azure-quickstart-templates/tree/master/201-vm-new-or-existing-conditions).
+For a complete example template that uses the `condition` element, see [VM with a new or existing Virtual Network, Storage, and Public IP](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.compute/vm-new-or-existing-conditions).
 
 ## Runtime functions
 

articles/azure-resource-manager/templates/copy-outputs.md

@@ -2,8 +2,9 @@
 title: Define multiple instances of an output value
 description: Use copy operation in an Azure Resource Manager template (ARM template) to iterate multiple times when returning a value from a deployment.
 ms.topic: conceptual
-ms.date: 04/01/2021
+ms.date: 05/07/2021
 ---
+
 # Output iteration in ARM templates
 
 This article shows you how to create more than one value for an output in your Azure Resource Manager template (ARM template). By adding copy loop to the outputs section of your template, you can dynamically return a number of items during deployment.
@@ -12,8 +13,6 @@ You can also use copy loop with [resources](copy-resources.md), [properties in a
 
 ## Syntax
 
-# [JSON](#tab/json)
-
 Add the `copy` element to the output section of your template to return a number of items. The copy element has the following general format:
 
 ```json
@@ -27,37 +26,6 @@ The `count` property specifies the number of iterations you want for the output
 
 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.
 
-# [Bicep](#tab/bicep)
-
-Loops can be used to return a number of items during deployment:
-
-- Iterating over an array:
-
-  ```bicep
-  output <output-name> array = [for <item> in <collection>: {
-    <properties>
-  }]
-
-  ```
-
-- Iterating over the elements of an array
-
-  ```bicep
-  output <output-name> array = [for <item>, <index> in <collection>: {
-    <properties>
-  }]
-  ```
-
-- Using loop index
-
-  ```bicep
-  output <output-name> array = [for <index> in range(<start>, <stop>): {
-    <properties>
-  }]
-  ```
-
----
-
 ## Copy limits
 
 The count can't exceed 800.
@@ -75,8 +43,6 @@ Earlier versions of PowerShell, CLI, and the REST API don't support zero for cou
 
 The following example creates a variable number of storage accounts and returns an endpoint for each storage account:
 
-# [JSON](#tab/json)
-
 ```json
 {
   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
@@ -119,28 +85,6 @@ The following example creates a variable number of storage accounts and returns
 }
 ```
 
-# [Bicep](#tab/bicep)
-
-```bicep
-param storageCount int = 2
-
-var baseName_var = 'storage${uniqueString(resourceGroup().id)}'
-
-resource baseName 'Microsoft.Storage/storageAccounts@2019-04-01' = [for i in range(0, storageCount): {
-  name: '${i}${baseName_var}'
-  location: resourceGroup().location
-  sku: {
-    name: 'Standard_LRS'
-  }
-  kind: 'Storage'
-  properties: {}
-}]
-
-output storageEndpoints array = [for i in range(0, storageCount): reference(${i}${baseName_var}).primaryEndpoints.blob]
-```
-
----
-
 The preceding template returns an array with the following values:
 
 ```json
@@ -152,8 +96,6 @@ The preceding template returns an array with the following values:
 
 The next example returns three properties from the new storage accounts.
 
-# [JSON](#tab/json)
-
 ```json
 {
   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
@@ -200,32 +142,6 @@ The next example returns three properties from the new storage accounts.
 }
 ```
 
-# [Bicep](#tab/bicep)
-
-```bicep
-param storageCount int = 2
-
-var baseName_var = 'storage${uniqueString(resourceGroup().id)}'
-
-resource baseName 'Microsoft.Storage/storageAccounts@2019-04-01' = [for i in range(0, storageCount): {
-  name: '${i}${baseName_var}'
-  location: resourceGroup().location
-  sku: {
-    name: 'Standard_LRS'
-  }
-  kind: 'Storage'
-  properties: {}
-}]
-
-output storageInfo array = [for i in range(0, storageCount): {
-  id: reference(concat(i, baseName_var), '2019-04-01', 'Full').resourceId
-  blobEndpoint: reference(concat(i, baseName_var)).primaryEndpoints.blob
-  status: reference(concat(i, baseName_var)).statusOfPrimary
-}]
-```
-
----
-
 The preceding example returns an array with the following values:
 
 ```json