Azure Key Vault
RBAC-mode Key Vault with private endpoint, diagnostics, and managed keys/secrets/certificates scaffolding.
Compare Secrets & Key Management across clouds →
Part of: Azure Production Landing Zone
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-29 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o azure-key-vault-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/azure-key-vault/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle azure-key-vault-1.0.0.sigstore.json \
azure-key-vault-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "ea22f081d381a16407d0f46d15e876819e9e2577d0bd0c42653f9b5780778bff azure-key-vault-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "key_vault" {
source = "www.iac-bazaar.com/iac-bazaar/azure-key-vault/azure"
version = "1.0.0"
}Paid module — needs a purchase (or a subscription that covers it) plus a registry token from /account/tokens. 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 Free module. This one is Basic, so its contract unlocks when you buy it.
Documentation
azure-key-vault
RBAC-mode Key Vault with private endpoint, diagnostics, and managed
keys/secrets/certificates scaffolding. Opinionated and secure by default:
Azure RBAC authorization only (no legacy access policies), purge protection
on, 90-day soft delete, network default-deny with trusted-services bypass.
Role assignments, rotation-enabled keys, secrets and self-signed certificate
scaffolding all hang off one module call — with data-plane objects sequenced
after RBAC grants so fresh deployments don't race role propagation. Works with
Terraform and OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/azurerm | >= 4.0, < 5.0 |
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference unlock after purchase
The complete copy-paste usage, the full input/output reference, and operational notes ship with your licence - shown here and bundled in the download.
- Usage
- Inputs
- Outputs
- Notes
Related modules
Cloud KMS Keyring & Keys
Keyrings and rotation-enabled crypto keys with per-key IAM for CMEK across GCS, BigQuery, Cloud SQL and disks.
KMS Key with Policy Patterns
Customer-managed KMS keys with sane key policies, aliases, rotation, and multi-region replicas.
Secret Manager Secrets
Secrets with versions, replication policy, rotation schedules, expiry and accessor IAM.
Secrets Manager Secret
Secrets with versioning, resource policies, replication, and optional Lambda rotation scaffolding.
Vault Policies & Auth
Vault policies, auth backends, and secret engine configuration as code.
Vault, Keys & Secrets
KMS vault with HSM/software master keys, key rotation and secret lifecycle management for app credentials.