Service Bus Namespace, Queues & Topics
An Azure Service Bus namespace with queues, topics and subscriptions on the Standard SKU - SAS local auth off (Entra ID + RBAC), TLS 1.2+ minimum, and dead-lettering of expired messages.
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-30 · 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-service-bus-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/azure-service-bus/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle azure-service-bus-1.0.0.sigstore.json \
azure-service-bus-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "916fa6c9aefa7e759806a339e678f43c89684e977052d99f7366b6adb846111d azure-service-bus-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "service_bus" {
source = "www.iac-bazaar.com/iac-bazaar/azure-service-bus/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-service-bus?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Service Bus Namespace, Queues & Topics](https://www.iac-bazaar.com/catalog/azure-service-bus?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "service_bus" {
source = "www.iac-bazaar.com/iac-bazaar/azure-service-bus/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-service-bus
Azure Service Bus namespace with queues, topics and topic subscriptions —
enterprise messaging done right. Defaults to the Standard SKU so topics and
subscriptions work (Basic has queues only). Secure by default: SAS local auth
off (Microsoft Entra ID + Azure RBAC), TLS 1.2+ minimum, and queues /
subscriptions dead-letter expired messages so nothing is silently dropped.
Premium-only knobs (dedicated capacity, messaging partitions, large messages)
are gated so a Standard namespace plans cleanly. Works with Terraform and
OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.
Security notes
- SAS off by default (
local_auth_enabled = false): authenticate clients with Entra ID and assign data roles such asAzure Service Bus Data Sender/Azure Service Bus Data Receiver. Creating queues/topics is a control-plane (ARM) operation and works regardless of this flag — only data-plane SAS keys are affected. Settrueonly if a client cannot use Entra ID. - TLS 1.2+ enforced via
minimum_tls_version. - Dead-lettering on expiration is on by default for queues and subscriptions so expired messages are captured for redrive, not lost.
- Private networking (
public_network_access_enabled = false, private endpoints, IP/VNet rules) requires the Premium SKU — the namespace ships with a public endpoint on Basic/Standard. - SKU guards: the module fails fast at plan time if you define topics on a
Basic namespace, or
max_message_size_in_kilobyteson a non-Premium one.
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 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-iot-hub
Shared access keys are symmetric credentials that grant everything their policy names and are revoked only by regeneration; the endpoint is public by default; telemetry that matches no route is dropped when the fallback route is off; and the built-in endpoint keeps one day. Keys off, private endpoints, TLS 1.2, the fallback route on so unrouted telemetry lands, and seven days of retention.
azure-communication-email
Azure Communication Services email from your own domain: the email service, the domain with the DNS records to publish exported, sender addresses as a map, and the Communication Services resource that sends. CustomerManaged rather than the random azurecomm.net subdomain (accepted by name), engagement tracking off, and the key-based connection string sensitive; managed identity is the better path.
azure-event-grid
An Event Grid custom topic plus event subscriptions with an optional in-module Storage Queue target - SAS auth off (Entra ID), a system-assigned identity, and HTTPS-only TLS 1.2+ storage.
azure-event-hubs
An Event Hubs namespace plus hubs, each with consumer groups and least-privilege SAS rules for high-throughput (Kafka-compatible) ingestion - TLS 1.2 floor and optional default-deny networking.
aws-mq
deployment_mode defaults to SINGLE_INSTANCE, and Amazon MQ reboots the instance to patch it - so a single broker has planned downtime on AWS's schedule. Active/standby across two AZs, both log streams on, and passwords in a separate variable from users, because a sensitive value cannot be a for_each argument at all.
aws-kinesis-firehose
Without error_output_prefix, records Firehose could not process are written into the same prefix as the ones it could, wrapped in an error envelope that whatever reads the prefix treats as data. Nothing reports it.