Azure SQL Database
Logical SQL server + database with Entra-only auth, firewall/private endpoint, auditing, TDE and failover-group option.
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-08-04 · 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-sql-database-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/azure-sql-database/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle azure-sql-database-1.0.0.sigstore.json \
azure-sql-database-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "a7b2e2fb4cea8225b610c98414bd53acf9a4caa9cf0d372f6bb627f5f2f86217 azure-sql-database-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "sql_database" {
source = "www.iac-bazaar.com/iac-bazaar/azure-sql-database/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.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/azure-sql-database?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Azure SQL Database](https://www.iac-bazaar.com/catalog/azure-sql-database?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "sql_database" {
source = "www.iac-bazaar.com/iac-bazaar/azure-sql-database/azure"
version = "1.0.0"
}
```Preview:
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-sql-database
Logical SQL server + database with Entra-only auth, firewall/private endpoint,
auditing, TDE and a failover-group option. Works with Terraform and
OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.
Secure defaults:
- Public network access off (bring a private endpoint, or opt in to the public endpoint + firewall rules)
- Minimum TLS 1.2, transparent data encryption on
- Entra (Azure AD) admin with
azuread_authentication_only = trueby default — no SQL passwords anywhere - Serverless General Purpose SKU by default: scales to zero cost when idle
- System-assigned managed identity on the server (needed for auditing/CMK)
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/azurerm>= 4.0, < 5.0(built against 4.76)- The failover partner server must already exist (pass its resource ID); pair two instances of this module for a full active/standby pair.
- Look up the Entra admin
object_idyourself (azuread provider or portal) — this module deliberately avoids a second provider dependency.
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
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
- Inputs
- Outputs
Related modules
azure-database-migration
An Azure Database Migration Service instance placed in a subnet that must reach both source and target, on the Premium SKU that runs online migrations with continuous sync so a cutover is minutes (the Standard tiers are offline), with a migration project per source and target pair from a map. Tasks and credentials are supplied when a migration runs, not here.
azure-databricks
The default deployment puts the clusters in a managed network you cannot see with a public IP per node, and the workspace URL - notebooks, jobs, tokens - is reachable from the internet. VNet injection into your subnets with no public IPs, the workspace endpoint off the internet, and one Key Vault key wired to all four encryption settings including the DBFS root, a separate resource.
azure-data-explorer
The Dev(No SLA) SKUs say it in the name and are what a proof of concept becomes production on; public network access is on by default; disk and double encryption are off by default and set only at creation. Standard SKU with two instances across zones, private endpoints, both encryption layers on, a customer-managed key, and purge enabled because it is the only way to honour an erasure request.
azure-sql-managed-instance
The public data endpoint turns a private database into one listening on the internet on port 3342; SQL logins put an administrator password in state when Entra-only authentication would remove them entirely; and zone redundancy is off by default. Private, Entra-only with SQL authentication accepted by name, Business Critical across zones, TLS 1.2, and geo-zone-redundant backups.
azure-powerbi-embedded
A Power BI Embedded Gen2 capacity with the administrators who may assign workspaces named (required), in the size you chose with no default because the capacity bills by the hour from creation whether a report is rendered or not. Workspaces are assigned to the capacity in Power BI, which is an admin action outside the module.
azure-search-service
One replica - the default - is excluded from the availability SLA; the admin key, on by default, reads and writes every index and is revoked only by regenerating it for everyone; and the query endpoint is public by default. Three replicas, Entra ID only, private endpoint, 0.0.0.0/0 refused in the allow list, and optional enforcement that refuses an index without a customer-managed key.