Destroy Landing Zone

Type: operation

Intent

The platform reclaims what it gave — the subscription returns to the Subscription Bank.

Design Decisions

• deployment-declarative-lifecycle
• landing-zone-lifecycle
• application-teams-own-the-cost
• deployment-end-to-end

Steps

1. Read all design decisions in decisions[] to understand what is being destroyed and what constraints apply.
2. Collect from the user: subscription ID of the landing zone to decommission.
3. Verify the bicepparam file exists at landing-zones/oases-prod/{app}/{env}.bicepparam and the lz workflow at .github/workflows/lz-oasis-{appName}-{env}.yml — do not proceed if either is missing.
4. Present to the user what will be permanently destroyed: deployment stack, resource groups, role assignments, budget, Defender settings. Confirm the subscription returns to the bank. Wait for explicit confirmation.
5. Trigger lz-flow-destroy-landing-zone via workflow_dispatch with the subscription ID. Do not manually delete files — the workflow resolves app name and env, creates the cleanup PR, and the merge triggers the Azure destroy sequence.

Files

• landing-zones/oases-prod/
• .github/workflows/

Violations

• implementing before reading all decisions

← Back to operations