az bicep snapshot and run subcommands
Introduced 2026-07-07 · score 0.90
HOW TO USE IT
When working with Bicep snapshots or forwarding a command to the Bicep CLI, use `az bicep snapshot` or `az bicep run` with the documented arguments.
az bicep snapshot --file <bicepparam-file>az bicep snapshot --file <bicepparam-file> --mode Validateaz bicep run --command "<bicep-cli-command-and-arguments>"WHY THIS HELPS
Use the Azure CLI Bicep surface when working with Bicep snapshots or runs.
REQUIREMENTS AND LIMITATIONS
- Version: 2.88.0
- snapshot --file (-f) (required): Path to the .bicepparam file to snapshot.
- snapshot --mode: Snapshot mode: `Overwrite` (default) writes the snapshot; `Validate` compares the existing snapshot and fails if differences are detected. Allowed values are mutually exclusive.
- snapshot --deployment-name: Deployment context used to resolve `existing` references during snapshot capture.
- snapshot --location (-l): Location in the deployment context used to resolve `existing` references during snapshot capture.
- snapshot --management-group-id: Management group ID in the deployment context used to resolve `existing` references during snapshot capture.
- snapshot --resource-group (-g): Resource group name in the deployment context used to resolve `existing` references during snapshot capture.
- snapshot --subscription-id: Subscription ID in the deployment context used to resolve `existing` references; does not change Azure CLI authentication context.
- snapshot --tenant-id: Tenant ID in the deployment context used to resolve `existing` references; does not change Azure CLI authentication context.
- run --command (-c) (required): Bicep CLI command and arguments as one quoted string. For a forwarded command starting with `--`, use `--command=<value>`.
- Prerequisite: `az bicep snapshot` requires Bicep CLI v0.41.2 or later.
- Docs conflict: The Azure CLI reference documents `az bicep snapshot`; the Bicep CLI commands page says `az bicep snapshot` does not exist and instructs running `bicep snapshot` directly. The Azure CLI reference matches the card's interface: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-cli
FIRST-PARTY EVIDENCE
- https://learn.microsoft.com/en-us/cli/azure/release-notes-azure-cli#july-07-2026
- https://learn.microsoft.com/en-us/cli/azure/bicep?view=azure-cli-latest
Check the installed version and the source before using it. Entry JSON