Merge pull request #291548 from LiSeda/LS-params3

LS_Bicep parameters_batch 3

Author: prmerger-automator[bot]

articles/azure-resource-manager/bicep/msbuild-bicep-file.md

@@ -1,7 +1,7 @@
 ---
 title: Use MSBuild to convert Bicep to JSON
 description: Use MSBuild to convert a Bicep file to Azure Resource Manager template (ARM template) JSON.
-ms.date: 07/11/2024
+ms.date: 12/06/2024
 ms.topic: quickstart
 ms.custom: devx-track-bicep, devx-track-arm-template
 
@@ -10,7 +10,7 @@ ms.custom: devx-track-bicep, devx-track-arm-template
 
 # Quickstart: Use MSBuild to convert Bicep to JSON
 
-Learn the process of utilizing [MSBuild](/visualstudio/msbuild/msbuild) for the conversion of Bicep files to Azure Resource Manager JSON templates (ARM templates). Additionally, MSBuild can be utilized for the conversion of [Bicep parameter files](./parameter-files.md?tabs=Bicep) to [Azure Resource Manager parameter files](../templates/parameter-files.md) with the NuGet packages version 0.23.x or later. The provided examples demonstrate the use of MSBuild from the command line with C# project files for the conversion. These project files serve as examples that can be utilized in an MSBuild continuous integration (CI) pipeline.
+Learn the process of utilizing [MSBuild](/visualstudio/msbuild/msbuild) for the conversion of Bicep files to Azure Resource Manager JSON templates (ARM templates). Additionally, MSBuild can be utilized for the conversion of [Bicep parameters files](./parameter-files.md?tabs=Bicep) to [Azure Resource Manager parameters files](../templates/parameter-files.md) with the NuGet packages version 0.23.x or later. The provided examples demonstrate the use of MSBuild from the command line with C# project files for the conversion. These project files serve as examples that can be utilized in an MSBuild continuous integration (CI) pipeline.
 
 ## Prerequisites
 
@@ -29,7 +29,7 @@ In certain environments, using a single package feed helps prevent problems aris
 
 ## MSBuild tasks and Bicep packages
 
-From your continuous integration (CI) pipeline, you can use MSBuild tasks and CLI packages to convert Bicep files and Bicep parameter files into JSON. The functionality relies on the following NuGet packages:
+From your continuous integration (CI) pipeline, you can use MSBuild tasks and CLI packages to convert Bicep files and Bicep parameters files into JSON. The functionality relies on the following NuGet packages:
 
 | Package Name | Description |
 | ----  |---- |
@@ -118,7 +118,7 @@ The latest NuGet package versions match the latest [Bicep CLI](./bicep-cli.md) v
 
 ### Project file examples
 
-The following examples show how to configure C# console application project files for converting Bicep files and Bicep parameter files to JSON. Replace `__LATEST_VERSION__` with the latest version of the [Bicep NuGet packages](https://www.nuget.org/packages/Azure.Bicep.Core/) in the following examples. See [MSBuild tasks and Bicep packages](#msbuild-tasks-and-bicep-packages) for finding the latest version.
+The following examples show how to configure C# console application project files for converting Bicep files and Bicep parameters files to JSON. Replace `__LATEST_VERSION__` with the latest version of the [Bicep NuGet packages](https://www.nuget.org/packages/Azure.Bicep.Core/) in the following examples. See [MSBuild tasks and Bicep packages](#msbuild-tasks-and-bicep-packages) for finding the latest version.
 
 #### SDK-based example
 
@@ -277,7 +277,7 @@ Use the classic example only if the previous examples don't work for you. In thi
 
 ## Convert Bicep to JSON
 
-These examples demonstrate the conversion of a Bicep file and a Bicep parameter file to JSON using MSBuild. Start by creating a project file for .NET, .NET Core 3.1, or the Classic framework. Then, generate the Bicep file and the Bicep parameter file before running MSBuild.
+These examples demonstrate the conversion of a Bicep file and a Bicep parameters file to JSON using MSBuild. Start by creating a project file for .NET, .NET Core 3.1, or the Classic framework. Then, generate the Bicep file and the Bicep parameters file before running MSBuild.
 
 ### Create project
 
@@ -402,7 +402,7 @@ You need a Bicep file and a BicepParam file to be converted to JSON.
 
 ### Run MSBuild
 
-Run MSBuild to convert the Bicep file and the Bicep parameter file to JSON.
+Run MSBuild to convert the Bicep file and the Bicep parameters file to JSON.
 
 1. Open a Visual Studio Code terminal session.
 1. In the PowerShell session, go to the folder that contains the project file. For example, the _C:\msBuildDemo_ directory.

articles/azure-resource-manager/bicep/parameter-files.md

@@ -3,7 +3,7 @@ title: Create parameters files for Bicep deployment
 description: Create parameters file for passing in values during deployment of a Bicep file.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 12/04/2024
+ms.date: 12/06/2024
 ---
 
 # Create parameters files for Bicep deployment

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

@@ -3,7 +3,7 @@ title: Parameters in Bicep files
 description: Describes how to define parameters in a Bicep file.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 08/20/2024
+ms.date: 12/06/2024
 ---
 
 # Parameters in Bicep
@@ -292,5 +292,5 @@ resource vnet 'Microsoft.Network/virtualNetworks@2023-11-01' = {
 ## Next steps
 
 - To learn about the available properties for parameters, see [Understand the structure and syntax of Bicep files](file.md).
-- To learn about passing in parameter values as a file, see [Create a Bicep parameter file](parameter-files.md).
+- To learn about passing in parameter values as a file, see [Create a Bicep parameters file](parameter-files.md).
 - To learn about providing parameter values at deployment, see [Deploy with Azure CLI](./deploy-cli.md), and [Deploy with Azure PowerShell](./deploy-powershell.md).

articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md

@@ -1,7 +1,7 @@
 ---
 title: Create Bicep files - Visual Studio Code
 description: Use Visual Studio Code and the Bicep extension to Bicep files for deploy Azure resources.
-ms.date: 12/04/2024
+ms.date: 12/06/2024
 ms.topic: quickstart
 ms.custom: mode-ui, devx-track-bicep
 #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio Code to create and edit Bicep files so that I can use them to deploy Azure resources.
@@ -256,9 +256,9 @@ The visualizer shows the resources defined in the Bicep file with the resource d
 
     :::image type="content" source="./media/quickstart-create-bicep-use-visual-studio-code/vscode-bicep-deploy-resource-group-locations.png" alt-text="Screenshot of resource group location options.":::
 
-1. From **Select a parameter file**, select **None**.
+1. From **Select a parameters file**, select **None**.
 
-    :::image type="content" source="./media/quickstart-create-bicep-use-visual-studio-code/vscode-bicep-deploy-select-parameter-file.png" alt-text="Screenshot of Select parameter file.":::
+    :::image type="content" source="./media/quickstart-create-bicep-use-visual-studio-code/vscode-bicep-deploy-select-parameter-file.png" alt-text="Screenshot of Select parameters file.":::
 
 It takes a few moments to create the resources. For more information, see [Deploy Bicep files with Visual Studio Code](./deploy-vscode.md).
 

articles/azure-resource-manager/bicep/scenarios-secrets.md

@@ -5,7 +5,7 @@ author: johndowns
 ms.author: jodowns
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/20/2024
+ms.date: 12/06/2024
 ---
 # Manage secrets by using Bicep
 
@@ -190,7 +190,7 @@ param securePassword = az.getSecret('<subscriptionId>', '<resourceGroupName>', '
 
 When you deploy your Azure resources by using a pipeline, you need to take care to handle your secrets appropriately.
 
-- Avoid storing secrets in your code repository. For example, don't add secrets to parameter files, or to your pipeline definition YAML files.
+- Avoid storing secrets in your code repository. For example, don't add secrets to parameters files or to your pipeline definition YAML files.
 - In GitHub Actions, use [encrypted secrets](https://docs.github.com/actions/security-guides/encrypted-secrets) to store secure data. Use [secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning) to detect any accidental commits of secrets.
 - In Azure Pipelines, use [secret variables](/azure/devops/pipelines/process/variables#secret-variables) to store secure data.