Merge pull request #307584 from mumian/1030-refresh-bicep

prmerger-automator[bot] · web-flow · commit 56aa6e3842d5 · 2025-10-31T17:50:00.000Z
Refresh Bicep content
diff --git a/articles/azure-resource-manager/bicep/linter-rule-prefer-unquoted-property-names.md b/articles/azure-resource-manager/bicep/linter-rule-prefer-unquoted-property-names.md
@@ -3,7 +3,7 @@ title: Linter rule - prefer unquoted property names
 description: Linter rule - prefer unquoted property names
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - prefer unquoted property names
@@ -14,13 +14,13 @@ In Bicep, quotes are optionally allowed when the object property keys contain nu
 
 ## Linter rule code
 
-Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:
+To customize rule settings, use the following value in the [Bicep configuration file](bicep-config-linter.md).
 
 `prefer-unquoted-property-names`
 
 ## Solution
 
-Quotes are not required in following code:
+Quotes aren't required in following code:
 
 ```bicep
 var obj = {
@@ -55,8 +55,6 @@ var x3 = obj.myProp
 
 Optionally, you can use **Quick Fix** to fix the issues:
 
-linter-rule-prefer-unquoted-property-names-quick-fix
-
 :::image type="content" source="./media/linter-rule-prefer-unquoted-property-names/linter-rule-prefer-unquoted-property-names-quick-fix.png" alt-text="The screenshot of Prefer unquoted property names quick fix.":::
 
 ## Next steps
diff --git a/articles/azure-resource-manager/bicep/linter-rule-protect-commandtoexecute-secrets.md b/articles/azure-resource-manager/bicep/linter-rule-protect-commandtoexecute-secrets.md
@@ -3,7 +3,7 @@ title: Linter rule - use protectedSettings for commandToExecute secrets
 description: Linter rule - use protectedSettings for commandToExecute secrets
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use protectedSettings for commandToExecute secrets
diff --git a/articles/azure-resource-manager/bicep/linter-rule-secure-parameter-default.md b/articles/azure-resource-manager/bicep/linter-rule-secure-parameter-default.md
@@ -3,7 +3,7 @@ title: Linter rule - secure parameter default
 description: Linter rule - secure parameter default
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - secure parameter default
diff --git a/articles/azure-resource-manager/bicep/linter-rule-secure-params-in-nested-deploy.md b/articles/azure-resource-manager/bicep/linter-rule-secure-params-in-nested-deploy.md
@@ -3,7 +3,7 @@ title: Linter rule - secure params in nested deploy
 description: Linter rule - secure params in nested deploy
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - secure params in nested deploy
diff --git a/articles/azure-resource-manager/bicep/linter-rule-secure-secrets-in-parameters.md b/articles/azure-resource-manager/bicep/linter-rule-secure-secrets-in-parameters.md
@@ -3,7 +3,7 @@ title: 'Linter rule: Secure secrets in parameters'
 description: This article describes the linter rule, secure secrets in parameters.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule: Secure secrets in parameters
diff --git a/articles/azure-resource-manager/bicep/linter-rule-simplify-interpolation.md b/articles/azure-resource-manager/bicep/linter-rule-simplify-interpolation.md
@@ -3,7 +3,7 @@ title: Linter rule - simplify interpolation
 description: Linter rule - simplify interpolation
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - simplify interpolation
diff --git a/articles/azure-resource-manager/bicep/linter-rule-simplify-json-null.md b/articles/azure-resource-manager/bicep/linter-rule-simplify-json-null.md
@@ -3,7 +3,7 @@ title: Linter rule - simplify JSON null
 description: Linter rule - simplify JSON null
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - simplify JSON null
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-parent-property.md b/articles/azure-resource-manager/bicep/linter-rule-use-parent-property.md
@@ -3,7 +3,7 @@ title: Linter rule - use parent property
 description: Linter rule - use parent property
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use parent property
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-recent-api-versions.md b/articles/azure-resource-manager/bicep/linter-rule-use-recent-api-versions.md
@@ -3,7 +3,7 @@ title: Linter rule - use recent API versions
 description: Linter rule - use recent API versions
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use recent API versions
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-recent-module-versions.md b/articles/azure-resource-manager/bicep/linter-rule-use-recent-module-versions.md
@@ -3,7 +3,7 @@ title: Linter rule - use recent module versions
 description: Linter rule - use recent module versions
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use recent module versions
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-resource-id-functions.md b/articles/azure-resource-manager/bicep/linter-rule-use-resource-id-functions.md
@@ -3,7 +3,7 @@ title: Linter rule - use resource ID functions
 description: Linter rule - use resource ID functions
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 04/23/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use resource ID functions
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-resource-symbol-reference.md b/articles/azure-resource-manager/bicep/linter-rule-use-resource-symbol-reference.md
@@ -3,7 +3,7 @@ title: Linter rule - use resource symbol reference
 description: Linter rule - use resource symbol reference
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use resource symbol reference
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-safe-access.md b/articles/azure-resource-manager/bicep/linter-rule-use-safe-access.md
@@ -3,7 +3,7 @@ title: Linter rule - Use the safe access (.?) operator
 description: Use the safe access (.?) operator instead of checking object contents with the 'contains' function.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use the safe access operator
@@ -104,4 +104,4 @@ var test = contains(foo, target) ? bar[notTarget] : 'baz'
 
 ## Next steps
 
-For more information about the linter, see [Use Bicep linter](./linter.md).
+For more information about the linter, see [Use Bicep linter](./linter.md).
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-secure-value-for-secure-inputs.md b/articles/azure-resource-manager/bicep/linter-rule-use-secure-value-for-secure-inputs.md
@@ -3,7 +3,7 @@ title: Linter rule - adminPassword should be assigned a secure value
 description: Linter rule - adminPassword should be assigned a secure value.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - adminPassword should be assigned a secure value.
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-stable-resource-identifier.md b/articles/azure-resource-manager/bicep/linter-rule-use-stable-resource-identifier.md
@@ -3,7 +3,7 @@ title: Linter rule - use stable resource identifier
 description: Linter rule - use stable resource identifier
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use stable resource identifier
diff --git a/articles/azure-resource-manager/bicep/linter-rule-use-stable-vm-image.md b/articles/azure-resource-manager/bicep/linter-rule-use-stable-vm-image.md
@@ -3,7 +3,7 @@ title: Linter rule - use stable VM image
 description: Linter rule - use stable VM image
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Linter rule - use stable VM image
@@ -16,7 +16,7 @@ Virtual machines shouldn't use preview images. This rule checks the following pr
 
 ## Linter rule code
 
-Use the following value in the [Bicep configuration file](bicep-config-linter.md) to customize rule settings:
+To customize rule settings, use the following value in the [Bicep configuration file](bicep-config-linter.md)
 
 `use-stable-vm-image`
 
@@ -42,7 +42,7 @@ resource vm 'Microsoft.Compute/virtualMachines@2024-03-01' = {
 }
 ```
 
-You can fix it by using an image that does not contain the string `preview` in the imageReference.
+You can fix it by using an image that doesn't contain the string `preview` in the imageReference.
 
 ```bicep
 param location string = resourceGroup().location
diff --git a/articles/azure-resource-manager/bicep/loops.md b/articles/azure-resource-manager/bicep/loops.md
@@ -5,7 +5,7 @@ ms.topic: conceptual
 ms.custom:
   - devx-track-bicep
   - build-2025
-ms.date: 03/25/2025
+ms.date: 10/30/2025
 ---
 
 # Iterative loops in Bicep
diff --git a/articles/azure-resource-manager/bicep/migrate.md b/articles/azure-resource-manager/bicep/migrate.md
@@ -2,7 +2,7 @@
 title: Migrate Azure resources and JSON ARM templates to use Bicep
 description: Learn the recommended workflow when migrating Azure resources and JSON ARM templates to use Bicep.
 ms.topic: conceptual
-ms.date: 04/09/2025
+ms.date: 10/30/2025
 ms.custom:
   - devx-track-bicep
   - build-2025
diff --git a/articles/azure-resource-manager/bicep/msbuild-bicep-file.md b/articles/azure-resource-manager/bicep/msbuild-bicep-file.md
@@ -2,7 +2,7 @@
 title: 'Quickstart: Use MSBuild tasks to convert Bicep files and parameters to JSON' 
 description: Learn how to use MSBuild to convert Bicep files to JSON Azure Resource Manager templates.
 ms.topic: quickstart
-ms.date: 01/10/2025
+ms.date: 10/30/2025
 ms.custom: devx-track-bicep, devx-track-arm-template
 #customer intent: As a developer, I want to follow a MSBuild continuous integration pipeline to convert Bicep files to JSON Azure Resource Manager templates (ARM templates).
 ---
diff --git a/articles/azure-resource-manager/bicep/operator-null-forgiving.md b/articles/azure-resource-manager/bicep/operator-null-forgiving.md
@@ -3,7 +3,7 @@ title: Bicep null-forgiving operator
 description: Describes Bicep null-forgiving operator.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Bicep null-forgiving operator
diff --git a/articles/azure-resource-manager/bicep/operator-safe-dereference.md b/articles/azure-resource-manager/bicep/operator-safe-dereference.md
@@ -3,7 +3,7 @@ title: Bicep safe-dereference operator
 description: Describes Bicep safe-dereference operator.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Bicep safe-dereference operator
diff --git a/articles/azure-resource-manager/bicep/operator-spread.md b/articles/azure-resource-manager/bicep/operator-spread.md
@@ -3,7 +3,7 @@ title: Bicep spread operator
 description: Describes Bicep spread operator.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Bicep spread operator
diff --git a/articles/azure-resource-manager/bicep/operators-comparison.md b/articles/azure-resource-manager/bicep/operators-comparison.md
@@ -3,7 +3,7 @@ title: Bicep comparison operators
 description: Describes Bicep comparison operators that compare values.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Bicep comparison operators
diff --git a/articles/azure-resource-manager/bicep/operators-logical.md b/articles/azure-resource-manager/bicep/operators-logical.md
@@ -3,7 +3,7 @@ title: Bicep logical operators
 description: Describes Bicep logical operators that evaluate conditions.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/21/2025
+ms.date: 10/30/2025
 ---
 
 # Bicep logical operators
diff --git a/articles/azure-resource-manager/bicep/operators-numeric.md b/articles/azure-resource-manager/bicep/operators-numeric.md
@@ -3,7 +3,7 @@ title: Bicep numeric operators
 description: Describes Bicep numeric operators that calculate values.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 10/30/2025
 ---
 
 # Bicep numeric operators
diff --git a/articles/azure-resource-manager/bicep/private-module-registry.md b/articles/azure-resource-manager/bicep/private-module-registry.md
@@ -2,7 +2,7 @@
 title: Create a private container registry in Azure for Bicep modules
 description: Learn how to set up a private container registry in Azure for private Bicep modules.
 ms.topic: how-to
-ms.date: 01/10/2025
+ms.date: 10/30/2025
 ms.custom: devx-track-bicep
 ---
 
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md b/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md
@@ -2,7 +2,7 @@
 title: 'Quickstart: Create Bicep files with Visual Studio Code'
 description: Learn how to use Visual Studio Code and the Bicep extension to create Bicep files and deploy Azure resources.
 ms.topic: quickstart
-ms.date: 03/25/2025
+ms.date: 10/30/2025
 ms.custom:
   - mode-ui
   - devx-track-bicep
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md b/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md
@@ -1,37 +1,37 @@
 ---
 title: Create Bicep files - Visual Studio
 description: Use Visual Studio and the Bicep extension to create Bicep files for deploy Azure resources.
-ms.date: 03/17/2025
+ms.date: 10/30/2025
 ms.topic: quickstart
 ms.custom: devx-track-bicep
 #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio to create and edit Bicep files, so I can use them to deploy Azure resources.
 ---
 
 # Quickstart: Create Bicep files with Visual Studio
 
-This quickstart guides you through the steps to create a [Bicep file](overview.md) with Visual Studio. You'll create a storage account and a virtual network. You'll also learn how the Bicep extension simplifies development by providing type safety, syntax validation, and autocompletion.
+This quickstart guides you through the steps to create a [Bicep file](overview.md) with Visual Studio. You create a storage account and a virtual network. You also learn how the Bicep extension simplifies development by providing type safety, syntax validation, and autocompletion.
 
-Similar authoring experience is also supported in Visual Studio Code.  See [Quickstart: Create Bicep files with Visual Studio Code](./quickstart-create-bicep-use-visual-studio-code.md).
+Similar authoring experience is also supported in Visual Studio Code. See [Quickstart: Create Bicep files with Visual Studio Code](./quickstart-create-bicep-use-visual-studio-code.md).
 
 ## Prerequisites
 
 - Azure Subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn) before you begin.
-- Visual Studio version 17.3.0 preview 3 or newer.  See [Visual Studio Preview](https://visualstudio.microsoft.com/vs/preview/).
-- Visual Studio Bicep extension.  See [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
+- Visual Studio version 17.3.0 preview 3 or newer. See [Visual Studio Preview](https://visualstudio.microsoft.com/vs/preview/).
+- Visual Studio Bicep extension. See [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
 - Bicep file deployment requires either the latest [Azure CLI](/cli/azure/) or the latest [Azure PowerShell module](/powershell/azure/new-azureps-module-az).
 
 ## Add resource snippet
 
 Launch Visual Studio and create a new file named **main.bicep**.
 
-Visual Studio with the Bicep extension simplifies development by providing pre-defined snippets. In this quickstart, you'll add a snippet that creates a virtual network.
+Visual Studio with the Bicep extension simplifies development by providing predefined snippets. In this quickstart, you add a snippet that creates a virtual network.
 
 In *main.bicep*, type **vnet**. Select **res-vnet** from the list, and then press **[TAB]** or **[ENTER]**.
 
 :::image type="content" source="./media/quickstart-create-bicep-use-visual-studio/add-snippet.png" alt-text="Screenshot of adding snippet for virtual network.":::
 
 > [!TIP]
-> If you don't see those intellisense options in Visual Studio, make sure you've installed the Bicep extension as specified in [Prerequisites](#prerequisites). If you have installed the extension, give the Bicep language service some time to start after opening your Bicep file. It usually starts quickly, but you will not have intellisense options until it starts.
+> If you don't see those intellisense options in Visual Studio, make sure you've installed the Bicep extension as specified in [Prerequisites](#prerequisites). If you have installed the extension, give the Bicep language service some time to start after opening your Bicep file. It usually starts quickly, but you won't have intellisense options until it starts.
 
 Your Bicep file now contains the following code:
 
@@ -73,7 +73,7 @@ Notice **location** has a red curly underline. This indicates a problem. Hover y
 
 ## Add parameters
 
-Now, we'll add two parameters for the storage account name and the location. At the top of file, add:
+Now, we add two parameters for the storage account name and the location. At the top of file, add:
 
 ```bicep
 param storageName
@@ -89,7 +89,7 @@ You have the following parameter:
 param storageName string
 ```
 
-This parameter works fine, but storage accounts have limits on the length of the name. The name must have at least 3 characters and no more than 24 characters. You can specify those requirements by adding decorators to the parameter.
+This parameter works fine, but storage accounts have limits on the length of the name. The name must have at least three characters and no more than 24 characters. You can specify those requirements by adding decorators to the parameter.
 
 Add a line above the parameter, and type **@**. You see the available decorators. Notice there are decorators for both **minLength** and **maxLength**.
 
@@ -122,9 +122,9 @@ param location string = resourceGroup().location
 
 ## Add resource
 
-Instead of using a snippet to define the storage account, we'll use intellisense to set the values. Intellisense makes this step much easier than having to manually type the values.
+Instead of using a snippet to define the storage account, we use intellisense to set the values. Intellisense makes this step easier than having to manually type the values.
 
-To define a resource, use the `resource` keyword.  Below your virtual network, type **resource exampleStorage**:
+To define a resource, use the `resource` keyword. Below your virtual network, type **resource exampleStorage**:
 
 ```bicep
 resource exampleStorage
@@ -208,7 +208,7 @@ For more information about the Bicep syntax, see [Bicep structure](./file.md).
 
 ## Deploy the Bicep file
 
-Bicep file deployment can't be done from Visual Studio yet.  You can deploy the Bicep file by using Azure CLI or Azure PowerShell:
+Bicep file deployment can't be done from Visual Studio yet. You can deploy the Bicep file by using Azure CLI or Azure PowerShell:
 
 # [CLI](#tab/CLI)
 
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks-template-specs.md b/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks-template-specs.md
@@ -1,7 +1,7 @@
 ---
 title: Create and deploy a deployment stack with Bicep from template specs
 description: Learn how to use Bicep to create and deploy a deployment stack from template specs.
-ms.date: 03/17/2025
+ms.date: 10/30/2025
 ms.topic: quickstart
 ms.custom: mode-api, devx-track-azurecli, devx-track-azurepowershell, devx-track-bicep
 # Customer intent: As a developer I want to use Bicep to create a deployment stack from a template spec.
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks.md b/articles/azure-resource-manager/bicep/quickstart-create-deployment-stacks.md
@@ -1,7 +1,7 @@
 ---
 title: Create and deploy a deployment stack with Bicep
 description: Learn how to use Bicep to create and deploy a deployment stack in your Azure subscription.
-ms.date: 01/15/2025
+ms.date: 10/30/2025
 ms.topic: quickstart
 ms.custom: mode-api, devx-track-azurecli, devx-track-azurepowershell, devx-track-bicep
 # Customer intent: As a developer I want to use Bicep to create a deployment stack.
diff --git a/articles/azure-resource-manager/bicep/resource-dependencies.md b/articles/azure-resource-manager/bicep/resource-dependencies.md
diff --git a/articles/azure-resource-manager/bicep/scenarios-rbac.md b/articles/azure-resource-manager/bicep/scenarios-rbac.md
diff --git a/articles/azure-resource-manager/bicep/scenarios-secrets.md b/articles/azure-resource-manager/bicep/scenarios-secrets.md
diff --git a/articles/azure-resource-manager/bicep/scope-extension-resources.md b/articles/azure-resource-manager/bicep/scope-extension-resources.md
diff --git a/articles/azure-resource-manager/bicep/template-specs.md b/articles/azure-resource-manager/bicep/template-specs.md
diff --git a/articles/azure-resource-manager/bicep/visual-studio-code.md b/articles/azure-resource-manager/bicep/visual-studio-code.md
