landing-zone-template

Type: decision

Decision

Landing zones are stamped from a single shared template, but each is managed through its own dedicated parameter file and workflow.

Why

Without per-zone parameter files and workflows, a team couldn't act on their landing zone without risking triggering another's redeployment.

Links

• landing-zone-application-profile — Landing zone initial values come from the application profile.
• deployment-logic-reusable-workflow — Each landing zone has a dedicated workflow that passes parameters to the centralized template.
• platform-identity-azure — The platform identity is used to create and configure landing zone resources.
• platform-identity-graph — The landing zone identity receives Directory.Read.All at landing zone creation time.
• landing-zone-repo — landing zone provisioning writes environment scoped variables (resource ID) to the application repo.

← Back to all decisions