Create Landing Zone

Type: operation

Intent

The platform hands over an isolated environment — from this point, the application team operates independently.

Design Decisions

• landing-zone-lifecycle
• application-teams-own-the-cost
• landing-zone-ipam
• landing-zone-template
• deployment-branch-gated-promotion

Steps

1. Confirm the application's file exists under platform-members/ — if not, the register-platform-member operation must be completed first.
2. Collect from the user: application name, environment (test or prod), management group name (oases-prod or oases-test), and budget (optional, default 100).
3. Auto-select the subscription ID: run `az account management-group subscription show-sub-under-mg --name subscription-bank --query "[0].name" -o tsv`.
4. Confirm the values with the user (including the auto-selected subscription ID), then trigger the workflow: gh workflow run requestNew-Landing-Zone.yml -f ApplicationName="{AppName}" -f Environment="{env}" -f ManagementGroupName="{mgmtGroup}" -f SubscriptionId="{subscriptionId}" -f Budget="{budget}" — this raises a pull request.
5. A platform engineer reviews and approves the pull request — approval is what triggers the automation to complete provisioning.

Files

• platform-members/

Violations

• implementing before reading all decisions

← Back to operations