landing-zone-template

Type: decision

Decision

Each landing zone has its own parameter file and dedicated trigger workflow.

Why

Acting on one landing zone would risk triggering another team's redeployment.

Violations

• Generated workflow name not matching lz-* prefix — breaks fan-out discovery.

Links

• landing-zone-platform-members — Without the platform member profile, the bicepparam file has no initial values to populate.
• deployment-logic-reusable-workflow — Without the reusable workflow, per landing-zone triggers cannot share centralized deployment logic.
• platform-identity-azure — Without the app registration's credentials, the template cannot deploy landing zone resources.
• landing-zone-repo — Without the application repo, environment-scoped variables have no destination after provisioning.

← Back to knowledge graph