A Store where a Leaked Read Key Is Not the Whole Estate
local_auth_enabled defaults true and the keys carry no identity: a read key reads every value, cannot be scoped, and is revoked only by regenerating it for everybody. Purge protection defaults off, and purging frees the name - which frees the endpoint your applications trust.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-13 · how we verify
Use it from the registry
terraform · opentofumodule "app_configuration" {
source = "www.iac-bazaar.com/iac-bazaar/azure-app-configuration/azure"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
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.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
Related modules
azure-devops
Bootstraps an Azure DevOps project with an initialized Git repository and a YAML build pipeline - repeatable team setup as code.
azure-jenkins
Self-hosted Jenkins on a hardened Azure Linux VM - self-contained vnet/subnet/NSG, SSH-key auth only, managed-disk encryption, Jenkins installed via cloud-init.