Document Details
Parameter Files
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation page demonstrates a Windows bias by providing all PowerShell deployment examples using Windows-style paths (e.g., C:\MyTemplates\...), referencing Visual Studio Code (a tool more commonly used on Windows), and omitting any explicit Linux/bash shell or cross-platform examples for PowerShell commands. There are no bash or Linux shell examples for deploying Bicep files, and all file path conventions are Windows-centric. The documentation also references Azure PowerShell and Visual Studio Code before mentioning the Bicep CLI, and does not show how to use Linux-native tools or file paths.
Recommendations:
- Add Linux/bash shell examples for deploying Bicep files using Azure CLI, showing Linux-style paths (e.g., /home/user/templates/storage.bicep).
- Include PowerShell Core examples that use Linux/macOS file paths, or clarify that PowerShell commands work cross-platform.
- When referencing Visual Studio Code, mention that it is available on Linux and macOS, or suggest alternative editors where appropriate.
- Balance the order of tool mentions (e.g., Azure CLI before Azure PowerShell) and ensure that Linux-native workflows are described alongside Windows ones.
- For every example using Windows paths, provide a corresponding example using Linux paths.
- Explicitly state that the Bicep CLI and Azure CLI are cross-platform, and provide installation links or notes for Linux users.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-12 00:58 | #8 | cancelled | ✅ Clean |
| 2025-07-10 05:06 | #7 | processing | ✅ Clean |
Flagged Code Snippets
---
## File name
### [Bicep parameters file](#tab/Bicep)
The file extension for a Bicep parameters file is `.bicepparam`.
To deploy to multiple environments, you create more than one parameters file. When you use multiple parameters files, label them according to their use. For example, to deploy resources, use the label _main.dev.bicepparam_ for development and the label _main.prod.bicepparam_ for production.
### [JSON parameters file](#tab/JSON)
The general naming convention for a parameters file is to include _parameters_ in the Bicep file name. For example, if your Bicep file is named _azuredeploy.bicep_, then your parameters file is named _azuredeploy.parameters.json_. This naming convention helps you see the connection between the Bicep file and the parameters.
To deploy to different environments, you create more than one parameters file. When you use multiple parameters files, label them according to their use. For example, to deploy resources, use the label _azuredeploy.parameters-dev.json_ for development and the label _azuredeploy.parameters-prod.json_ for production.
---
## Define parameter values
To determine how to define parameter names and values, open your Bicep file. Look at the **parameters** section of the Bicep file. The following examples show the parameters from a Bicep file named `main.bicep`:
> [!NOTE]
> For inline comments, you can use either // or /* ... */. In Visual Studio Code, save parameters files with the `JSONC` file type. If you don't, you get an error message that says, "Comments not permitted in JSON."
---
To see if there are any restrictions like maximum length, check the Bicep file's allowed values. The allowed values specify the range of values you can provide for a parameter. In this example, `storagePrefix` can have a maximum of 11 characters, and `storageAccountType` must specify an allowed value.
### [Bicep parameters file](#tab/Bicep)
---
For more information, see [Deploy Bicep files by using the Azure CLI](./deploy-cli.md#parameters).
### Azure PowerShell
From Azure PowerShell, pass a local parameters file by using the `TemplateParameterFile` parameter.
### [Bicep parameters file](#tab/Bicep)