Jenkins Controller on Azure (VM)
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.
This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.
Provider drift
This module's own ceiling currently holds it below a release that has already shipped. It still applies exactly as before, against the newest version it allows. What it cannot reach is anything added in the newer major.
| Provider | This module allows | Newest it accepts | Newest released |
|---|---|---|---|
| hashicorp/azurerm | >= 4.0, < 5.0 | 4.81.0 | 5.3.0 |
Measured 2026-09-01 against the Terraform registry. The whole catalogue is on provider freshness.
What depends on this
No reference architecture names this module, so changing it affects only configurations that reference it directly.
Nearest alternatives
Same cloud, same category. These are what you would weigh against it without changing provider.
The same job on other clouds
This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.
Installing it
module "azure_jenkins" {
source = "www.iac-bazaar.com/iac-bazaar/azure-jenkins/azure"
version = "1.1.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.