Azure Enterprise Baseline
The BuiltForProd Azure Enterprise Baseline is the Azure landing zone your workloads run on: 15 subscriptions under one management-group tree, a hub-and-spoke network, guardrail policies, security and audit services, and the pipelines that change all of it. It is engineered around the Azure Well-Architected Framework and deployed as code into your own Microsoft Entra ID tenant.
It is one of three editions of the BuiltForProd Baseline, alongside the AWS and GCP Enterprise Baselines. Every edition solves the same problem, a foundation that is secure, repeatable and owned by the team that runs on it, using the native mechanisms of its cloud.
What it deploys
| Area | What the code creates |
|---|---|
| Organization | The management group mg-acme with mg-acme-core and mg-acme-plat beneath it, eleven core subscriptions that run the landing zone (root, audit, security, identity, network, DNS, artifacts, automation, backup, corporate and public) and four platform subscriptions where workloads live, one per stage: sandbox, dev, staging and prod |
| Guardrails | Azure Policy initiatives assigned at mg-acme: guardrails that hold for every subscription, a region restriction, a tag policy, and the Microsoft cloud security benchmark and a SOC 2 baseline initiative. Further compliance initiatives, such as CIS, NIST SP 800-53, PCI DSS and ISO 27001, are one switch each |
| Identity | Microsoft Entra ID groups mapped to Azure role-based access control (RBAC), Conditional Access policies, and Privileged Identity Management for the admin roles as an option. Pipelines sign in from GitHub Actions with federated identities, so no client secret exists |
| Network | A hub virtual network with Azure Firewall as the egress point, spoke networks peered to it, private DNS zones with a DNS Private Resolver, and separate prod and nonprod isolation domains. Every address range comes from one address plan, vnet_map.yaml. A point-to-site VPN for engineers is one switch |
| Security | Microsoft Defender for Cloud plans for containers, storage, Key Vault and Resource Manager in every subscription, findings and alerts routed to the security subscription, and the Center for Internet Security (CIS) activity-log alerts |
| Audit | An audit Log Analytics workspace and immutable audit storage encrypted with a customer-managed key, in the audit subscription |
| Workload contract | A platform Key Vault per stage that publishes the landing-zone values blueprints read at plan time: subnet IDs, DNS zones, the registry and the deployer identities |
| Delivery | Azure Container Registry for images, self-hosted GitHub runners on Azure Container Apps that reach the private endpoints, and plan, apply and drift-detection workflows |
The home region is eastus2, and every regional resource name carries its short slug, eus2. Both are chosen before the first deployment. The architecture overview shows how the subscriptions, the network and the pipelines fit together.
Built to the BuiltForProd Standard
Every edition is measured against the same eight properties: Secure, Reliable, Observable, Scalable, Automated, Recoverable, Compliant and Operable. The BuiltForProd Standard defines each one. The bar is the same on every cloud. What differs between editions is which Azure mechanism meets it.
Delivered as code
The Baseline is Terragrunt over OpenTofu: reusable modules, and one small unit per piece of infrastructure that says which module to use, in which subscription and region, with which inputs. Every change is proposed as a pull request, planned and reviewed there, and applied on merge, with a required approval before production. Nothing is clicked together in a console. Infrastructure as code explains the approach, and landing zones explains why the subscription is the unit of isolation.
Set up by us, owned by you
The BuiltForProd team customizes the Baseline to your organization and deploys it. At handover you receive the repositories, the infrastructure code and the documentation, and from then on the foundation is yours to run and change. The Baseline product page describes the deployment options and what a handover includes.
The complete Azure Enterprise Baseline documentation is available to customers who hold it. Read the documentation overview for the concepts behind the Baseline, then sign in from the navigation bar, or contact BuiltForProd to discuss your Azure estate.