Merge pull request #192060 from davidsmatlak/ds-bicep-links-0316

Adds Bicep links

Author: PRMerger17

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

@@ -11,6 +11,9 @@ This article shows you how to create more than one value for an output in your A
 
 You can also use copy loop with [resources](copy-resources.md), [properties in a resource](copy-properties.md), and [variables](copy-variables.md).
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [loops](../bicep/loops.md).
+
 ## Syntax
 
 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:
@@ -167,4 +170,4 @@ The preceding example returns an array with the following values:
   - [Property iteration in ARM templates](copy-properties.md)
   - [Variable iteration in ARM templates](copy-variables.md)
 - If you want to learn about the sections of a template, see [Understand the structure and syntax of ARM templates](./syntax.md).
-- To learn how to deploy your template, see [Deploy resources with ARM templates and Azure PowerShell](deploy-powershell.md).
+- To learn how to deploy your template, see [Deploy resources with ARM templates and Azure PowerShell](deploy-powershell.md).

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

@@ -13,6 +13,9 @@ You can only use copy loop with top-level resources, even when applying copy loo
 
 You can also use copy loop with [resources](copy-resources.md), [variables](copy-variables.md), and [outputs](copy-outputs.md).
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [loops](../bicep/loops.md).
+
 ## Syntax
 
 Add the `copy` element to the resources section of your template to set the number of items for a property. The copy element has the following general format:

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

@@ -13,6 +13,10 @@ You can also use copy loop with [properties](copy-properties.md), [variables](co
 
 If you need to specify whether a resource is deployed at all, see [condition element](conditional-resource-deployment.md).
 
+
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [loops](../bicep/loops.md).
+
 ## Syntax
 
 Add the `copy` element to the resources section of your template to deploy multiple instances of the resource. The `copy` element has the following general format:

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

@@ -10,6 +10,9 @@ 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).
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [loops](../bicep/loops.md).
+
 ## Syntax
 
 The copy element has the following general format:

articles/azure-resource-manager/templates/deploy-cli.md

@@ -17,6 +17,10 @@ The deployment commands changed in Azure CLI version 2.2.0. The examples in this
 
 If you don't have Azure CLI installed, you can use Azure Cloud Shell. For more information, see [Deploy ARM templates from Azure Cloud Shell](deploy-cloud-shell.md).
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [How to deploy resources with Bicep and Azure CLI](../bicep/deploy-cli.md).
+
+
 [!INCLUDE [permissions](../../../includes/template-deploy-permissions.md)]
 
 ## Deployment scope
@@ -244,7 +248,7 @@ az deployment group create \
   --resource-group testgroup \
   --template-file <path-to-template> \
   --parameters $params
-``` 
+```
 
 However, if you're using Azure CLI with Windows Command Prompt (CMD) or PowerShell, set the variable to a JSON string. Escape the quotation marks: `$params = '{ \"prefix\": {\"value\":\"start\"}, \"suffix\": {\"value\":\"end\"} }'`.
 
@@ -291,4 +295,4 @@ To deploy a template with multi-line strings or comments using Azure CLI with ve
 * To roll back to a successful deployment when you get an error, see [Rollback on error to successful deployment](rollback-on-error.md).
 * To specify how to handle resources that exist in the resource group but aren't defined in the template, see [Azure Resource Manager deployment modes](deployment-modes.md).
 * To understand how to define parameters in your template, see [Understand the structure and syntax of ARM templates](./syntax.md).
-* For tips on resolving common deployment errors, see [Troubleshoot common Azure deployment errors with Azure Resource Manager](common-deployment-errors.md).
+* For tips on resolving common deployment errors, see [Troubleshoot common Azure deployment errors with Azure Resource Manager](common-deployment-errors.md).

articles/azure-resource-manager/templates/deploy-powershell.md

@@ -10,6 +10,9 @@ ms.custom: devx-track-azurepowershell
 
 This article explains how to use Azure PowerShell with Azure Resource Manager templates (ARM templates) to deploy your resources to Azure. If you aren't familiar with the concepts of deploying and managing your Azure solutions, see [template deployment overview](overview.md).
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [Deploy resources with Bicep and Azure PowerShell](../bicep/deploy-powershell.md).
+
 ## Prerequisites
 
 You need a template to deploy. If you don't already have one, download and save an [example template](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.storage/storage-account-create/azuredeploy.json) from the Azure Quickstart templates repo. The local file name used in this article is _C:\MyTemplates\azuredeploy.json_.

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

@@ -20,6 +20,9 @@ For a tutorial, see [Tutorial: Deploy a linked template](./deployment-tutorial-l
 > If the linked or nested template targets a different resource group, that deployment uses incremental mode.
 >
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [modules](../bicep/modules.md).
+
 ## Nested template
 
 To nest a template, add a [deployments resource](/azure/templates/microsoft.resources/deployments) to your main template. In the `template` property, specify the template syntax.

articles/azure-resource-manager/templates/parameter-files.md

@@ -10,6 +10,9 @@ ms.custom: devx-track-azurepowershell
 
 Rather than passing parameters as inline values in your script, you can use a JSON file that contains the parameter values. This article shows how to create a parameter file that you use with a JSON template.
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [parameter files](../bicep/parameter-files.md).
+
 ## Parameter file
 
 A parameter file uses the following format:
@@ -230,4 +233,4 @@ If your template includes a parameter with the same name as one of the parameter
 ## Next steps
 
 - For more information about how to define parameters in a template, see [Parameters in ARM templates](./parameters.md).
-- For more information about using values from a key vault, see [Use Azure Key Vault to pass secure parameter value during deployment](key-vault-parameter.md).
+- For more information about using values from a key vault, see [Use Azure Key Vault to pass secure parameter value during deployment](key-vault-parameter.md).

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

@@ -11,6 +11,9 @@ When deploying resources, you may need to make sure some resources exist before
 
 Azure Resource Manager evaluates the dependencies between resources, and deploys them in their dependent order. When resources aren't dependent on each other, Resource Manager deploys them in parallel. You only need to define dependencies for resources that are deployed in the same template.
 
+> [!TIP]
+> We recommend [Bicep](../bicep/overview.md) because it offers the same capabilities as ARM templates and the syntax is easier to use. To learn more, see [resource dependencies](../bicep/resource-dependencies.md).
+
 ## dependsOn
 
 Within your Azure Resource Manager template (ARM template), the `dependsOn` element enables you to define one resource as a dependent on one or more resources. Its value is a JavaScript Object Notation (JSON) array of strings, each of which is a resource name or ID. The array can include resources that are [conditionally deployed](conditional-resource-deployment.md). When a conditional resource isn't deployed, Azure Resource Manager automatically removes it from the required dependencies.
@@ -213,4 +216,4 @@ For information about assessing the deployment order and resolving dependency er
 * For recommendations when setting dependencies, see [ARM template best practices](./best-practices.md).
 * To learn about troubleshooting dependencies during deployment, see [Troubleshoot common Azure deployment errors with Azure Resource Manager](common-deployment-errors.md).
 * To learn about creating Azure Resource Manager templates, see [Understand the structure and syntax of ARM templates](./syntax.md).
-* For a list of the available functions in a template, see [ARM template functions](template-functions.md).
+* For a list of the available functions in a template, see [ARM template functions](template-functions.md).

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

@@ -83,6 +83,8 @@ The available properties for a parameter are:
 
 For examples of how to use parameters, see [Parameters in ARM templates](./parameters.md).
 
+In Bicep, see [parameters](../bicep/file.md#parameters).
+
 ## Variables
 
 In the `variables` section, you construct values that can be used throughout your template. You don't need to define variables, but they often simplify your template by reducing complex expressions. The format of each variable matches one of the [data types](data-types.md).
@@ -118,6 +120,8 @@ For information about using `copy` to create several values for a variable, see
 
 For examples of how to use variables, see [Variables in ARM template](./variables.md).
 
+In Bicep, see [variables](../bicep/file.md#variables).
+
 ## Functions
 
 Within your template, you can create your own functions. These functions are available for use in your template. Typically, you define complicated expressions that you don't want to repeat throughout your template. You create the user-defined functions from expressions and [functions](template-functions.md) that are supported in templates.
@@ -163,6 +167,8 @@ When defining a user function, there are some restrictions:
 
 For examples of how to use custom functions, see [User-defined functions in ARM template](./user-defined-functions.md).
 
+In Bicep, user-defined functions aren't supported. Bicep does support a variety of [functions](../bicep/bicep-functions.md) and [operators](../bicep/operators.md).
+
 ## Resources
 
 In the `resources` section, you define the resources that are deployed or updated.
@@ -249,6 +255,8 @@ You define resources with the following structure:
 | 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). |
 
+In Bicep, see [resources](../bicep/file.md#resources).
+
 ## Outputs
 
 In the `outputs` section, you specify values that are returned from deployment. Typically, you return values from resources that were deployed.
@@ -279,6 +287,8 @@ The following example shows the structure of an output definition:
 
 For examples of how to use outputs, see [Outputs in ARM template](./outputs.md).
 
+In Bicep, see [outputs](../bicep/file.md#outputs).
+
 <a id="comments"></a>
 
 ## Comments and metadata
@@ -309,6 +319,8 @@ In Visual Studio Code, the [Azure Resource Manager Tools extension](quickstart-c
 
 ![Visual Studio Code Azure Resource Manager template mode](./media/template-syntax/resource-manager-template-editor-mode.png)
 
+In Bicep, see [comments](../bicep/file.md#comments).
+
 ### Metadata
 
 You can add a `metadata` object almost anywhere in your template. Resource Manager ignores the object, but your JSON editor may warn you that the property isn't valid. In the object, define the properties you need.
@@ -409,6 +421,8 @@ You can break a string into multiple lines. For example, see the `location` prop
   ],
 ```
 
+In Bicep, see [multi-line strings](../bicep/file.md#multi-line-strings).
+
 ## Next steps
 
 * To view complete templates for many different types of solutions, see the [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/).