✨ FEATURE — Dev Center & Dev Box Platform Baseline (Per Environment)

[Evilazaro]

Parent: #811

✨ FEATURE — Dev Center & Dev Box Platform Baseline (Per Environment)

Parent Epic

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

Milestone

M2 — First Environment Live (Non-Prod)

📝 Feature Description

Deploy a separate Dev Center per environment using environment-aware configuration, and provision
Dev Box projects and baseline pools consistently within each environment.

❓ Problem Statement

Using a single Dev Center for all environments increases blast radius and complicates governance and RBAC separation.

💡 Proposed Solution

Use the environment configuration framework to deploy:

• One Dev Center per environment (prod and non-prod)
• Projects within each Dev Center
• Baseline pools per project as needed
• Consistent naming, tagging, and diagnostics

🔀 Alternative Solutions

• Single shared Dev Center with project-only separation
• Manual Dev Center creation per environment

🔧 Dev Box Component

• Infrastructure/Bicep Templates
• Dev Box
• Documentation

👤 Use Case

Platform teams deploy isolated Dev Centers for prod and non-prod using a single accelerator.

✨ Expected Benefits

• Strong environment isolation
• Reduced blast radius
• Clear operational boundaries

Acceptance Criteria

• Dev Centers deployed per environment
• Projects and pools created in correct Dev Center
• Same modules reused across environments

Dependencies

• FEATURE — Multi-Environment Configuration Framework
• Deployment identity validated

Definition of Done

• Dev Centers validated in prod and non-prod
• Documentation published