Skip to main content

Azure

On Azure, BuiltForProd delivers the Azure Enterprise Baseline and the Azure blueprints, all production-ready. The Baseline is a production-ready Azure foundation engineered around the Azure Well-Architected Framework; the blueprints are working workloads on top of it. Each has a public overview and a full documentation set for customers who hold it.

What the Azure offering includes​

ProductRepositoriesOverview
Azure Enterprise Baselineacme-azure-platform-baselineAzure Baseline overview
Web App Blueprintacme-azure-blueprint-webapp-infra, -code, -gitopsWeb App Blueprint overview
Data and ETL Blueprintacme-azure-blueprint-etl-infra, -codeData and ETL Blueprint overview
Secrets Blueprintacme-azure-blueprint-secretsSecrets Blueprint overview
Relational App Blueprintacme-azure-blueprint-relapp-infra, -codeRelational App Blueprint overview
Multi-tenant SaaS Blueprintacme-azure-blueprint-saas-infra, -codeMulti-tenant SaaS Blueprint overview
Serverless and Integration Blueprintacme-azure-blueprint-serverless-infra, -codeServerless and Integration Blueprint overview
Warehouse and BI Blueprintacme-azure-blueprint-analytics-infra, -codeWarehouse and BI Blueprint overview
GenAI RAG Assistant Blueprintacme-azure-blueprint-rag-infra, -codeGenAI RAG Assistant Blueprint overview
Agentic AI Platform Blueprintacme-azure-blueprint-agents-infra, -codeAgentic AI Platform Blueprint overview
VM Migration Landing Blueprintacme-azure-blueprint-vmlanding-infraVM Migration Landing Blueprint overview
Backup and DR Blueprintacme-azure-blueprint-backupdr-infraBackup and DR Blueprint overview
FinOps Cost Analytics Blueprintacme-azure-blueprint-finops-infraFinOps Cost Analytics Blueprint overview
Observability Blueprintacme-azure-blueprint-observability-infraObservability Blueprint overview
Azure Virtual Desktop Blueprintacme-azure-blueprint-avd-infraAzure Virtual Desktop Blueprint overview

The acme prefix is the namespace and changes per customer. The blueprint catalog lists every blueprint.

The Baseline on Azure​

One Microsoft Entra tenant with 15 subscriptions under three management groups: mg-acme at the top with acme-core-root directly beneath it, mg-acme-core with ten single-purpose shared subscriptions (audit, security, identity, network, dns, artifacts, auto, backup, corp, public) and mg-acme-plat with sandbox, dev, staging and prod. A hub VNet in acme-core-network peers with one spoke VNet per stage; Azure Firewall in the hub carries egress and keeps the prod and nonprod isolation domains apart, and a NAT gateway per spoke is the alternative egress mode. Azure Policy at mg-acme denies what must never happen, Microsoft Defender for Cloud plans run per subscription, and the Activity Log of every subscription lands in immutable audit storage in acme-core-audit. People get Azure RBAC through 13 ACME_* Entra groups plus ACME_BreakGlass; pipelines sign in with one federated managed identity per repository. The architecture overview has the diagram and the subscription table; the Baseline product page has the deployment options.

The blueprints on Azure​

  • Web App: AKS with a private API server, Azure CNI Overlay with Cilium and Node Auto Provisioning; the managed NGINX ingress; Front Door with a web application firewall as the only public entry; Cosmos DB for MongoDB vCore and Azure Managed Redis behind private endpoints, reached with Microsoft Entra tokens; External Secrets, cert-manager and ArgoCD; a Flask API and React front end; a GitOps repository ArgoCD syncs.
  • Data and ETL: an Azure Data Lake Storage Gen2 lake with raw, processed, curated and managed zones; an Azure Databricks workspace with Unity Catalog and the Databricks job; an Event Grid system topic, a Storage queue and an event-driven Container Apps job that starts the job.
  • Secrets: SOPS-encrypted files per application per stage, Key Vault keys per stage, and a sync to the application Key Vault of each stage.
  • Relational App: a containerized API on App Service with slot-swap releases, Azure SQL Database with Entra-only access and a single-page front end behind Front Door.
  • Multi-tenant SaaS: a multi-tenant web app on App Service with a host name per tenant behind Front Door: row-level security in Azure SQL Database, Microsoft Entra External ID sign-in with membership by invitation, a control plane that onboards, meters and offboards tenants, and dedicated stacks for premium tenants.
  • Serverless and Integration: an orders API behind API Management on Azure Functions Flex Consumption, with a Durable Functions workflow, Service Bus queues with dead-letter replay, an Event Grid topic and serverless Cosmos DB, private in staging and prod.
  • Warehouse and BI: a Microsoft Fabric capacity, lakehouse and warehouse per stage, with SQL marts and a Power BI report deployed by the pipeline.
  • GenAI RAG Assistant: a chat assistant behind Microsoft Entra sign-in that answers from your documents with citations, using Azure AI Search, Azure OpenAI models and an evaluation gate.
  • Agentic AI Platform: an operations assistant on Foundry Agent Service that answers from its MCP tools and runs every write only after the signed-in user confirms it, with an evaluation gate.
  • VM Migration Landing: an Azure Migrate project and a rehost resource group where migrated servers land on Azure VMs, golden Ubuntu and Windows Server images built by VM Image Builder with a sample fleet, and Azure Update Manager patch windows, monitoring agents and backups from day one.
  • Backup and DR: an Azure Backup vault in every stage with daily vaulted backups and backup audits, locked, geo-redundant and behind multi-user authorization in staging and prod, where a monthly tested restore alerts on failure.
  • FinOps Cost Analytics: monthly budgets and cost anomaly alerts in every stage, tag inheritance and saved cost views, and FOCUS cost exports read by Power BI reports and a monthly review script.
  • Observability: service level objectives with two-window burn-rate alerts, availability tests from three locations, Azure Monitor workbooks, a Prometheus workspace and an OpenTelemetry endpoint for each stage, alerting the stage action group.
  • Azure Virtual Desktop: a pooled Azure Virtual Desktop host pool whose session hosts the service builds, updates and scales itself, a workspace with one full Windows 11 desktop, FSLogix profiles on Azure Files over Microsoft Entra Kerberos and Azure Virtual Desktop Insights.

The blueprints page explains how each reads the Baseline through its contract Key Vault and how to customize it.

Azure services and tools used​

The Baseline and blueprints use management groups, subscriptions, resource groups and locks, Microsoft Entra ID, Azure RBAC, Privileged Identity Management, Conditional Access, managed identities, Azure Policy, Microsoft Defender for Cloud, Microsoft Sentinel, Key Vault, Azure DDoS Protection, Azure Web Application Firewall, Virtual Network and peering, route tables, Azure Firewall, NAT Gateway, Azure Virtual Network Manager, Private Link, Azure Private DNS, DNS Private Resolver, Azure DNS, VPN Gateway, Network Watcher, Azure Front Door, Azure Monitor, Log Analytics, Application Insights, Azure Storage, Azure Data Lake Storage, Azure Container Registry, Azure Container Apps, AKS with Node Auto Provisioning and application routing, Cosmos DB for MongoDB vCore, Azure Managed Redis, Event Grid, Azure Databricks and Unity Catalog. The Backup and DR, Observability and FinOps Cost Analytics blueprints add Azure Backup (Backup vaults, the Resource Guard for multi-user authorization, vaulted blob and Data Lake Storage backups), Azure Automation for the restore test, an Azure Monitor workspace with managed Prometheus, Azure Monitor scheduled query alerts for SLO burn rates, Application Insights availability tests and smart detection, the optional Azure Managed Grafana, and Cost Management exports, budgets, anomaly alerts and saved cost views, with Power BI reports over the exports. The Multi-tenant SaaS, Serverless and Integration, VM Migration Landing and Azure Virtual Desktop blueprints add Azure App Service, Azure SQL Database, Microsoft Entra External ID, Azure Logic Apps, Azure Functions on the Flex Consumption plan with Durable Functions, API Management, Service Bus, Event Grid topics, serverless Cosmos DB, Azure Migrate, Azure Site Recovery (optional), Azure Compute Gallery, VM Image Builder, Azure Update Manager, Azure Load Balancer, Azure Virtual Desktop and Azure Files. Around them: OpenTofu, Terragrunt, GitHub Actions with OIDC federation, SOPS, ArgoCD, Helm, Kubernetes, cert-manager, the External Secrets Operator, Checkov, Trivy, tflint, Infracost, pre-commit and Docker. The Azure services used index links each service it covers to a short explainer of what it does and where the platform uses it.

Tooling versions​

ToolPinned version
OpenTofu1.12.6
Terragrunt1.1.6
hashicorp/azurerm~> 5.7
hashicorp/azuread~> 3.10 (Baseline)
Azure/azapi~> 2.13 (Baseline)
Other providershashicorp/time ~> 0.13, helm ~> 3.3, kubernetes ~> 3.2, random ~> 3.7, databricks/databricks ~> 1.135
tflintv0.64.0, with tflint-ruleset-azurerm 0.32.0

No registry module is used: every module lives in its repository. Every GitHub Action is pinned to a commit SHA; the release notes list the versions.

Purchasing​

The Azure products are purchased directly from BuiltForProd, set up by the BuiltForProd team and handed over with their repositories and documentation. The steps and the license are on purchasing and licensing.