Merge pull request #269951 from mumian/0321-bicep-parameters

Add information about using parameters file and inline parameters

Author: prmerger-automator[bot]

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: conceptual
-ms.date: 11/03/2023
+ms.date: 03/22/2024
 ms.custom: devx-track-azurecli, seo-azure-cli, devx-track-arm-template, devx-track-bicep
 ---
 
@@ -203,6 +203,8 @@ az deployment group create \
 
 For more information about the parameters file, see [Create Resource Manager parameters file](./parameter-files.md).
 
+You can use inline parameters and a location parameters file in the same deployment operation. For more information, see [Parameter precedence](./parameter-files.md#parameter-precedence).
+
 ## Preview changes
 
 Before deploying your Bicep file, you can preview the changes the Bicep file will make to your environment. Use the [what-if operation](./deploy-what-if.md) to verify that the Bicep file makes the changes that you expect. What-if also validates the Bicep file for errors.

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: conceptual
 ms.custom: devx-track-arm-template, devx-track-bicep, devx-track-azurepowershell
-ms.date: 11/03/2023
+ms.date: 03/22/2024
 ---
 
 # Deploy resources with Bicep and Azure PowerShell
@@ -167,6 +167,8 @@ New-AzResourceGroupDeployment `
 
 The `TemplateParameterUri` parameter doesn't support `.bicepparam` files, it only supports JSON parameters files.
 
+You can use inline parameters and a location parameters file in the same deployment operation. For more information, see [Parameter precedence](./parameter-files.md#parameter-precedence).
+
 ## Preview changes
 
 Before deploying your Bicep file, you can preview the changes the Bicep file will make to your environment. Use the [what-if operation](./deploy-what-if.md) to verify that the Bicep file makes the changes that you expect. What-if also validates the Bicep file for errors.

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: conceptual
 ms.custom: devx-track-bicep
-ms.date: 03/19/2024
+ms.date: 03/22/2024
 ---
 
 # Create parameters files for Bicep deployment
@@ -361,6 +361,8 @@ From Bicep CLI, you can build a Bicep parameters file into a JSON parameters fil
 
 ## Deploy Bicep file with parameters file
 
+### Azure CLI
+
 From Azure CLI, you can pass a parameter file with your Bicep file deployment.
 
 # [Bicep parameters file](#tab/Bicep)
@@ -386,8 +388,35 @@ az deployment group create \
 
 ---
 
+You can use inline parameters and a location parameters file in the same deployment operation. For example:
+
+# [Bicep parameters file](#tab/Bicep)
+
+```azurecli
+az deployment group create \
+  --name ExampleDeployment \
+  --resource-group ExampleGroup \
+  --parameters storage.bicepparam \
+  --parameters storageAccountType=Standard_LRS
+```
+
+# [JSON parameters file](#tab/JSON)
+
+```azurecli
+az deployment group create \
+  --name ExampleDeployment \
+  --resource-group ExampleGroup \
+  --template-file storage.bicep \
+  --parameters storage.parameters.json \
+  --parameters storageAccountType=Standard_LRS
+```
+
+---
+
 For more information, see [Deploy resources with Bicep and Azure CLI](./deploy-cli.md#parameters).
 
+### Azure PowerShell
+
 From Azure PowerShell, pass a local parameters file using the `TemplateParameterFile` parameter.
 
 # [Bicep parameters file](#tab/Bicep)
@@ -402,7 +431,6 @@ New-AzResourceGroupDeployment `
 
 # [JSON parameters file](#tab/JSON)
 
-
 ```azurepowershell
 New-AzResourceGroupDeployment `
   -Name ExampleDeployment `
@@ -411,15 +439,44 @@ New-AzResourceGroupDeployment `
   -TemplateParameterFile C:\MyTemplates\storage.parameters.json
 ```
 
+---
+
+You can use inline parameters and a location parameters file in the same deployment operation. For example:
+
+# [Bicep parameters file](#tab/Bicep)
+
+```azurepowershell
+New-AzResourceGroupDeployment `
+  -Name ExampleDeployment `
+  -ResourceGroupName ExampleResourceGroup `
+  -TemplateFile C:\MyTemplates\storage.bicep `
+  -TemplateParameterFile C:\MyTemplates\storage.bicepparam `
+  -storageAccountType Standard_LRS
+```
+
+# [JSON parameters file](#tab/JSON)
+
+```azurepowershell
+New-AzResourceGroupDeployment `
+  -Name ExampleDeployment `
+  -ResourceGroupName ExampleResourceGroup `
+  -TemplateFile C:\MyTemplates\storage.bicep `
+  -TemplateParameterFile C:\MyTemplates\storage.parameters.json `
+  -storageAccountType Standard_LRS
+
+```
+
+
+
 ---
 
 For more information, see [Deploy resources with Bicep and Azure PowerShell](./deploy-powershell.md#parameters). To deploy _.bicep_ files you need Azure PowerShell version 5.6.0 or later.
 
 ## Parameter precedence
 
-You can use inline parameters and a local parameters file in the same deployment operation. For example, you can specify some values in the local parameters file and add other values inline during deployment. If you provide values for a parameter in both the local parameters file and inline, the inline value takes precedence. 
+You can use inline parameters and a local parameters file in the same deployment operation. For example, you can specify some values in the local parameters file and add other values inline during deployment. If you provide values for a parameter in both the local parameters file and inline, the inline value takes precedence.
 
-It's possible to use an external parameters file, by providing the URI to the file. When you use an external parameters file, you can't pass other values either inline or from a local file. All inline parameters are ignored. Provide all parameter values in the external file.
+It's possible to use an external JSON parameters file, by providing the URI to the file. External Bicep parameters file is not currently supported. When you use an external parameters file, you can't pass other values either inline or from a local file. All inline parameters are ignored. Provide all parameter values in the external file.
 
 ## Parameter name conflicts
 

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: 12/06/2023
+ms.date: 03/22/2024
 ---
 
 # Parameters in Bicep
@@ -235,8 +235,8 @@ The following example shows a parameter that is an object. The default value sho
 
 :::code language="bicep" source="~/azure-docs-bicep-samples/syntax-samples/parameters/parameterobject.bicep":::
 
-
 ## 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 providing parameter values at deployment, see [Deploy with Azure CLI](./deploy-cli.md), and [Deploy with Azure PowerShell](./deploy-powershell.md).