Azure Standard Load Balancer (L4)
An Azure Standard L4 load balancer with a self-created static public IP frontend, a backend address pool, health probes and load-balancing rules - Standard SKU throughout.
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)
- No applicable security policies for this provider
- 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-load-balancer-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/azure-load-balancer/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle azure-load-balancer-1.0.0.sigstore.json \
azure-load-balancer-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "a07fdf492980c736a37836b4fb1b21e976b54afe893d0b8d20ebab8f107536f3 azure-load-balancer-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "load_balancer" {
source = "www.iac-bazaar.com/iac-bazaar/azure-load-balancer/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-load-balancer?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Azure Standard Load Balancer (L4)](https://www.iac-bazaar.com/catalog/azure-load-balancer?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "load_balancer" {
source = "www.iac-bazaar.com/iac-bazaar/azure-load-balancer/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-load-balancer
An Azure Standard L4 (Layer-4) Load Balancer with a self-created static
public IP frontend, a backend address pool, health probe(s) and load-balancing
rule(s). Consumes an existing resource group. Works with Terraform and
OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.
What it provisions
azurerm_public_ip— Standard SKU, static allocation, IPv4 (the LB frontend)azurerm_lb— Standard SKU, one public frontend IP configurationazurerm_lb_backend_address_pool— one pool; attach NICs/VMs/VMSS out of bandazurerm_lb_probe— one perprobesentry (default: a single TCP probe on 80)azurerm_lb_rule— one perrulesentry (default: TCP 80 -> 80 via the probe)
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.
- Secure / modern defaults
- Usage
- Inputs
- Outputs
- Requirements & notes
Related modules
azure-application-gateway
Regional L7 load balancer with WAF v2 policy, TLS termination from Key Vault, autoscaling and health probes.
azure-front-door
Global entry point: Front Door profile, endpoints, origin groups, custom domains with managed TLS and WAF policy.
azure-traffic-manager
Global, DNS-based load balancing with a Traffic Manager profile and map-driven external endpoints - Performance, Priority, Weighted, Geographic, Subnet or MultiValue routing with an HTTPS health probe.
tencent-clb
A listener's health check is a switch that, off, sends traffic to every target forever; a port-80 listener forwards unless a redirection resource points it at 443; and delete_protect defaults to false. HTTP health checks on a path through listener rules, a 301 from 80 to 443 whenever a certificate is given, deletion protection on, access logs when a CLS topic is given.
huawei-elb
The default TLS policy accepts TLS 1.0; a pool without a monitor resource is never unhealthy and sends traffic to every member forever; an HTTPS listener does nothing about port 80 until an L7 policy redirects it; and deletion protection is off. tls-1-2-strict, an HTTP monitor on a path, a redirect on 80 whenever a certificate is given, two zones unless one is accepted, deletion protection on.
vultr-load-balancer
The default health check is TCP on the backend port, which a process that stopped serving still passes; ssl_redirect defaults to false, so the site stays in clear on 80; and a balancer with no instances is a public address that fails. HTTP checks on a path, redirect on whenever HTTPS exists, backends required, and a Let's Encrypt certificate from auto_ssl_domain rather than a pasted key in state.