Context
Wombat's multi-provider Terraform coverage includes Azure alongside AWS, GCP, STACKIT, OVHcloud and Hetzner Cloud (framework v1.1.0).
Azure
Keep the Azure Cloud Adoption Framework and Well-Architected guidance, then add a provider-neutral control model for the workloads that do not live in one cloud.
- CAF and Well-Architected, plus a neutral baseline
- Framework control coverage
- 91 controls with provider-specific checks
- 4 relevant pillars
- 4 starting points
What Wombat adds to the provider view.
Azure teams already have a strong operating model. Wombat adds the cross-provider view: the same control IDs, scoring and evidence for Azure, AWS, GCP, STACKIT, OVHcloud and Hetzner Cloud.
The current framework control pack includes 91 controls with Azure-specific checks.
Context
Use the comparison page to see where Azure CAF and Wombat overlap, and where Wombat adds sovereignty and evidence coverage.
Context
The control catalogue is designed to be read across providers, not as a replacement for Azure-native guidance.
Azure quickstart
Keep the Azure provider and CAF guidance, then add the Wombat baseline for the same workload.
main.tf
terraform {
required_version = ">= 1.6.0"
required_providers {
azurerm = {
source = "hashicorp/azurerm"
version = "~> 3.100"
}
}
}
provider "azurerm" {
features {}
}
terminal
wombat check . --output jsonAuthenticate with the standard Azure CLI or service-principal environment variables. Pin the provider version to your approved version.
Known regions in the dashboard map.
Approximate locations only. The dashboard maps 48 region codes for this provider; below are the distinct locations in that map.
Approximate region locations from the dashboard map. Not a datacenter map.
Virginia, USA
California, USA
Washington, USA
Arizona, USA
Iowa, USA
Illinois, USA
Texas, USA
Wyoming, USA
Toronto, Canada
Quebec, Canada
São Paulo, Brazil
Dublin, Ireland
Amsterdam, Netherlands
London, UK
Cardiff, UK
Paris, France
Marseille, France
Frankfurt, Germany
Berlin, Germany
Oslo, Norway
Stavanger, Norway
Zurich, Switzerland
Geneva, Switzerland
Hong Kong
Singapore
Sydney, Australia
Melbourne, Australia
Tokyo, Japan
Osaka, Japan
Seoul, South Korea
Busan, South Korea
Pune, India
Chennai, India
Mumbai, India
Dubai, UAE
Abu Dhabi, UAE
Johannesburg, South Africa
Cape Town, South Africa
Doha, Qatar
Warsaw, Poland
Gävle, Sweden
Milan, Italy
Tel Aviv, Israel
UK Sovereign Cloud (London)
France Sovereign Cloud (Paris)
Germany Sovereign Cloud (Frankfurt)
Norway Sovereign Cloud (Stavanger)
Data and verification
Data status. The region labels for Azure are compiled from the WOMBATpass dashboard region map. The current extract is dated 31 Oct 2026. The page currently lists 48 region codes from that map.
Verification. The data has not been cross-validated with the provider. It may be incomplete, approximate or outdated.
Intended use. The information is provided for general orientation only. It is not a guarantee of service availability, a representation of exact datacenter locations, or a statement of provider certification.
Corrections. Providers and other parties may submit corrections — including the provider name, the affected region code or control count, and a public source — to page@wombat-gov.dev or open a correction issue ↗.
Trademarks. Provider names and trademarks are the property of their respective owners. Wombat is not affiliated with, endorsed by or sponsored by these providers; the names are used solely for identification.
License. The provider data on this page is published under CC BY 4.0. It is a derived compilation from the WOMBATpass dashboard and the Wombat framework control pack. Attribution: Wombat Community. The data is provided without warranty. Data license.
Methodology. Read the data methodology →
Pillars that matter on Azure.
The same control model applies across providers, so the comparison stays consistent when the estate does not.
WAF-SEC
Security
Entra ID boundaries, network controls, encryption and secure configuration are the core review surface.
Read the Security pillar →WAF-OPS
Operational Excellence
Azure estates need change control, observability and incident evidence that survives audit.
Read the Operational Excellence pillar →WAF-REL
Reliability
Zone redundancy, backup and recovery objectives should be scored against the workload.
Read the Reliability pillar →WAF-SOV
Sovereign
Data residency, key custody and provider concentration are procurement questions in regulated markets.
Read the Sovereign pillar →Control coverage by pillar.
Unique controls with provider-specific checks in the current framework control pack. A control may have multiple checks.
Snapshot of the current framework control pack; counts are not a certification. See the full coverage table →
Start here.
Use the provider-native guidance for depth, and the Wombat baseline for the cross-provider score, comparison and evidence.
Wombat vs. Azure CAF
Open →Controls catalogue
Open →WOMBATpass quickstart
Open →Trust center
Open →Score the Azure estate without losing the Azure view
Keep the CAF and Well-Architected reviews, then use the Wombat baseline to compare, evidence and track the same workload over time.