Azure Landing Zone Architect
Purpose
Design or review Azure landing zones with an operator-grade focus on structure, dependencies, and blast radius.
This skill is for platform decisions that cut across:
- management groups,
- subscriptions,
- platform versus application landing zones,
- identity and access boundaries,
- network topology and shared services,
- governance and policy inheritance,
- security baselines,
- management, monitoring, backup, and recovery posture.
When to use
Use this skill when the user asks for:
- a greenfield Azure landing-zone design,
- a brownfield hierarchy or subscription-placement critique,
- shared-services or platform-subscription layout advice,
- a hub-spoke or alternative connectivity decision in landing-zone context,
- a review of whether governance, security, and operations dependencies were missed,
- clarification of platform-team versus application-team ownership boundaries.
Do not use this skill for:
- narrow RBAC assignment questions with no platform-design component,
- single-service implementation tutorials,
- writing production Bicep or Terraform on first pass,
- workload-only design questions that do not affect the platform operating model.
Lean operating rules
- Prefer live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and sanitized user evidence.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
References
Load these only when needed:
- MCP and evidence path - use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
- Workflow and output contract - use when executing the full review, applying stress checks, or formatting the final answer.
- Official sources - use when you need the detailed Microsoft documentation list or source notes.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- the assumptions or blockers that prevent stronger conclusions.
1---2name: techtide-azure-landing-zone-architect3description: Use this skill for Azure landing-zone design, management-group and subscription hierarchy reviews, platform-versus-application boundary decisions, or multi-subscription Azure platform architecture critiques that span governance, identity, networking, security, and operations.4---56# Azure Landing Zone Architect78## Purpose910Design or review Azure landing zones with an operator-grade focus on structure, dependencies, and blast radius.1112This skill is for platform decisions that cut across:1314- management groups,15- subscriptions,16- platform versus application landing zones,17- identity and access boundaries,18- network topology and shared services,19- governance and policy inheritance,20- security baselines,21- management, monitoring, backup, and recovery posture.2223## When to use2425Use this skill when the user asks for:2627- a greenfield Azure landing-zone design,28- a brownfield hierarchy or subscription-placement critique,29- shared-services or platform-subscription layout advice,30- a hub-spoke or alternative connectivity decision in landing-zone context,31- a review of whether governance, security, and operations dependencies were missed,32- clarification of platform-team versus application-team ownership boundaries.3334Do not use this skill for:3536- narrow RBAC assignment questions with no platform-design component,37- single-service implementation tutorials,38- writing production Bicep or Terraform on first pass,39- workload-only design questions that do not affect the platform operating model.4041## Lean operating rules4243- Prefer live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and sanitized user evidence.44- Separate confirmed facts from inference. If state was not queried or shown, say so.45- Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.46- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.4748## References4950Load these only when needed:5152- [MCP and evidence path](references/mcp-and-evidence.md) - use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.53- [Workflow and output contract](references/workflow-and-output.md) - use when executing the full review, applying stress checks, or formatting the final answer.54- [Official sources](references/official-sources.md) - use when you need the detailed Microsoft documentation list or source notes.5556## Response minimum5758Return, at minimum:5960- the scoped target and evidence level,61- the main risks or control gaps,62- the safest next actions,63- the assumptions or blockers that prevent stronger conclusions.
TechTideOhio