azure-landingzone-generator

You can generate a CAF-compliant Azure landing zone by running the init command to scaffold the repository, then using the customer command with your specific code to produce modular hub-spoke topology templates in Bicep or Terraform.

A hub-spoke topology for Azure deployments centralizes shared services in a hub virtual network while isolating workloads in spoke networks, enabling modular, multi-subscription governance and reproducible infrastructure-as-code provisioning.

Yes, the landing zone generator is designed for enterprise-scale CAF deployments across multiple subscriptions and regions, requiring you to provide customer codes, subscription details, and environment names to produce production-ready templates.

Yes, you can choose between Bicep and Terraform for Azure landing zone scaffolding by providing your preferred IaC format as an input, which generates parameterized, idempotent templates enforcing naming, tagging, and governance.

Creating a production-ready Azure landing zone requires user-provided inputs including a customer code, subscription identifiers, target environment, and preferred IaC format to ensure the generated templates enforce proper governance and reproducibility.