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-jenkins-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/azure-jenkins/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle azure-jenkins-1.0.0.sigstore.json \
azure-jenkins-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "bc775f895a3a828474e33a3a499d04cb67d1cad9866dc85a662de1b711b458f3 azure-jenkins-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "jenkins" {
source = "www.iac-bazaar.com/iac-bazaar/azure-jenkins/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-jenkins?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Jenkins Controller on Azure (VM)](https://www.iac-bazaar.com/catalog/azure-jenkins?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "jenkins" {
source = "www.iac-bazaar.com/iac-bazaar/azure-jenkins/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-jenkins
Jenkins installs asynchronously via cloud-init after the VM boots, so the apply completes before Jenkins is reachable. Poll the endpoint rather than assuming it is up when Terraform returns.
A fully self-contained Jenkins controller on a single Azure Linux VM. One
tofu apply creates everything — resource group, virtual network, subnet, NSG,
NIC, an optional public IP and the VM — and bootstraps Jenkins via cloud-init.
tofu destroy removes all of it (including the resource group). Works with
Terraform and OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.
What it provisions
azurerm_resource_group(created and destroyed by this module)azurerm_virtual_network+azurerm_subnetazurerm_network_security_group— SSH (22) and the Jenkins UI (jenkins_port) allowed only fromallowed_source_cidr, plus an explicit DenyAllInboundazurerm_network_interface(+ NSG association at both the NIC and the subnet)- optional
azurerm_public_ip(Standard, static;create_public_ip) azurerm_linux_virtual_machine(SSH-key-only, system-assigned identity, cloud-init Jenkins bootstrap)
Secure defaults
- SSH-key auth only —
disable_password_authentication = true; a validadmin_ssh_public_keyis required. - No open ingress by default —
allowed_source_cidris required (no default) and gates both SSH and the Jenkins UI; a catch-all rule denies everything else. - System-assigned managed identity for least-privilege role grants.
- OS disk encrypted at rest with platform-managed keys (always on in Azure).
- VM extension operations disabled (
allow_extension_operations = false) — Jenkins bootstraps via cloud-init, so the extension channel is unused attack surface. Setallow_extension_operations = trueif you attach extension-delivered agents (Azure Monitor, AAD SSH login, ...). Upgrade note: before this hardening the provider default (true) applied; existing deployments that rely on extensions must now opt in. - Optional Trusted Launch (Secure Boot + vTPM) for capable VM sizes
(
secure_boot_enabled/vtpm_enabled, off by default so the cheapest B1s size always applies).
License
Commercial — LicenseRef-IaCBazaar-Commercial
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
- Requirements & notes
Related modules
azure-chaos-studio
Chaos Studio has no stop condition: an experiment runs for its actions' duration or until somebody presses Stop, so the duration is the only guardrail and every action here is capped. The experiment acts as its own identity and fails safely without a role on each target; every fault it can inject is a capability somebody enabled on an onboarded target, so the scope cannot quietly widen.
azure-data-factory
The managed virtual network cannot be turned on after creation, and without it the integration runtime that copies your data reaches every source over public endpoints; the studio endpoint is public by default; and a factory with no git repository keeps its pipelines only in the service, with no review. Managed VNet on, studio private, git required, Key Vault linked for secrets.
azure-app-configuration
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.
ansible-azure-cli
The Azure CLI on EL 10 from Microsoft's rhel/10/prod repository, signed by the 2025 key: the key in most guides carries SHA-1 signatures and fails the GPG check, and the repository in most guides tops out at a 2022 build. Pinned, telemetry and the survey prompt off for every login shell; the live test asserts the SHA-1 key was never imported. Original role, live-tested on Rocky Linux 10.
azure-devops
Bootstraps an Azure DevOps project with an initialized Git repository and a YAML build pipeline - repeatable team setup as code.