Merge pull request #295981 from LiSeda/LS-batch8

LS_Bicep_batch 8

Author: prmerger-automator[bot]

articles/azure-resource-manager/bicep/conditional-resource-deployment.md

@@ -1,9 +1,9 @@
 ---
-title: Conditional deployment with Bicep
-description: Describes how to conditionally deploy a resource in Bicep.
+title: Conditional deployments in Bicep with the if expression
+description: Understand how to use the 'if' expression to conditionally deploy a resource in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 07/11/2024
+ms.date: 03/25/2025
 ---
 
 # Conditional deployments in Bicep with the if expression
@@ -19,7 +19,7 @@ If you would rather learn about conditions through step-by-step guidance, see [B
 
 ## Define condition for deployment
 
-In Bicep, you can conditionally deploy a resource by passing in a parameter that specifies whether the resource is deployed. You test the condition with an `if` expression in the resource declaration. The following example shows the syntax for an `if` expression in a Bicep file. It conditionally deploys a DNS zone. When `deployZone` is `true`, it deploys the DNS zone. When `deployZone` is `false`, it skips deploying the DNS zone.
+In Bicep, you can conditionally deploy a resource by passing in a parameter that specifies if the resource is deployed. You test the condition with an `if` expression in the resource declaration. The following example shows the syntax for an `if` expression in a Bicep file. It conditionally deploys a Domain Name System (DNS) zone. When `deployZone` is `true`, it deploys the DNS zone. When `deployZone` is `false`, it skips deploying the DNS zone.
 
 ```bicep
 param deployZone bool
@@ -30,7 +30,7 @@ resource dnsZone 'Microsoft.Network/dnsZones@2023-07-01-preview' = if (deployZon
 }
 ```
 
-The next example conditionally deploys a module.
+The following example conditionally deploys a module:
 
 ```bicep
 param deployZone bool
@@ -40,11 +40,11 @@ module dnsZone 'dnszones.bicep' = if (deployZone) {
 }
 ```
 
-Conditions may be used with dependency declarations. For [explicit dependencies](resource-dependencies.md), Azure Resource Manager automatically removes it from the required dependencies when the resource isn't deployed. For implicit dependencies, referencing a property of a conditional resource is allowed but may produce a deployment error.
+Conditions can be used with dependency declarations. For [explicit dependencies](resource-dependencies.md), Azure Resource Manager automatically removes them from the required dependencies when the resource isn't deployed. For implicit dependencies, referencing a property of a conditional resource is allowed but might produce a deployment error.
 
 ## New or existing resource
 
-You can use conditional deployment to create a new resource or use an existing one. The following example shows how to either deploy a new storage account or use an existing storage account.
+You can use conditional deployment to create a new resource or use an existing one. The following example shows how to deploy a new storage account or use an existing storage account.
 
 ```bicep
 param storageAccountName string
@@ -72,16 +72,16 @@ resource saExisting 'Microsoft.Storage/storageAccounts@2023-04-01' existing = if
 output storageAccountId string = ((newOrExisting == 'new') ? saNew.id : saExisting.id)
 ```
 
-When the parameter `newOrExisting` is set to **new**, the condition evaluates to true. The storage account is deployed. Otherwise the existing storage account is used.
+When the parameter `newOrExisting` is set to **new**, the condition evaluates to true. The storage account is deployed. Otherwise, the existing storage account is used.
 
 > [!WARNING]
-> If you reference a conditionally-deployed resource that is not deployed. You will get an error saying the resource is not defined in the template.
+> If you reference a conditionally deployed resource that isn't deployed, you'll get an error saying that the resource isn't defined in the template.
 
 ## Runtime functions
 
-If you use a [reference](./bicep-functions-resource.md#reference) or [list](./bicep-functions-resource.md#list) function with a resource that is conditionally deployed, the function is evaluated even if the resource isn't deployed. You get an error if the function refers to a resource that doesn't exist.
+If you use a [reference](./bicep-functions-resource.md#reference) or [list](./bicep-functions-resource.md#list) function with a resource that's conditionally deployed, the function is evaluated even if the resource isn't deployed. You get an error if the function refers to a resource that doesn't exist.
 
-Use the [conditional expression ?:](./operators-logical.md#conditional-expression--) operator to make sure the function is only evaluated for conditions when the resource is deployed. The following example template shows how to use this function with expressions that are only conditionally valid.
+Use the [conditional expression ?:](./operators-logical.md#conditional-expression--) operator to ensure that the function is only evaluated for conditions when the resource is deployed. The following example template shows how to use this function with expressions that are only conditionally valid.
 
 ```bicep
 param vmName string
@@ -110,6 +110,5 @@ output mgmtStatus string = ((!empty(logAnalytics)) ? 'Enabled monitoring for VM!
 
 ## Next steps
 
-* Review the Learn module [Build flexible Bicep templates by using conditions and loops](/training/modules/build-flexible-bicep-templates-conditions-loops/).
 * For recommendations about creating Bicep files, see [Best practices for Bicep](best-practices.md).
 * To create multiple instances of a resource, see [Iterative loops in Bicep](loops.md).

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

@@ -2,8 +2,8 @@
 title: Deploy Bicep files with the Azure CLI  
 description: Learn how to use Azure Resource Manager and the Azure CLI to deploy resources to Azure. The resources are defined in a Bicep file.
 ms.topic: how-to
-ms.date: 01/13/2025
 ms.custom: devx-track-azurecli, seo-azure-cli, devx-track-arm-template, devx-track-bicep
+ms.date: 03/25/2025
 ---
 
 # Deploy Bicep files with the Azure CLI
@@ -19,7 +19,7 @@ You need a Bicep file to deploy, and the file must be local. You also need the A
 
 Samples for the Azure CLI are written for the `bash` shell. To run this sample in Windows PowerShell or Command Prompt (cmd), you might need to change elements of the script.
 
-If you don't have the Azure CLI installed, you can use Azure Cloud Shell. For more information, see [Deploy Bicep files with Azure Cloud Shell](./deploy-cloud-shell.md).
+If you don't have the Azure CLI installed, you can use Azure Cloud Shell. For more information, see [Deploy Bicep files from Azure Cloud Shell](./deploy-cloud-shell.md).
 
 [!INCLUDE [permissions](../../../includes/template-deploy-permissions.md)]
 
@@ -39,23 +39,23 @@ You can target your deployment to a resource group, subscription, management gro
   az deployment sub create --location <location> --template-file <path-to-bicep>
   ```
 
-  For more information about subscription-level deployments, see [Use Bicep to deploy resources to subscription](deploy-to-subscription.md).
+  For more information about subscription-level deployments, see [Subscription deployments with Bicep files](deploy-to-subscription.md).
 
 * To deploy to a **management group**, use [`az deployment mg create`](/cli/azure/deployment/mg#az-deployment-mg-create):
 
   ```azurecli-interactive
   az deployment mg create --location <location> --template-file <path-to-bicep>
   ```
 
-  For more information about management-group-level deployments, see [Use Bicep to deploy resources to management group](deploy-to-management-group.md).
+  For more information about management-group-level deployments, see [Management group deployments with Bicep files](deploy-to-management-group.md).
 
 * To deploy to a **tenant**, use [`az deployment tenant create`](/cli/azure/deployment/tenant#az-deployment-tenant-create):
 
   ```azurecli-interactive
   az deployment tenant create --location <location> --template-file <path-to-bicep>
   ```
 
-  For more information about tenant-level deployments, see [Use Bicep to deploy resources to tenant](deploy-to-tenant.md).
+  For more information about tenant-level deployments, see [Tenant deployments with Bicep file](deploy-to-tenant.md).
 
 ## Deploy local Bicep file
 
@@ -170,7 +170,7 @@ The evaluation of parameters follows a sequential order, meaning that if a value
 
 ### Bicep parameters files
 
-Rather than passing parameters as inline values in your script, you might find it easier to use a [Bicep parameters file](#bicep-parameters-files) or a [JSON parameters file](#json-parameters-files) that contains the parameter values. The parameters file must be a local file since the Azure CLI doesn't support external parameters files. For more information about parameters files, see [Create parameters files for Bicep deployment](./parameter-files.md).
+Rather than passing parameters as inline values in your script, you might find it easier to use a [Bicep parameters file](#bicep-parameters-files) or a [JSON parameters file](#json-parameters-files) that contains the parameter values. The parameters file must be a local file since the Azure CLI doesn't support external parameters files. For more information about parameters files, see [Create a parameters file for Bicep deployment](./parameter-files.md).
 
 You can use a Bicep parameters file to deploy a Bicep file with [Azure CLI](./install.md#azure-cli) version 2.53.0 or later and [Bicep CLI](./install.md#visual-studio-code-and-bicep-extension) version 0.22.X or later. 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 prompt an, "Only a .bicep template is allowed with a .bicepparam file," error.
 
@@ -233,4 +233,4 @@ To avoid conflicts with concurrent deployments and to ensure unique entries in t
 
 ## Next steps
 
-To understand how to define parameters in your file, see [Understand the structure and syntax of Bicep files](file.md).
+To understand how to define parameters in your file, see [Bicep file structure and syntax](file.md).

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

@@ -3,7 +3,7 @@ title: Bicep modules
 description: This article describes how to define a module in a Bicep file and how to use module scopes.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 02/21/2025
+ms.date: 03/25/2025
 ---
 
 # Bicep modules
@@ -91,7 +91,7 @@ module <symbolic-name> '<path-to-file>' = {
 }
 ```
 
-To *conditionally deploy a module*, add an `if` expression. The use is similar to [conditionally deploying a resource](conditional-resource-deployment.md).
+To *conditionally deploy a module*, add an `if` expression. This is similar to [conditionally deploying a resource](conditional-resource-deployment.md).
 
 ```bicep
 // conditional deployment
@@ -116,7 +116,7 @@ module <symbolic-name> '<path-to-file>' = [for <item> in <collection>: {
 }]
 ```
 
-Like resources, modules are deployed in parallel unless they depend on other modules or resources. Typically, you don't need to set dependencies because they're determined implicitly. If you need to set an explicit dependency, add `dependsOn` to the module definition. To learn more about dependencies, see [Resource dependencies](resource-dependencies.md).
+Like resources, modules are deployed in parallel unless they depend on other modules or resources. Typically, you don't need to set dependencies because they're determined implicitly. If you need to set an explicit dependency, add `dependsOn` to the module definition. To learn more about dependencies, see [Resource dependencies in Bicep](resource-dependencies.md).
 
 ```bicep
 module <symbolic-name> '<path-to-file>' = {
@@ -136,7 +136,7 @@ The file for the module can be either a local file or an external file. The exte
 
 ### Local file
 
-If the module is a *local file*, provide a relative path to that file. All paths in Bicep must be specified by using the forward slash (/) directory separator to ensure consistent compilation across platforms. The Windows backslash (\\) character is unsupported. Paths can contain spaces.
+If the module is a *local file*, provide a relative path to that file. All paths in Bicep must be specified by the forward slash (/) directory separator to ensure consistent compilation across platforms. The Windows backslash (\\) character isn't supported. Paths can contain spaces.
 
 For example, to deploy a file that's up one level in the directory from your main file, use:
 
@@ -160,7 +160,7 @@ There are public and private module registries.
 
 [Azure Verified Modules](https://azure.github.io/Azure-Verified-Modules/) are prebuilt, pretested, and preverified modules that you can use to deploy resources on Azure. Microsoft employees created and own these modules. They were designed to simplify and accelerate the deployment process for common Azure resources and configurations. The modules also align to best practices like Azure Well-Architected Framework.
 
-Browse to the [Azure Verified Modules Bicep Index](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/) to see the list of modules that are available. Select the highlighted numbers in the following screenshot to go directly to that filtered view.
+Browse [Bicep Modules](https://azure.github.io/Azure-Verified-Modules/indexes/bicep/) to see the list of modules that are available. Select the highlighted numbers in the following screenshot to go directly to that filtered view:
 
 :::image type="content" source="./media/modules/bicep-azure-verified-modules-avm.png" alt-text="Screenshot that shows Azure Verified Modules.":::
 
@@ -174,9 +174,9 @@ To link to a public module, specify the module path with the following syntax:
 module <symbolic-name> 'br/public:<file-path>:<tag>' = {}
 ```
 
-- **br/public**: Is the alias for public modules. You can customize this alias in the [Bicep configuration file](./bicep-config-modules.md).
-- **file path**: Can contain segments that you can separate by the `/` character.
-- **tag**: Is used for specifying a version for the module.
+- **br/public**: This is the alias for public modules. You can customize this alias in the [Bicep configuration file](./bicep-config-modules.md).
+- **file path**: This can contain segments that you can separate with the `/` character.
+- **tag**: This is used for specifying a version for the module.
 
 For example:
 
@@ -205,8 +205,8 @@ If you [published a module to a registry](bicep-cli.md#publish), you can link to
 module <symbolic-name> 'br:<registry-name>.azurecr.io/<file-path>:<tag>' = {
 ```
 
-- **br**: Is a scheme name for a Bicep registry.
-- **file path**: Is called `repository` in Azure Container Registry. The file path can contain segments that are separated by the `/` character.
+- **br**: This is a scheme name for a Bicep registry.
+- **file path**: This is called `repository` in Azure Container Registry. The file path can contain segments that are separated by the `/` character.
 - **tag**: Is used to specify a version for the module.
 
 For example:
@@ -220,7 +220,7 @@ module stgModule 'br:exampleregistry.azurecr.io/bicep/modules/storage:v1' = {
 }
 ```
 
-When you reference a module in a registry, the Bicep extension in Visual Studio Code automatically calls [bicep restore](bicep-cli.md#restore) to copy the external module to the local cache. It takes a few moments to restore the external module. If IntelliSense for the module doesn't work immediately, wait for the restore to complete.
+When you reference a module in a registry, the Bicep extension in Visual Studio Code automatically calls [`bicep restore`](bicep-cli.md#restore) to copy the external module to the local cache. It takes a few moments to restore the external module. If IntelliSense for the module doesn't work immediately, wait for the restore to complete.
 
 The full path for a module in a registry can be long. Instead of providing the full path each time you want to use the module, [configure aliases in the bicepconfig.json file](bicep-config-modules.md#aliases-for-modules). The aliases make it easier to reference the module. For example, with an alias, you can shorten the path to:
 
@@ -273,7 +273,7 @@ module stgModule 'ts/ContosoSpecs:storageSpec:2.0' = {
 
 ## Use decorators
 
-Decorators are written in the format `@expression` and are placed above module declarations. The following table shows the available decorators for modules.
+Decorators are written in the format `@expression` and are placed above module declarations. The following table shows the available decorators for modules:
 
 | Decorator | Argument | Description |
 | --------- | ----------- | ------- |
@@ -450,7 +450,7 @@ module storage2 '../create-storage-account/main.bicep' = {
 }
 ```
 
-Set the `scope` property to a valid scope object. If your Bicep file deploys a resource group, subscription, or management group, you can set the scope for a module to the symbolic name for that resource. Or you can use the scope functions to get a valid scope.
+Set the `scope` property to a valid scope object. If your Bicep file deploys a resource group, subscription, or management group, you can set the scope for a module to the symbolic name for that resource. Or, you can use the scope functions to get a valid scope.
 
 Those functions are:
 
@@ -474,7 +474,7 @@ module mgDeploy 'main.bicep' = {
 
 You can get values from a module and use them in the main Bicep file. To get an output value from a module, use the `outputs` property on the module object.
 
-The first example creates a storage account and returns the primary endpoints.
+The first example creates a storage account and returns the primary endpoints:
 
 ```bicep
 @minLength(3)
@@ -512,7 +512,7 @@ resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
 output storageEndpoint object = stg.properties.primaryEndpoints
 ```
 
-When the property is used as a module, you can get that output value.
+When the property is used as a module, you can get that output value:
 
 ```bicep
 targetScope = 'subscription'
@@ -539,5 +539,5 @@ output storageEndpoint object = stgModule.outputs.storageEndpoint
 
 ## Related content
 
-- For a tutorial, see [Deploy Azure resources by using Bicep templates](/training/modules/deploy-azure-resources-by-using-bicep-templates/).
-- To pass a sensitive value to a module, use the [getSecret](bicep-functions-resource.md#getsecret) function.
+- For a tutorial, see [Build your first Bicep template](/training/modules/deploy-azure-resources-by-using-bicep-templates/).
+- To pass a sensitive value to a module, use the [`getSecret`](bicep-functions-resource.md#getsecret) function.

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

@@ -1,9 +1,9 @@
 ---
-title: Create Parameters Files for Bicep Deployment
-description: Learn how to create Bicep parameters files, instead of passing parameters as inline values in your script.
+title: Create a parameters file for bicep deployment
+description: Learn how to create Bicep parameters files instead of passing parameters as inline values in your script.
 ms.topic: how-to
-ms.date: 01/10/2025
 ms.custom: devx-track-bicep
+ms.date: 03/25/2025
 ---
 
 # Create a parameters file for Bicep deployment
@@ -473,7 +473,7 @@ New-AzResourceGroupDeployment `
 
 ---
 
-For more information, see [Deploy Bicep files by using Azure PowerShell](./deploy-powershell.md#parameters). To deploy `.bicep` files, you need Azure PowerShell version 5.6.0 or later.
+For more information, see [Deploy Bicep files with Azure PowerShell](./deploy-powershell.md#parameters). To deploy `.bicep` files, you need Azure PowerShell version 5.6.0 or later.
 
 ## Parameter precedence