terragrunt azure-backend experiment manages azurerm remote state
Introduced 2026-07-29 · score 0.93
HOW TO USE IT
When an Azure Storage remote-state configuration uses `azurerm`, enable the `azure-backend` experiment and run `terragrunt --experiment azure-backend run -- plan` to manage backend resources and state blobs. [Release v1.1.2](https://github.com/gruntwork-io/terragrunt/releases/tag/v1.1.2)
terragrunt --experiment azure-backend run -- planWHY THIS HELPS
When maintaining a Terragrunt configuration that uses Azure Storage remote state, enable Terragrunt management of its backend resources and state blobs.
REQUIREMENTS AND LIMITATIONS
- Version: v1.1.2
- Availability: opt-in while the experiment is active
- --experiment azure-backend (required): Enables the Azure Storage (`azurerm`) remote-state experiment.
- run -- plan (required): Runs the underlying `plan` command through Terragrunt.
- location: Terragrunt-only Azure backend setting; release notes do not document its value semantics.
- storage account SKU options: Terragrunt-only settings; specific option names and semantics are not documented in the release notes.
- skip_* flags: Terragrunt-only flags; specific names and semantics are not documented in the release notes.
- enable_soft_delete: Terragrunt-only Azure backend setting; release notes do not document allowed values or details.
- soft_delete_retention_days: Terragrunt-only Azure backend setting; release notes do not document allowed values or range.
- msi_resource_id: Terragrunt-only setting that also selects the managed identity used for delete and migrate operations.
- Prerequisite: Enable the `azure-backend` experiment for this feature.
- Prerequisite: Use an Azure Storage `azurerm` remote-state backend.
- The `azure-backend` experiment must be enabled.
- State blob migration is within the same storage account.
FIRST-PARTY EVIDENCE
Check the installed version and the source before using it. Entry JSON