🎯 EPIC 1 — Dev Box Adoption & Deployment (Multi-Environment, Multi-Dev Center)

[Evilazaro]

🎯 EPIC 1 — Dev Box Adoption & Deployment (Multi-Environment, Multi-Dev Center)

Milestone

M2 — First Environment Live (Non-Prod)

🎯 Epic Objective

Expedite Microsoft Dev Box adoption by providing a secure, repeatable accelerator that supports
deploying separate Dev Centers per environment (prod and non-prod), enabling self-service Dev Boxes
with environment-aware configuration, governance, and identity controls.

📝 Feature Description

This Epic delivers a production-ready Dev Box adoption path that supports:

• One Dev Center per environment (recommended default)
• Environment-aware configuration (prod vs non-prod)
• Dual identity model (deployment vs operational)
• Project-scoped Dev Box access and delegation
• Automated, repeatable deployments using a single codebase

All capabilities are delivered using Infrastructure as Code (Bicep), automation (PowerShell),
and documentation.

❓ Problem Statement

Dev Box adoption is slow and inconsistent when identity, environment separation, governance, networking,
and operational readiness are treated as one-off decisions. This leads to duplicated deployments,
security risks, governance gaps, and operational complexity.

💡 Proposed Solution

Provide a Dev Box accelerator that:

• Enforces identity readiness as the P0 adoption gate
• Uses a centralized multi-environment configuration framework
• Deploys environment-scoped Dev Centers with project-scoped Dev Box RBAC
• Applies environment-specific governance, networking, image strategy, and diagnostics
• Enables one-command deployments and repeatable onboarding

🚫 Out of Scope / Non-Goals

• Custom per-team CI/CD pipelines
• Snowflake architectures per team/environment
• Non–Dev Box workload enablement
• Manual approval-heavy onboarding processes

🔧 Dev Box / DevEx Components

• Infrastructure / Bicep Templates
• PowerShell Scripts
• Configuration Management
• Networking
• Identity & Access
• Monitoring & Diagnostics
• Dev Box
• Documentation

👤 Use Cases

• Platform teams deploy Dev Box consistently across prod and non-prod.
• Developers self-serve Dev Boxes appropriate to their environment and project.
• Security/ops validate compliance, visibility, and operational readiness from day one.

✨ Expected Benefits

• Faster Dev Box rollout across environments
• Clear separation between prod and non-prod through separate Dev Centers
• Reduced duplication and drift
• Scalable governance and operations

Success Metrics (Exit Criteria)

• Dev Centers deployed for prod and non-prod using the same accelerator
• Identity adoption gate passed end-to-end
• Developer onboarding succeeds without manual RBAC intervention
• Environment tagging and cost visibility enabled

Dependencies & Assumptions

• EPIC — Dev Box–Ready Landing Zone (FOUNDATION) completed
• Environment naming/tagging standards exist
• Entra ID group strategy agreed

Definition of Done (Epic-Level)

• All child features completed
• Multi-environment + multi-Dev Center deployment validated
• Documentation published and validated