adds cross reference links

davidsmatlak · davidsmatlak · commit ebe05d6084c5 · 2022-01-19T14:56:10.000-08:00
diff --git a/articles/azure-resource-manager/templates/child-resource-name-type.md b/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: 05/07/2021
+ms.date: 01/19/2022
 ---
 
 # Set name and type for child resources
@@ -13,6 +13,9 @@ Each parent resource accepts only certain resource types as child resources. The
 
 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.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [child resources](../bicep/child-resource-name-type.md).
+
 ## Within parent resource
 
 The following example shows the child resource included within the resources property of the parent resource.
@@ -130,4 +133,4 @@ The following example shows a virtual network and subnet that are both defined a
 ## Next steps
 
 * To learn about creating ARM templates, see [Understand the structure and syntax of ARM templates](./syntax.md).
-* To learn about the format of the resource name when referencing the resource, see the [reference function](template-functions-resource.md#reference).
+* To learn about the format of the resource name when referencing the resource, see the [reference function](template-functions-resource.md#reference).
diff --git a/articles/azure-resource-manager/templates/conditional-resource-deployment.md b/articles/azure-resource-manager/templates/conditional-resource-deployment.md
@@ -2,7 +2,7 @@
 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: 05/07/2021
+ms.date: 01/19/2022
 ---
 
 # Conditional deployment in ARM templates
@@ -12,6 +12,9 @@ Sometimes you need to optionally deploy a resource in an Azure Resource Manager
 > [!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.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [conditional deployments](../bicep/conditional-resource-deployment.md).
+
 ## Deploy condition
 
 You can pass in a parameter value that indicates whether a resource is deployed. The following example conditionally deploys a DNS zone.
@@ -106,4 +109,4 @@ If you deploy a template with [complete mode](deployment-modes.md) and a resourc
 
 * For a Microsoft Learn module that covers conditional deployment, see [Manage complex cloud deployments by using advanced ARM template features](/learn/modules/manage-deployments-advanced-arm-template-features/).
 * For recommendations about creating templates, see [ARM template best practices](./best-practices.md).
-* To create multiple instances of a resource, see [Resource iteration in ARM templates](copy-resources.md).
+* To create multiple instances of a resource, see [Resource iteration in ARM templates](copy-resources.md).
diff --git a/articles/azure-resource-manager/templates/deploy-to-management-group.md b/articles/azure-resource-manager/templates/deploy-to-management-group.md
@@ -2,14 +2,17 @@
 title: Deploy resources to management group
 description: Describes how to deploy resources at the management group scope in an Azure Resource Manager template.
 ms.topic: conceptual
-ms.date: 11/22/2021
+ms.date: 01/19/2022
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ---
 
 # Management group deployments with ARM templates
 
 As your organization matures, you can deploy an Azure Resource Manager template (ARM template) to create resources at the management group level. For example, you may need to define and assign [policies](../../governance/policy/overview.md) or [Azure role-based access control (Azure RBAC)](../../role-based-access-control/overview.md) for a management group. With management group level templates, you can declaratively apply policies and assign roles at the management group level.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [management group deployments](../bicep/deploy-to-management-group.md).
+
 ## Supported resources
 
 Not all resource types can be deployed to the management group level. This section lists which resource types are supported.
diff --git a/articles/azure-resource-manager/templates/deploy-to-resource-group.md b/articles/azure-resource-manager/templates/deploy-to-resource-group.md
@@ -2,14 +2,17 @@
 title: Deploy resources to resource groups
 description: Describes how to deploy resources in an Azure Resource Manager template. It shows how to target more than one resource group.
 ms.topic: conceptual
-ms.date: 10/01/2021
+ms.date: 01/19/2022
 ms.custom: devx-track-azurepowershell
 ---
 
 # Resource group deployments with ARM templates
 
 This article describes how to scope your deployment to a resource group. You use an Azure Resource Manager template (ARM template) for the deployment. The article also shows how to expand the scope beyond the resource group in the deployment operation.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [resource group deployments](../bicep/deploy-to-resource-group.md).
+
 ## Supported resources
 
 Most resources can be deployed to a resource group. For a list of available resources, see [ARM template reference](/azure/templates).
diff --git a/articles/azure-resource-manager/templates/deploy-to-subscription.md b/articles/azure-resource-manager/templates/deploy-to-subscription.md
@@ -2,7 +2,7 @@
 title: Deploy resources to subscription
 description: Describes how to create a resource group in an Azure Resource Manager template. It also shows how to deploy resources at the Azure subscription scope.
 ms.topic: conceptual
-ms.date: 11/22/2021
+ms.date: 01/19/2022
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ---
 
@@ -15,6 +15,9 @@ To simplify the management of resources, you can use an Azure Resource Manager t
 
 To deploy templates at the subscription level, use Azure CLI, PowerShell, REST API, or the portal.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [subscription deployments](../bicep/deploy-to-subscription.md).
+
 ## Supported resources
 
 Not all resource types can be deployed to the subscription level. This section lists which resource types are supported.
diff --git a/articles/azure-resource-manager/templates/deploy-to-tenant.md b/articles/azure-resource-manager/templates/deploy-to-tenant.md
@@ -2,14 +2,17 @@
 title: Deploy resources to tenant
 description: Describes how to deploy resources at the tenant scope in an Azure Resource Manager template.
 ms.topic: conceptual
-ms.date: 11/22/2021
+ms.date: 01/19/2022
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ---
 
 # Tenant deployments with ARM templates
 
 As your organization matures, you may need to define and assign [policies](../../governance/policy/overview.md) or [Azure role-based access control (Azure RBAC)](../../role-based-access-control/overview.md) across your Azure AD tenant. With tenant level templates, you can declaratively apply policies and assign roles at a global level.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [tenant deployments](../bicep/deploy-to-tenant.md).
+
 ## Supported resources
 
 Not all resource types can be deployed to the tenant level. This section lists which resource types are supported.
diff --git a/articles/azure-resource-manager/templates/outputs.md b/articles/azure-resource-manager/templates/outputs.md
@@ -2,7 +2,7 @@
 title: Outputs in templates
 description: Describes how to define output values in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 05/18/2021 
+ms.date: 01/19/2022
 ms.custom: devx-track-azurepowershell
 ---
 
@@ -12,6 +12,9 @@ This article describes how to define output values in your Azure Resource Manage
 
 The format of each output value must resolve to one of the [data types](data-types.md).
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [outputs](../bicep/outputs.md).
+
 ## Define output values
 
 The following example shows how to return a property from a deployed resource.
@@ -144,4 +147,4 @@ az deployment group show \
 
 ## Next steps
 
-* To learn about the available properties for outputs, see [Understand the structure and syntax of ARM templates](./syntax.md).
+* To learn about the available properties for outputs, see [Understand the structure and syntax of ARM templates](./syntax.md).
diff --git a/articles/azure-resource-manager/templates/parameters.md b/articles/azure-resource-manager/templates/parameters.md
@@ -2,7 +2,7 @@
 title: Parameters in templates
 description: Describes how to define parameters in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 05/14/2021
+ms.date: 01/19/2022
 ---
 
 # Parameters in ARM templates
@@ -13,6 +13,9 @@ Resource Manager resolves parameter values before starting the deployment operat
 
 Each parameter must be set to one of the [data types](data-types.md).
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [parameters](../bicep/parameters.md).
+
 ## Minimal declaration
 
 At a minimum, every parameter needs a name and type.
diff --git a/articles/azure-resource-manager/templates/resource-declaration.md b/articles/azure-resource-manager/templates/resource-declaration.md
@@ -2,13 +2,16 @@
 title: Declare resources in templates
 description: Describes how to declare resources to deploy in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 05/11/2021
+ms.date: 01/19/2022
 ---
 
 # Resource declaration in ARM templates
 
 To deploy a resource through an Azure Resource Manager template (ARM template), you add a resource declaration. Use the `resources` array in a JSON template.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [resource declaration](../bicep/resource-declaration.md).
+
 ## Set resource type and version
 
 When adding a resource to your template, start by setting the resource type and API version. These values determine the other properties that are available for the resource.
@@ -124,4 +127,4 @@ Use intellisense or [template reference](/azure/templates/) to determine which p
 ## Next steps
 
 * To conditionally deploy a resource, see [Conditional deployment in ARM templates](conditional-resource-deployment.md).
-* To set resource dependencies, see [Define the order for deploying resources in ARM templates](./resource-dependency.md).
+* To set resource dependencies, see [Define the order for deploying resources in ARM templates](./resource-dependency.md).
diff --git a/articles/azure-resource-manager/templates/variables.md b/articles/azure-resource-manager/templates/variables.md
@@ -2,7 +2,7 @@
 title: Variables in templates
 description: Describes how to define variables in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
-ms.date: 06/24/2021
+ms.date: 01/19/2022
 ---
 
 # Variables in ARM templates
@@ -11,6 +11,9 @@ This article describes how to define and use variables in your Azure Resource Ma
 
 Resource Manager resolves variables before starting the deployment operations. Wherever the variable is used in the template, Resource Manager replaces it with the resolved value.
 
+> [!TIP]
+> For an improved authoring experience, you can use Bicep rather than JSON to develop templates. For more information about Bicep syntax, see [variables](../bicep/variables.md).
+
 ## Define variable
 
 When defining a variable, you don't specify a [data type](data-types.md) for the variable. Instead provide a value or template expression. The variable type is inferred from the resolved value. The following example sets a variable to a string.
@@ -84,4 +87,4 @@ You can define variables that hold related values for configuring an environment
 
 * To learn about the available properties for variables, see [Understand the structure and syntax of ARM templates](./syntax.md).
 * For recommendations about creating variables, see [Best practices - variables](./best-practices.md#variables).
-* For an example template that assigns security rules to a network security group, see [network security rules](https://github.com/Azure/azure-docs-json-samples/blob/master/azure-resource-manager/multipleinstance/multiplesecurityrules.json) and [parameter file](https://github.com/Azure/azure-docs-json-samples/blob/master/azure-resource-manager/multipleinstance/multiplesecurityrules.parameters.json).
+* For an example template that assigns security rules to a network security group, see [network security rules](https://github.com/Azure/azure-docs-json-samples/blob/master/azure-resource-manager/multipleinstance/multiplesecurityrules.json) and [parameter file](https://github.com/Azure/azure-docs-json-samples/blob/master/azure-resource-manager/multipleinstance/multiplesecurityrules.parameters.json).
