A Store where a Leaked Read Key Is Not the Whole Estate

azure-app-configuration

An App Configuration store where a leaked read key is not the whole estate. Works with Terraform and OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.

local_auth_enabled defaults to true, and the keys read everything. App Configuration keys are connection strings with no identity attached: a read key reads every value in the store, there is no per-key scoping, and the only revocation is regenerating the key for everybody at once. This is the store that holds feature flags and, in practice, connection strings - so "a read key" tends to mean "the estate". Off here, which forces Entra ID and gives you RBAC, conditional access, and an audit trail with a name in it.

The keys exist whether or not you use them. Turning local auth off is what makes them inert; leaving it on and simply not using them means the credential is still there, still valid, and still in the portal.

purge_protection_enabled defaults to false, and purging frees the name. That matters more than it sounds: the data-plane endpoint is derived from the store name, so whoever creates the next store with that name owns the address your applications are configured to trust.

public_network_access is unset by default, which behaves as Enabled. The data plane holding your configuration answers from the internet.

Smaller things: a precondition refuses the free SKU alongside private endpoints, purge protection, customer-managed keys or replicas, none of which it supports; and replica_regions is an output because a replica means the configuration exists in more places than one, which is worth knowing rather than discovering.

Verification

Static validation runs tofu fmt, init, validate, tflint and checkov. This module has not yet had a live test, so it is published as statically validated with its live test pending and does not carry the live-tested mark.