docs/src/data/experiments/azure-backend.mdx
Experimental support for the Azure Storage (azurerm) remote state backend.
azure-backend - What it doesTerragrunt already recognizes backend = "azurerm" in remote_state blocks regardless
of whether this experiment is enabled, and currently falls through to the native
OpenTofu/Terraform azurerm backend. This experiment reserves the flag for the
long-term goal of having Terragrunt manage Azure Storage accounts, blob containers,
and state blobs in the same way it already manages S3 buckets and GCS buckets:
automatic bootstrap, delete, migrate, and direct state reads for
dependency-fetch-output-from-state.
In its current form (initial registration) the experiment only:
azure-backend experiment name.azurerm backend slot in Terragrunt's remote state layer.The flag itself currently has no behavioral effect: there is no Azure SDK code, authentication logic, or storage account management yet, and the backend is not gated on the flag. Functional behavior will land in subsequent releases.
azure-backend - How to enable it# Via CLI flag
terragrunt --experiment azure-backend run -- plan
# Via environment variable
export TG_EXPERIMENT=azure-backend
terragrunt run -- plan
azure-backend - How to provide feedbackTrack and discuss this experiment in gruntwork-io/terragrunt#4307. When reporting issues or providing feedback, please include:
init, plan, or backend bootstrap.azure-backend - Criteria for stabilizationTo transition the azure-backend feature to a stable release, the following must be addressed, at a minimum:
internal/azurehelper package wrapping the Azure SDK with a builder pattern matching awshelper/gcphelper.use_azuread_auth.--dependency-fetch-output-from-state.