updates1

Author: LiSeda

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

@@ -2,7 +2,7 @@
 title: Deploy resources with Azure CLI and Bicep files | Microsoft Docs
 description: Use Azure Resource Manager and Azure CLI to deploy resources to Azure. The resources are defined in a Bicep file.
 ms.topic: how-to
-ms.date: 03/22/2024
+ms.date: 12/06/2024
 ms.custom: devx-track-azurecli, seo-azure-cli, devx-track-arm-template, devx-track-bicep
 ---
 
@@ -174,11 +174,11 @@ However, if you're using Azure CLI with Windows Command Prompt (CMD) or PowerShe
 
 The evaluation of parameters follows a sequential order, meaning that if a value is assigned multiple times, only the last assigned value is used. To ensure proper parameter assignment, it's advised to provide your parameters file initially and selectively override specific parameters using the _KEY=VALUE_ syntax. It's important to mention that if you're supplying a `bicepparam` parameters file, you can use this argument only once.
 
-### Bicep parameter files
+### Bicep parameters files
 
 Rather than passing parameters as inline values in your script, you might find it easier to use a parameters file, either a [Bicep parameters file](#bicep-parameter-files) or a [JSON parameters file](#json-parameter-files) that contains the parameter values. The parameters file must be a local file. External parameters files aren't supported with Azure CLI. For more information about the parameters file, see [Create Resource Manager parameters file](./parameter-files.md).
 
-With Azure CLI version 2.53.0 or later, and [Bicep CLI version 0.22.X or higher](./install.md), you can deploy a Bicep file by utilizing a Bicep parameter file. With the `using` statement within the Bicep parameters file, there's no need to provide the `--template-file` switch when specifying a Bicep parameter file for the `--parameters` switch. Including the `--template-file` switch will result in an "Only a .bicep template is allowed with a .bicepparam file" error.
+With Azure CLI version 2.53.0 or later, and [Bicep CLI version 0.22.X or higher](./install.md), you can deploy a Bicep file by utilizing a Bicep parameters file. With the `using` statement within the Bicep parameters file, there's no need to provide the `--template-file` switch when specifying a Bicep parameters file for the `--parameters` switch. Including the `--template-file` switch will result in an "Only a .bicep template is allowed with a .bicepparam file" error.
 
 The following example shows a parameters file named _storage.bicepparam_. The file is in the same directory where the command is run.
 
@@ -189,7 +189,7 @@ az deployment group create \
   --parameters storage.bicepparam
 ```
 
-### JSON parameter files
+### JSON parameters files
 
 The following example shows a parameters file named _storage.parameters.json_. The file is in the same directory where the command is run.
 

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

@@ -3,7 +3,7 @@ title: Deploy resources with PowerShell and Bicep
 description: Use Azure Resource Manager and Azure PowerShell to deploy resources to Azure. The resources are defined in a Bicep file.
 ms.topic: how-to
 ms.custom: devx-track-arm-template, devx-track-bicep, devx-track-azurepowershell
-ms.date: 06/14/2024
+ms.date: 12/06/2024
 ---
 
 # Deploy resources with Bicep and Azure PowerShell
@@ -137,11 +137,11 @@ New-AzResourceGroupDeployment -ResourceGroupName testgroup `
   -exampleArray $subnetArray
 ```
 
-### Bicep parameter files
+### Bicep parameters files
 
 Rather than passing parameters as inline values in your script, you might find it easier to use a parameters file, either a `.bicepparam` file or a JSON parameters file, that contains the parameter values. The Bicep parameters file must be a local file.
 
-With Azure PowerShell version 10.4.0 or later, and [Bicep CLI version 0.22.X or higher](./install.md), you can deploy a Bicep file by utilizing a Bicep parameter file. With the `using` statement within the Bicep parameters file, there is no need to provide the `-TemplateFile` switch when specifying a Bicep parameter file for the `-TemplateParameterFile` switch.
+With Azure PowerShell version 10.4.0 or later, and [Bicep CLI version 0.22.X or higher](./install.md), you can deploy a Bicep file by utilizing a Bicep parameters file. With the `using` statement within the Bicep parameters file, there is no need to provide the `-TemplateFile` switch when specifying a Bicep parameters file for the `-TemplateParameterFile` switch.
 
 The following example shows a parameters file named _storage.bicepparam_. The file is in the same directory where the command is run.
 

articles/azure-resource-manager/bicep/deploy-vscode.md

@@ -3,7 +3,7 @@ title: Deploy Bicep files with Visual Studio Code
 description: Deploy Bicep files from Visual Studio Code.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 12/03/2024
+ms.date: 12/06/2024
 ---
 
 # Deploy Bicep files from Visual Studio Code
@@ -32,19 +32,19 @@ After you select the command, you follow the wizard to enter the values:
 
 1. Select or create a resource group.
 
-1. Select a parameter file or select **None** to enter the parameter values.
+1. Select a parameters file or select **None** to enter the parameter values.
 
-    :::image type="content" source="./media/deploy-vscode/bicep-deploy-select-parameter-file.png" alt-text="Screenshot of Select parameter file.":::
+    :::image type="content" source="./media/deploy-vscode/bicep-deploy-select-parameter-file.png" alt-text="Screenshot of Select parameters file.":::
 
 1. If you choose **None**, enter the parameter values.
 
     :::image type="content" source="./media/deploy-vscode/bicep-deploy-enter-parameter-values.png" alt-text="Screenshot of Enter parameter values.":::
 
     After you enter the values, you have the option to create a parameters file from values used in this deployment:
 
-    :::image type="content" source="./media/deploy-vscode/bicep-deploy-create-parameter-file.png" alt-text="Screenshot of Create parameter file.":::
+    :::image type="content" source="./media/deploy-vscode/bicep-deploy-create-parameter-file.png" alt-text="Screenshot of Create parameters file.":::
 
-    If you select **Yes**, a parameter file with the file name **<Bicep-file-name>.parameters.json** is created in the same folder.
+    If you select **Yes**, a parameters file with the file name **<Bicep-file-name>.parameters.json** is created in the same folder.
 
 For more information about VS Code commands, see [Visual Studio Code](./visual-studio-code.md).
 

articles/azure-resource-manager/bicep/diagnostics/bcp338.md

@@ -3,12 +3,12 @@ title: BCP338
 description: Failed to evaluate parameter <parameter-name>.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 08/09/2024
+ms.date: 12/06/2024
 ---
 
 # Bicep diagnostic code - BCP338
 
-This diagnostic occurs when Bicep can't resolve a parameter name in the Bicep parameter file.
+This diagnostic occurs when Bicep can't resolve a parameter name in the Bicep parameters file.
 
 ## Description
 
@@ -24,7 +24,7 @@ Check the parameter value.
 
 ## Examples
 
-The following Bicep parameter file raises the diagnostic because _testEnvironmentVariable_ can't be found:
+The following Bicep parameters file raises the diagnostic because _testEnvironmentVariable_ can't be found:
 
 ```bicep
 using 'main.bicep'

articles/azure-resource-manager/bicep/key-vault-parameter.md

@@ -3,7 +3,7 @@ title: Key Vault secret with Bicep
 description: Shows how to pass a secret from a key vault as a parameter during Bicep deployment.
 ms.topic: conceptual
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep
-ms.date: 05/06/2024
+ms.date: 12/06/2024
 ---
 
 # Use Azure Key Vault to pass secure parameter value during Bicep deployment
@@ -155,7 +155,7 @@ When using a key vault with the Bicep file for a [Managed Application](../manage
 
 You can use the [getSecret function](./bicep-functions-resource.md#getsecret) in Bicep files to obtain a key vault secret. Note that the `getSecret` function is exclusively applicable to a `Microsoft.KeyVault/vaults` resource. Additionally, it's restricted to usage within the `params` section of a module and can only be used with parameters with the `@secure()` decorator.
 
-Another function called `az.getSecret()` function can be used in Bicep parameter files to retrieve key vault secrets. For more information, see [Retrieve secrets in parameters file](#retrieve-secrets-in-parameters-file).
+Another function called `az.getSecret()` function can be used in Bicep parameters files to retrieve key vault secrets. For more information, see [Retrieve secrets in parameters file](#retrieve-secrets-in-parameters-file).
 
 Because the `getSecret` function can only be used in the `params` section of a module. Let's create a *sql.bicep* in the same directory as the *main.bicep* file with the following content:
 
@@ -207,7 +207,7 @@ module sql './sql.bicep' = {
 
 ## Retrieve secrets in parameters file
 
-If you don't want to use a module, you can retrieve key vault secrets in parameters file. However, the approach varies depending on whether you're using a JSON parameter file or a Bicep parameter file.
+If you don't want to use a module, you can retrieve key vault secrets in parameters file. However, the approach varies depending on whether you're using a JSON parameters file or a Bicep parameters file.
 
 The following Bicep file deploys a SQL server that includes an administrator password. The password parameter is set to a secure string. But the Bicep doesn't specify where that value comes from.
 
@@ -232,7 +232,7 @@ resource sqlServer 'Microsoft.Sql/servers@2023-08-01-preview' = {
 
 Now, create a parameters file for the preceding Bicep file. 
 
-### Bicep parameter file
+### Bicep parameters file
 
 [`az.getSecret`](./bicep-functions-parameters-file.md#getsecret) function can be used in a `.bicepparam` file to retrieve the value of a secret from a key vault.
 
@@ -244,7 +244,7 @@ param adminLogin = '<your-admin-login>'
 param adminPassword = az.getSecret('<subscription-id>', '<rg-name>', '<key-vault-name>', '<secret-name>', '<secret-version>')
 ```
 
-### JSON parameter file
+### JSON parameters file
 
 In the JSON parameters file, specify a parameter that matches the name of the parameter in the Bicep file. For the parameter value, reference the secret from the key vault. You reference the secret by passing the resource identifier of the key vault and the name of the secret: