add a languageVersion 2.0 section

Author: mumian

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

@@ -378,7 +378,7 @@ This Bicep file is transpiled into the following ARM JSON template that utilizes
 ```json
 {
   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
-  "languageVersion": "2.0",
+  "languageVersion": "1.10-experimental",
   "contentVersion": "1.0.0.0",
   "parameters": {
     "location": {
@@ -419,7 +419,7 @@ This Bicep file is transpiled into the following ARM JSON template that utilizes
 }
 ```
 
-Note in the preceding ARM JSON template, `languageVersion` must be set to `2.0` or newer, and the resource element is an object instead of an array.
+Note in the preceding ARM JSON template, `languageVersion` must be set to `1.10-experimental`, and the resource element is an object instead of an array.
 
 ## Next steps
 

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

@@ -8,12 +8,13 @@ ms.date: 08/22/2023
 
 # Type definitions in ARM templates
 
-This article describes how to create and use definitions in your Azure Resource Manager template (ARM template). By defining your own types, you can reuse these types. Type definitions can only be used with [languageVersion 2.0](./syntax.md#template-format).
+This article describes how to create and use definitions in your Azure Resource Manager template (ARM template). By defining your own types, you can reuse these types. Type definitions can only be used with [languageVersion 2.0](./syntax.md#languageversion-20).
+
+[!INCLUDE [VSCode ARM Tools extension doesn't support languageVersion 2.0](../../../includes/resource-manager-vscode-language-version-20.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 [User-defined data types in Bicep](../bicep/user-defined-data-types.md).
 
-
 ## Minimal declaration
 
 At a minimum, every type definition needs a name and type.
@@ -366,7 +367,13 @@ You can add a description to a type definition to help users of your template un
 
 ## Use definition
 
-To reference a type definition, use `"$ref": "#/definitions/<definition-name>"`. The following example shows how to reference a type definition from parameters and outputs.
+To reference a type definition, use the following syntax:
+
+```json
+"$ref": "#/definitions/<definition-name>"
+```
+
+The following example shows how to reference a type definition from parameters and outputs:
 
 ```json
 {

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

@@ -14,13 +14,6 @@ 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]
-> 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 [parameters](../bicep/parameters.md).
-
-You are limited to 256 parameters in a template. For more information, see [Template limits](./best-practices.md#template-limits).
-
-For parameter best practices, see [Parameters](./best-practices.md#parameters).
-
 In addition to minValue, maxValue, minLength, maxLength, and allowedValues, [languageVersion 2.0](./syntax.md#languageversion-20) introduces some aggregate type validation constraints to be used in [definitions](./syntax.md#definitions), [parameters](./syntax.md#parameters) and [outputs](./syntax.md#outputs) definitions. These constraints include:
 
 - [additionalProperties](#additionalproperties)
@@ -30,6 +23,15 @@ In addition to minValue, maxValue, minLength, maxLength, and allowedValues, [lan
 - [prefixItems](#prefixitems)
 - [properties](#properties)
 
+[!INCLUDE [VSCode ARM Tools extension doesn't support languageVersion 2.0](../../../includes/resource-manager-vscode-language-version-20.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 [parameters](../bicep/parameters.md).
+
+You are limited to 256 parameters in a template. For more information, see [Template limits](./best-practices.md#template-limits).
+
+For parameter best practices, see [Parameters](./best-practices.md#parameters).
+
 ## Minimal declaration
 
 At a minimum, every parameter needs a name and type.

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

@@ -10,7 +10,9 @@ ms.date: 09/28/2022
 
 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.
 
-languageVersion 2.0 makes a list of enhancements to ARM JSON templates, such as use symbolic names for resources and change the resource definition from an array to an object. The majority of the samples shown in this article still use `resources` array.  For languageVersion 2.0 specific information, see [Use symbolic name](#use-symbolic-name).
+[languageVersion 2.0](./syntax.md#languageversion-20) makes a list of enhancements to ARM JSON templates, such as use symbolic names for resources and change the resource definition from an array to an object. The majority of the samples shown in this article still use `resources` array.  For languageVersion 2.0 specific information, see [Use symbolic name](#use-symbolic-name).
+
+[!INCLUDE [VSCode ARM Tools extension doesn't support languageVersion 2.0](../../../includes/resource-manager-vscode-language-version-20.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 [resource declaration](../bicep/resource-declaration.md).
@@ -207,7 +209,7 @@ If [Deployments resource](/azure/templates/microsoft.resources/deployments?tabs=
 
 ### Declare existing resources
 
-With [`languageVersion 2.0`](#template-format) and using symbolic name for resource declaration, you can declare existing resources. A top-level resource property of `"existing": true` causes ARM to read rather than deploy a resource as shown in the following example:
+With [`languageVersion 2.0`](./syntax.md#languageversion-20) and using symbolic name for resource declaration, you can declare existing resources. A top-level resource property of `"existing": true` causes ARM to read rather than deploy a resource as shown in the following example:
 
 ```json
 {

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

@@ -35,6 +35,44 @@ The following example shows a network interface that depends on a virtual networ
 }
 ```
 
+With [languageVersion 2.0](./syntax.md#languageversion-20), use resource symbolic name in `dependsOn` arrays. For example:
+
+```json
+{
+  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+  "languageVersion": "2.0",
+  "contentVersion": "1.0.0.0",
+  "parameters": {
+    "location": {
+      "type": "string",
+      "defaultValue": "[resourceGroup().location]"
+    }
+  },
+  "resources": {
+    "myStorage": {
+      "type": "Microsoft.Storage/storageAccounts",
+      "apiVersion": "2023-01-01",
+      "name": "[format('storage{0}', uniqueString(resourceGroup().id))]",
+      "location": "[parameters('location')]",
+      "sku": {
+        "name": "Standard_LRS"
+      },
+      "kind": "StorageV2"
+    },
+    "myVm": {
+      "type": "Microsoft.Compute/virtualMachines",
+      "apiVersion": "2023-03-01",
+      "name": "[format('vm{0}', uniqueString(resourceGroup().id))]",
+      "location": "[parameters('location')]",
+      "dependsOn": [
+        "myStorage"
+      ],
+      ...
+    }
+  }
+}
+```
+
 While you may be inclined to use `dependsOn` to map relationships between your resources, it's important to understand why you're doing it. For example, to document how resources are interconnected, `dependsOn` isn't the right approach. After deployment, the resource doesn't retain deployment dependencies in its properties, so there are no commands or operations that let you see dependencies. Setting unnecessary dependencies slows deployment time because Resource Manager can't deploy those resources in parallel.
 
 ## Child resources
@@ -204,7 +242,7 @@ The following example shows how to deploy three storage accounts before deployin
 }
 ```
 
-[Symbolic names](./resource-declaration.md#use-symbolic-name) can be used in `dependsOn`` arrays. If a symbolic name is for a copy loop, all resources in the loop are added as dependencies. The preceding sample can be written as the following JSON. In the sample, **myVM** depends on all of the storage accounts in the **myStorages** loop.
+[Symbolic names](./resource-declaration.md#use-symbolic-name) can be used in `dependsOn` arrays. If a symbolic name is for a copy loop, all resources in the loop are added as dependencies. The preceding sample can be written as the following JSON. In the sample, **myVM** depends on all of the storage accounts in the **myStorages** loop.
 
 ```json
 {