🎯 EPIC — Dev Box–Ready Landing Zone (FOUNDATION)

[Evilazaro]

🎯 EPIC — Dev Box–Ready Landing Zone (FOUNDATION)

Milestone

M0 — Platform Readiness & Guardrails Locked

🎯 Epic Objective

Establish the minimum viable Azure Landing Zone foundation required to safely deploy, adopt,
govern, and operate Microsoft Dev Box across multiple environments (prod and non-prod).

📝 Feature Description

This Epic delivers a Dev Box–Ready Landing Zone by providing:

• Identity and access foundations
• Subscription and scope boundaries (prod vs non-prod)
• Naming and tagging standards
• Adoption-first networking baseline
• Lightweight governance guardrails
• Baseline logging and diagnostics

Completion of this Epic is a hard prerequisite for Dev Box enablement Epics.

❓ Problem Statement

Dev Box adoption fails or stalls when foundational Landing Zone components are missing, incomplete,
or assumed to exist. This results in governance blockers, security concerns, networking issues,
and operational instability during developer onboarding.

💡 Proposed Solution

Deliver a minimal, opinionated Landing Zone foundation aligned to Dev Box requirements,
implemented via Infrastructure as Code and documented as explicit accelerator assumptions.

🚫 Out of Scope / Non-Goals

• Full CAF management group hierarchy implementation
• Enterprise firewall / complex hub-spoke reference implementations
• SIEM/SOC integrations
• Advanced FinOps tooling and chargeback systems

🔧 Dev Box / DevEx Components

• Identity & Access
• Networking
• Governance & Policy
• Monitoring & Diagnostics
• Infrastructure / Bicep Templates
• Documentation

👤 Use Cases

Platform teams want to deploy Microsoft Dev Box quickly and safely without rebuilding a full enterprise landing zone,
while still meeting baseline security, governance, and operational expectations.

✨ Expected Benefits

• Faster Dev Box adoption by removing foundational blockers
• Reduced ambiguity on prerequisites and ownership boundaries
• Lower operational risk and clearer governance posture

Success Metrics (Exit Criteria)

• Dev Box prerequisites satisfied and validated
• No Dev Box enablement work blocked by missing foundation components
• Foundation assumptions documented and published

Dependencies & Assumptions

• Azure tenant exists
• Microsoft Entra ID is available
• Platform team owns subscription provisioning and baseline policies

Definition of Done (Epic-Level)

• All child Features and Tasks completed
• Foundation validated in at least one environment
• Documentation published