Merge pull request #287440 from mumian/0926-arm-freshness

denrea · web-flow · commit 6cad7901b183 · 2024-09-26T15:52:20.000-07:00
refresh ARM template content
diff --git a/articles/azure-resource-manager/templates/best-practices.md b/articles/azure-resource-manager/templates/best-practices.md
@@ -3,7 +3,7 @@ title: Best practices for templates
 description: Describes recommended approaches for authoring Azure Resource Manager templates (ARM templates). Offers suggestions to avoid common problems when using templates.
 ms.topic: best-practice
 ms.custom: devx-track-arm-template
-ms.date: 09/25/2024
+ms.date: 09/26/2024
 ---
 # ARM template best practices
 
@@ -206,7 +206,7 @@ The following information can be helpful when you work with [resources](./syntax
     ]
     ```
 
-   For more details about comments and metadata see [Understand the structure and syntax of ARM templates](./syntax.md#comments-and-metadata).
+   For more details about comments and metadata, see [Understand the structure and syntax of ARM templates](./syntax.md#comments-and-metadata).
 
 * If you use a *public endpoint* in your template (such as an Azure Blob storage public endpoint), *don't hard-code* the namespace. Use the `reference` function to dynamically retrieve the namespace. You can use this approach to deploy the template to different public namespace environments without manually changing the endpoint in the template. Set the API version to the same version that you're using for the storage account in your template.
 
@@ -293,11 +293,11 @@ The following information can be helpful when you work with [resources](./syntax
 
 ## Comments
 
-In addition to the `comments` property, comments using the `//` syntax are supported.  For more details about comments and metadata see [Understand the structure and syntax of ARM templates](./syntax.md#comments-and-metadata). You may choose to save JSON files that contain `//` comments using the `.jsonc` file extension, to indicate the JSON file contains comments. The ARM service will also accept comments in any JSON file including parameters files.
+In addition to the `comments` property, comments using the `//` syntax are supported.  For more details about comments and metadata, see [Understand the structure and syntax of ARM templates](./syntax.md#comments-and-metadata). You may choose to save JSON files that contain `//` comments using the `.jsonc` file extension, to indicate the JSON file contains comments. The ARM service will also accept comments in any JSON file including parameters files.
 
 ## Visual Studio Code ARM Tools
 
-Working with ARM templates is much easier with the Azure Resource Manager (ARM) Tools for Visual Studio Code. This extension provides language support, resource snippets, and resource auto-completion to help you create and validate Azure Resource Manager templates. To learn more and install the extension, see [Azure Resource Manager (ARM) Tools](https://marketplace.visualstudio.com/items?itemName=msazurermtools.azurerm-vscode-tools).
+Working with ARM templates is easier with the Azure Resource Manager (ARM) Tools for Visual Studio Code. This extension provides language support, resource snippets, and resource auto-completion to help you create and validate Azure Resource Manager templates. To learn more and install the extension, see [Azure Resource Manager (ARM) Tools](https://marketplace.visualstudio.com/items?itemName=msazurermtools.azurerm-vscode-tools).
 
 ## Use test toolkit
 
diff --git a/articles/azure-resource-manager/templates/copy-resources.md b/articles/azure-resource-manager/templates/copy-resources.md
@@ -3,7 +3,7 @@ title: Deploy multiple instances of resources
 description: Use copy operation and arrays in an Azure Resource Manager template (ARM template) to deploy resource type many times.
 ms.topic: how-to
 ms.custom: devx-track-arm-template
-ms.date: 08/30/2023
+ms.date: 09/26/2024
 ---
 
 # Resource iteration in ARM templates
@@ -14,7 +14,6 @@ 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).
 
diff --git a/articles/azure-resource-manager/templates/definitions.md b/articles/azure-resource-manager/templates/definitions.md
@@ -3,7 +3,7 @@ title: Type definitions in templates
 description: Describes how to create type definitions in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 08/22/2023
+ms.date: 09/26/2024
 ---
 
 # Type definitions in ARM templates
@@ -348,7 +348,6 @@ If the value is true, elements of the array whose index is greater than the larg
 
 The nullable constraint indicates that the value may be `null` or omitted. See [Properties](#properties) for an example.
 
-
 ## Description
 
 You can add a description to a type definition to help users of your template understand the value to provide.
diff --git a/articles/azure-resource-manager/templates/deploy-cli.md b/articles/azure-resource-manager/templates/deploy-cli.md
@@ -2,7 +2,7 @@
 title: Azure deployment templates with Azure CLI – Azure Resource Manager | Microsoft Docs
 description: Use Azure Resource Manager and Azure CLI to create and deploy resource groups to Azure. The resources are defined in an Azure deployment template.
 ms.topic: how-to
-ms.date: 10/10/2023
+ms.date: 09/26/2024
 ms.custom: devx-track-azurecli, seo-azure-cli, devx-track-arm-template
 keywords: azure cli deploy arm template, create resource group azure, azure deployment template, deployment resources, arm template, azure arm template
 ---
diff --git a/articles/azure-resource-manager/templates/deploy-github-actions.md b/articles/azure-resource-manager/templates/deploy-github-actions.md
@@ -2,7 +2,7 @@
 title: Deploy Resource Manager templates by using GitHub Actions
 description: Describes how to deploy Azure Resource Manager templates (ARM templates) by using GitHub Actions.
 ms.topic: how-to
-ms.date: 06/23/2023
+ms.date: 09/26/2024
 ms.custom: github-actions-azure, devx-track-arm-template
 ---
 
@@ -46,7 +46,7 @@ Add a Resource Manager template to your GitHub repository. This template creates
 https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.storage/storage-account-create/azuredeploy.json
 ```
 
-You can put the file anywhere in the repository. The workflow sample in the next section assumes the template file is named **azuredeploy.json**, and it is stored at the root of your repository.
+You can put the file anywhere in the repository. The workflow sample in the next section assumes the template file is named **azuredeploy.json**, and it's stored at the root of your repository.
 
 ## Create workflow
 
@@ -94,7 +94,7 @@ The workflow file must be stored in the **.github/workflows** folder at the root
   The first section of the workflow file includes:
 
   - **name**: The name of the workflow.
-  - **on**: The name of the GitHub events that triggers the workflow. The workflow is trigger when there is a push event on the main branch, which modifies at least one of the two files specified. The two files are the workflow file and the template file.
+  - **on**: The name of the GitHub events that triggers the workflow. The workflow is trigger when there's a push event on the main branch, which modifies at least one of the two files specified. The two files are the workflow file and the template file.
 
   # [OpenID Connect](#tab/openid)
 
@@ -135,7 +135,7 @@ The workflow file must be stored in the **.github/workflows** folder at the root
   The first section of the workflow file includes:
 
   - **name**: The name of the workflow.
-  - **on**: The name of the GitHub events that triggers the workflow. The workflow is trigger when there is a push event on the main branch, which modifies at least one of the two files specified. The two files are the workflow file and the template file.
+  - **on**: The name of the GitHub events that triggers the workflow. The workflow is trigger when there's a push event on the main branch, which modifies at least one of the two files specified. The two files are the workflow file and the template file.
   ---
 
 1. Select **Start commit**.
@@ -146,7 +146,7 @@ Because the workflow is configured to be triggered by either the workflow file o
 
 ## Check workflow status
 
-1. Select the **Actions** tab. You will see a **Create deployStorageAccount.yml** workflow listed. It takes 1-2 minutes to run the workflow.
+1. Select the **Actions** tab. You see a **Create deployStorageAccount.yml** workflow listed. It takes 1-2 minutes to run the workflow.
 1. Select the workflow to open it.
 1. Select **Run ARM deploy** from the menu to verify the deployment.
 
diff --git a/articles/azure-resource-manager/templates/deployment-tutorial-linked-template.md b/articles/azure-resource-manager/templates/deployment-tutorial-linked-template.md
@@ -1,7 +1,7 @@
 ---
 title: Tutorial - Deploy a linked template
 description: Learn how to deploy a linked template
-ms.date: 10/05/2023
+ms.date: 09/26/2024
 ms.topic: tutorial
 ms.custom: devx-track-azurepowershell
 ---
@@ -26,7 +26,7 @@ You can separate the storage account resource into a linked template:
 
 :::code language="json" source="~/resourcemanager-templates/get-started-deployment/linked-template/linkedStorageAccount.json":::
 
-The following template is the main template. The highlighted `Microsoft.Resources/deployments` object shows how to call a linked template. The linked template cannot be stored as a local file or a file that is only available on your local network. You can either provide a URI value of the linked template that includes either HTTP or HTTPS,  or use the _relativePath_ property to deploy a remote linked template at a location relative to the parent template. One option is to place both the main template and the linked template in a storage account.
+The following template is the main template. The highlighted `Microsoft.Resources/deployments` object shows how to call a linked template. The linked template can't be stored as a local file or a file that is only available on your local network. You can either provide a URI value of the linked template that includes either HTTP or HTTPS,  or use the _relativePath_ property to deploy a remote linked template at a location relative to the parent template. One option is to place both the main template and the linked template in a storage account.
 
 :::code language="json" source="~/resourcemanager-templates/get-started-deployment/linked-template/azuredeploy.json" highlight="34-52":::
 
@@ -95,7 +95,7 @@ Write-Host "Press [ENTER] to continue ..."
 
 ## Deploy template
 
-To deploy templates in a storage account, generate a SAS token and supply it to the _-QueryString_ parameter. Set the expiry time to allow enough time to complete the deployment. The blobs containing the templates are accessible to only the account owner. However, when you create a SAS token for a blob, the blob is accessible to anyone with that SAS token. If another user intercepts the URI and the SAS token, that user is able to access the template. A SAS token is a good way of limiting access to your templates, but you should not include sensitive data like passwords directly in the template.
+To deploy templates in a storage account, generate a SAS token and supply it to the _-QueryString_ parameter. Set the expiry time to allow enough time to complete the deployment. The blobs containing the templates are accessible to only the account owner. However, when you create a SAS token for a blob, the blob is accessible to anyone with that SAS token. If another user intercepts the URI and the SAS token, that user is able to access the template. A SAS token is a good way of limiting access to your templates, but you shouldn't include sensitive data like passwords directly in the template.
 
 If you haven't created the resource group, see [Create resource group](./deployment-tutorial-local-template.md#create-resource-group).
 
diff --git a/articles/azure-resource-manager/templates/deployment-tutorial-local-template.md b/articles/azure-resource-manager/templates/deployment-tutorial-local-template.md
@@ -1,7 +1,7 @@
 ---
 title: Tutorial - Deploy a local Azure Resource Manager template
 description: Learn how to deploy an Azure Resource Manager template (ARM template) from your local computer
-ms.date: 10/05/2023
+ms.date: 09/26/2024
 ms.topic: tutorial
 ms.custom: devx-track-arm-template
 ---
diff --git a/articles/azure-resource-manager/templates/deployment-tutorial-pipeline.md b/articles/azure-resource-manager/templates/deployment-tutorial-pipeline.md
@@ -1,7 +1,7 @@
 ---
 title: Continuous integration with Azure Pipelines
 description: Learn how to continuously build, test, and deploy Azure Resource Manager templates (ARM templates).
-ms.date: 06/20/2024
+ms.date: 09/26/2024
 ms.topic: tutorial
 ms.custom: devx-track-arm-template
 ---
diff --git a/articles/azure-resource-manager/templates/linked-templates.md b/articles/azure-resource-manager/templates/linked-templates.md
@@ -2,7 +2,7 @@
 title: Link templates for deployment
 description: Describes how to use linked templates in an Azure Resource Manager template (ARM template) to create a modular template solution. Shows how to pass parameters values, specify a parameter file, and dynamically created URLs.
 ms.topic: conceptual
-ms.date: 08/22/2023
+ms.date: 09/26/2024
 ms.custom: devx-track-azurepowershell, devx-track-arm-template
 ---
 
@@ -94,7 +94,7 @@ The following example deploys a storage account through a nested template.
 }
 ```
 
-[Nested resources](./child-resource-name-type.md#within-parent-resource) can't be used in a [symbolic name](./resource-declaration.md#use-symbolic-name) template. In the following template, the nested storage account resource cannot use symbolic name:
+[Nested resources](./child-resource-name-type.md#within-parent-resource) can't be used in a [symbolic name](./resource-declaration.md#use-symbolic-name) template. In the following template, the nested storage account resource can't use symbolic name:
 
 ```json
 {
@@ -643,7 +643,7 @@ az deployment group create \
 
 ---
 
-Make sure there is no leading "?" in QueryString. The deployment adds one when assembling the URI for the deployments.
+Make sure there's no leading "?" in QueryString. The deployment adds one when assembling the URI for the deployments.
 
 ## Template specs
 
diff --git a/articles/azure-resource-manager/templates/parameter-file-test-cases.md b/articles/azure-resource-manager/templates/parameter-file-test-cases.md
@@ -3,7 +3,7 @@ title: Parameter file test cases for Azure Resource Manager test toolkit
 description: Describes the parameter file tests that are run by the Azure Resource Manager template test toolkit.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 06/23/2023
+ms.date: 09/26/2024
 ---
 
 # Test cases for parameter files
diff --git a/articles/azure-resource-manager/templates/parameters.md b/articles/azure-resource-manager/templates/parameters.md
@@ -3,7 +3,7 @@ title: Parameters in templates
 description: Describes how to define parameters in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 08/22/2023
+ms.date: 09/26/2024
 ---
 
 # Parameters in ARM templates
@@ -28,7 +28,7 @@ In addition to minValue, maxValue, minLength, maxLength, and allowedValues, [lan
 > [!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).
+You're 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).
 
@@ -421,7 +421,6 @@ If the value is true, elements of the array whose index is greater than the larg
 }
 ```
 
-
 ## nullable constraint
 
 The nullable constraint can only be used with [languageVersion 2.0](./syntax.md#languageversion-20). It indicates that the value may be `null` or omitted. See [Properties](#properties) for an example.
@@ -545,6 +544,6 @@ The following examples demonstrate scenarios for using parameters.
 
 ## Next steps
 
-* To learn about the available properties for parameters, see [Understand the structure and syntax of ARM templates](./syntax.md).
-* To learn about passing in parameter values as a file, see [Create Resource Manager parameter file](parameter-files.md).
-* For recommendations about creating parameters, see [Best practices - parameters](./best-practices.md#parameters).
+- To learn about the available properties for parameters, see [Understand the structure and syntax of ARM templates](./syntax.md).
+- To learn about passing in parameter values as a file, see [Create Resource Manager parameter file](parameter-files.md).
+- For recommendations about creating parameters, see [Best practices - parameters](./best-practices.md#parameters).
diff --git a/articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md b/articles/azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md
@@ -1,7 +1,7 @@
 ---
 title: Create template - Visual Studio Code
 description: Use Visual Studio Code and the Azure Resource Manager tools extension to work on Azure Resource Manager templates (ARM templates).
-ms.date: 07/28/2023
+ms.date: 09/26/2024
 ms.topic: quickstart
 ms.custom: mode-ui, devx-track-arm-template
 #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio Code to create and edit Resource Manager templates, so I can use the templates to deploy Azure resources.
@@ -78,7 +78,7 @@ Update the name of the parameter to `storageAccountName` and the description to
 
 :::image type="content" source="./media/quickstart-create-templates-use-visual-studio-code/10.png" alt-text="Screenshot showing the completed parameter in an ARM template.":::
 
-Azure storage account names have a minimum length of 3 characters and a maximum of 24. Add both `minLength` and `maxLength` to the parameter and provide appropriate values.
+Azure storage account names have a minimum length of three characters and a maximum of 24. Add both `minLength` and `maxLength` to the parameter and provide appropriate values.
 
 :::image type="content" source="./media/quickstart-create-templates-use-visual-studio-code/11.png" alt-text="Screenshot showing minLength and maxLength being added to an ARM template parameter.":::
 
@@ -133,6 +133,7 @@ New-AzResourceGroup -Name arm-vscode -Location eastus
 
 New-AzResourceGroupDeployment -ResourceGroupName arm-vscode -TemplateFile ./azuredeploy.json -TemplateParameterFile ./azuredeploy.parameters.json
 ```
+
 ---
 
 ## Clean up resources
@@ -150,6 +151,7 @@ az group delete --name arm-vscode
 ```azurepowershell
 Remove-AzResourceGroup -Name arm-vscode
 ```
+
 ---
 
 ## Next steps
diff --git a/articles/azure-resource-manager/templates/resource-dependency.md b/articles/azure-resource-manager/templates/resource-dependency.md
@@ -2,7 +2,7 @@
 title: Set deployment order for resources
 description: Describes how to set one Azure resource as dependent on another resource during deployment. The dependencies ensure resources are deployed in the correct order.
 ms.topic: conceptual
-ms.date: 08/22/2023
+ms.date: 09/26/2024
 ---
 
 # Define the order for deploying resources in ARM templates
@@ -18,7 +18,7 @@ Azure Resource Manager evaluates the dependencies between resources, and deploys
 
 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.
 
-The following example shows a network interface that depends on a virtual network, network security group, and public IP address. For the full template, see [the quickstart template for a Linux VM](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.compute/vm-simple-linux/azuredeploy.json).
+The following example shows a network interface that depends on a virtual network, network security group, and public IP address. For the full template, see [the quickstart template for a Linux virtual machine](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.compute/vm-simple-linux/azuredeploy.json).
 
 ```json
 {
diff --git a/articles/azure-resource-manager/templates/resource-extensions.md b/articles/azure-resource-manager/templates/resource-extensions.md
@@ -3,7 +3,7 @@ title: Post-deployment configuration with extensions
 description: Learn how to use Azure Resource Manager template (ARM template) extensions for post-deployment configurations.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 06/23/2023
+ms.date: 09/26/2024
 ---
 
 # Post-deployment configurations by using extensions
diff --git a/articles/azure-resource-manager/templates/scope-functions.md b/articles/azure-resource-manager/templates/scope-functions.md
@@ -3,7 +3,7 @@ title: Template functions in scoped deployments
 description: Describes how template functions are resolved in scoped deployments. The scope can be a tenant, management groups, subscriptions, and resource groups.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 06/23/2023
+ms.date: 09/26/2024
 ---
 
 # ARM template functions in deployment scopes
diff --git a/articles/azure-resource-manager/templates/syntax.md b/articles/azure-resource-manager/templates/syntax.md
diff --git a/articles/azure-resource-manager/templates/template-expressions.md b/articles/azure-resource-manager/templates/template-expressions.md
diff --git a/articles/azure-resource-manager/templates/update-visual-studio-deployment-script.md b/articles/azure-resource-manager/templates/update-visual-studio-deployment-script.md
