Merge pull request #296344 from LiSeda/LS-batch9

LS_Bicep_batch 9

Author: prmerger-automator[bot]

articles/azure-resource-manager/bicep/add-template-to-azure-pipelines.md

@@ -1,36 +1,36 @@
 ---
-title: CI/CD with Azure Pipelines, Bicep, and bicepparam files
-description: In this quickstart, you learn how to configure continuous integration in Azure Pipelines by using Bicep and bicepparam files. It shows how to use an Azure CLI task to deploy a bicepparam file.
+title: 'Quickstart: Integrate Bicep with Azure Pipelines'
+description: This quickstart explains how to use Bicep and `.bicepparam` files to configure continuous integration and continuous deployments in Azure Pipelines, plus how to use an Azure CLI task to deploy a `.bicepparam` file.
 ms.topic: quickstart
 ms.custom: devx-track-bicep, devx-track-azurecli
-ms.date: 09/26/2024
+ms.date: 03/25/2025
 ---
 
 # Quickstart: Integrate Bicep with Azure Pipelines
 
-This quickstart shows you how to integrate Bicep files with Azure Pipelines for continuous integration and continuous deployment (CI/CD).
+This quickstart shows you how to integrate Bicep files with Azure Pipelines for continuous integration and continuous deployment.
 
-It provides a short introduction to the pipeline task you need for deploying a Bicep file. If you want more detailed steps on setting up the pipeline and project, see [Deploy Azure resources by using Bicep and Azure Pipelines](/training/paths/bicep-azure-pipelines/).
+It provides a short introduction to the pipeline task you need for deploying a Bicep file. For more detailed steps on setting up the pipeline and project, see the [Deploy Azure resources by using Bicep and Azure Pipelines](/training/paths/bicep-azure-pipelines/) Microsoft Learn module.
 
 ## Prerequisites
 
 If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
 
-You need an Azure DevOps organization. If you don't have one, [create one for free](/azure/devops/pipelines/get-started/pipelines-sign-up). If your team already has an Azure DevOps organization, make sure you're an administrator of the Azure DevOps project that you want to use.
+You also need an Azure DevOps organization. If you don't have one, [create one for free](/azure/devops/pipelines/get-started/pipelines-sign-up). If your team already has an Azure DevOps organization, make sure you're an administrator of the Azure DevOps project that you want to use.
 
 You need to have configured a [service connection](/azure/devops/pipelines/library/connect-to-azure) to your Azure subscription. The tasks in the pipeline execute under the identity of the service principal. For steps to create the connection, see [Create a DevOps project](../templates/deployment-tutorial-pipeline.md#create-a-devops-project).
 
 You need a [Bicep file](./quickstart-create-bicep-use-visual-studio-code.md) that defines the infrastructure for your project. This file is in a repository.
 
-You need a [bicepparam file](/azure/azure-resource-manager/bicep/parameter-files) that defines the parameters used by your bicep file. This file is in a repository.
+You need a ['.bicepparam' file](/azure/azure-resource-manager/bicep/parameter-files) that defines the parameters that your Bicep file uses. This file is in a repository.
 
 ## Create pipeline
 
 1. From your Azure DevOps organization, select **Pipelines** and **Create pipeline**.
 
     :::image type="content" source="./media/add-template-to-azure-pipelines/new-pipeline.png" alt-text="Screenshot of creating new pipeline.":::
 
-1. Specify where your code is stored. This quickstart uses Azure Repos Git.
+1. Specify where your code is stored. This quickstart uses Azure Repos Git repos.
 
     :::image type="content" source="./media/add-template-to-azure-pipelines/select-source.png" alt-text="Screenshot of selecting code source.":::
 
@@ -44,17 +44,17 @@ You need a [bicepparam file](/azure/azure-resource-manager/bicep/parameter-files
 
 ## Deploy Bicep files
 
-You can use Azure Resource Group Deployment task or Azure CLI task to deploy a Bicep file.
+You can use an Azure Resource Group deployment task or an Azure CLI task to deploy a Bicep file.
 
-### Use Azure Resource Manager Template Deployment task
+### Use Azure Resource Manager template deployment task
 
 > [!NOTE]
-> As of version 3.235.0 of the [Azure Resource Manager Template Deployment task](/azure/devops/pipelines/tasks/reference/azure-resource-manager-template-deployment-v3), usage of [bicepparam](/azure/azure-resource-manager/bicep/parameter-files) files is supported.
+> As of [Azure Resource Manager template deployment task](/azure/devops/pipelines/tasks/reference/azure-resource-manager-template-deployment-v3) version 3.235.0, usage of ['.bicepparam'](/azure/azure-resource-manager/bicep/parameter-files) files is supported.
 
 > [!NOTE]
-> The `AzureResourceManagerTemplateDeployment@3` task requires both Bicep and bicepparam files be provided when using bicepparam. The Bicep file can reference all supported locations for module references. The bicepparam file must reference the local Bicep file in the `using` statement.
+> The `AzureResourceManagerTemplateDeployment@3` task requires both Bicep and `.bicepparam` files to be provided when using `.bicepparam`. The Bicep file can reference all supported locations for module references. The `.bicepparam` file must reference the local Bicep file in the `using` statement.
 
-1. Replace your starter pipeline with the following YAML. It creates a resource group and deploys a Bicep and bicepparam file by using the Azure Resource Manager Template Deployment task.
+1. Replace your starter pipeline with the following YAML. It uses the Azure Resource Manager template deployment task to create a resource group and deploy a Bicep and `.bicepparam` file.
 
     ```yml
     trigger:
@@ -95,18 +95,18 @@ You can use Azure Resource Group Deployment task or Azure CLI task to deploy a B
 
 1. Update the values of `azureServiceConnection` and `location`.
 1. Verify you have a valid `main.bicep` file in your repo.
-1. Verify you have a valid `main.bicepparam` file in your repo that contains a [using](/azure/azure-resource-manager/bicep/bicep-using) statement.
-1. Select **Save**. The build pipeline automatically runs. Go back to the summary for your build pipeline, and watch the status.
+1. Verify you have a valid `main.bicepparam` file in your repo that contains a [`using`](/azure/azure-resource-manager/bicep/bicep-using) statement.
+1. Select **Save**. The build pipeline runs automatically. Go back to the summary for your build pipeline, and watch the status.
 
 ### Use Azure CLI task
 
 > [!NOTE]
-> The [az deployment group create](/cli/azure/deployment/group?view=azure-cli-latest#az-deployment-group-create&preserve-view=true) command requires only a bicepparam file. The `using` statement in the bicepparam file can target any supported location to reference the Bicep file. A Bicep file is only required in your repository when `using` from a local disk path with Azure CLI.
+> The [`az deployment group create`](/cli/azure/deployment/group?view=azure-cli-latest#az-deployment-group-create&preserve-view=true) command requires only a `bicepparam.` file. The `using` statement in the `.bicepparam` file can target any supported location to reference the Bicep file. A Bicep file is only required in your repository when `using` from a local disk path with the Azure CLI.
 
 > [!NOTE]
-> When you use a *[bicepparam](/azure/azure-resource-manager/bicep/parameter-files)* file with the [az deployment group create](/cli/azure/deployment/group?view=azure-cli-latest#az-deployment-group-create&preserve-view=true) command, you can't override parameters.
+> When you use a [`.bicepparam`](/azure/azure-resource-manager/bicep/parameter-files) file with the [`az deployment group create`](/cli/azure/deployment/group?view=azure-cli-latest#az-deployment-group-create&preserve-view=true) command, you can't override parameters.
 
-1. Replace your starter pipeline with the following YAML. It creates a resource group and deploys a [bicepparam](/azure/azure-resource-manager/bicep/parameter-files) file by using an [Azure CLI task](/azure/devops/pipelines/tasks/reference/azure-cli-v2):
+1. Replace your starter pipeline with the following YAML. It creates a resource group and deploys a [`.bicepparam`](/azure/azure-resource-manager/bicep/parameter-files) file by using an [Azure CLI task](/azure/devops/pipelines/tasks/reference/azure-cli-v2):
 
     ```yml
     trigger:
@@ -142,23 +142,23 @@ You can use Azure Resource Group Deployment task or Azure CLI task to deploy a B
             --name DeployPipelineTemplate
     ```
 
-    For the descriptions of the task inputs, see [Azure CLI task](/azure/devops/pipelines/tasks/reference/azure-cli-v2). When using the task on air-gapped cloud, you must set the `useGlobalConfig` property of the task to `true`. The default value is `false`.
+    For the descriptions of the task inputs, see [Azure CLI v2 task](/azure/devops/pipelines/tasks/reference/azure-cli-v2). When using the task on air-gapped cloud, you must set the `useGlobalConfig` property of the task to `true`. The default value is `false`.
 
 1. Update the values of `azureServiceConnection` and `location`.
-1. Verify you have a valid `main.bicepparam` file in your repo that contains a [using](/azure/azure-resource-manager/bicep/bicep-using) statement.
-1. Select **Save**. The build pipeline automatically runs. Go back to the summary for your build pipeline, and watch the status.
+1. Verify you have a valid `main.bicepparam` file in your repo that contains a [`using`](/azure/azure-resource-manager/bicep/bicep-using) statement.
+1. Select **Save**. The build pipeline runs automatically. Go back to the summary for your build pipeline, and watch the status.
 
 ## Clean up resources
 
 When the Azure resources are no longer needed, use the Azure CLI or Azure PowerShell to delete the quickstart resource group.
 
-# [CLI](#tab/CLI)
+# [Azure CLI](#tab/azure-cli)
 
 ```azurecli
 az group delete --name exampleRG
 ```
 
-# [PowerShell](#tab/PowerShell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell
 Remove-AzResourceGroup -Name exampleRG

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

@@ -2,8 +2,8 @@
 title: Decompile a JSON Azure Resource Manager template to Bicep
 description: Learn the commands for decompiling JSON Azure Resource Manager templates to Bicep files.
 ms.topic: how-to
-ms.date: 02/14/2025
 ms.custom: devx-track-bicep, devx-track-arm-template
+ms.date: 03/25/2025
 ---
 
 # Decompile a JSON Azure Resource Manager template to Bicep
@@ -32,9 +32,9 @@ This command creates a file named _main.bicep_ in the same directory as _main.js
 You can also decompile ARM template JSON to Bicep from Visual Studio Code by using the `Decompile into Bicep` command in Visual Studio Code. For more information, see [Decompile into Bicep](./visual-studio-code.md#decompile-into-bicep-command).
 
 > [!CAUTION]
-> Decompilation attempts to convert the file, but there is no guaranteed mapping from JSON ARM templates to Bicep. You might need to fix warnings and errors in the generated Bicep file. Or, decompilation can fail if an accurate conversion isn't possible. [Create an issue](https://github.com/Azure/bicep/issues) to report any issues or inaccurate conversions.
+> Decompilation attempts to convert the file, but there is no guaranteed mapping from JSON ARM templates to Bicep. You might need to fix warnings and errors in the generated Bicep file. Otherwise, decompilation can fail if an accurate conversion isn't possible. [Create an issue](https://github.com/Azure/bicep/issues) to report any issues or inaccurate conversions.
 
-The decompile and [build](bicep-cli.md#build) commands produce templates that are functionally equivalent. However, they might not be exactly the same during implementation. Converting a template from JSON to Bicep and then back to JSON might produce a template with different syntax than the original template. When deployed, the converted templates produce the same results.
+The decompile and [build](bicep-cli.md#build) commands produce templates that are functionally equivalent. However, they might not be exactly the same during implementation. Converting a template from JSON to Bicep and then back to JSON can produce a template with different syntax than the original template. When deployed, the converted templates produce the same results.
 
 ## Fix conversion issues
 
@@ -168,7 +168,7 @@ output storageAccountName string = uniqueStorageName
 ## Export template and convert
 
 > [!NOTE]
-> You can export Bicep files by using the Azure portal.  For more information, see [Use Azure portal to export a Bicep file](./export-bicep-portal.md).
+> You can use the Azure portal to export Bicep files.  For more information, see [Use Azure portal to export a Bicep file](./export-bicep-portal.md).
 
 You can export the template for a resource group and then pass it directly to the `decompile` command. The following examples show how to decompile an exported template:
 

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

@@ -1,16 +1,16 @@
 ---
 title: Reference existing resource in Bicep
-description: Describes how to reference a resource that already exists.
+description: Learn how to reference resources that exist.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 07/11/2024
+ms.date: 03/25/2025
 ---
 
-# Existing resources in Bicep
+# Reference existing resources in Bicep
 
 To reference an existing resource that isn't deployed in your current Bicep file, declare the resource with the `existing` keyword. Use the `existing` keyword when you're deploying a resource that needs to get a value from an existing resource. You access the existing resource's properties through its symbolic name.
 
-The resource isn't redeployed when referenced with the `existing` keyword.
+The resource doesn't deploy again when the `existing` keyword references it.
 
 ## Same scope
 
@@ -26,7 +26,7 @@ output blobEndpoint string = stg.properties.primaryEndpoints.blob
 
 ## Different scope
 
-Set the `scope` property to access a resource in a different scope. The following example references an existing storage account in a different resource group.
+Set the `scope` property to access a resource in a different scope. The following example references an existing storage account in a different resource group:
 
 ```bicep
 resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {