Parent: #811

✨ FEATURE — Governance & Guardrails (Environment + Dev Center Scoped)

Parent Epic

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

Milestone

M2 — First Environment Live (Non-Prod)

📝 Feature Description

Apply environment-specific governance and guardrails to Dev Box resources deployed within each environment’s Dev Center.

❓ Problem Statement

Without environment-aware guardrails, Dev Box adoption can lead to inconsistent SKU usage, cost overruns,
and compliance gaps—especially between prod and non-prod.

💡 Proposed Solution

Use environment configuration to apply:

• Azure Policy assignments per environment / Dev Center scope
• SKU and region restrictions
• Required tagging enforcement aligned to the landing zone standards
• Exception guidance for adoption vs production

🔀 Alternative Solutions

• Manual reviews and post-deployment audits
• Deny-heavy policies that block early adoption

🔧 Dev Box Component

• Infrastructure/Bicep Templates
• Documentation

👤 Use Case

Organizations enforce stricter controls in prod while maintaining agility in non-prod.

✨ Expected Benefits

• Predictable governance baseline
• Reduced risk and easier audits

Acceptance Criteria

• Governance differs between prod and non-prod
• Guardrails enforced automatically via IaC
• Exceptions guidance documented

Dependencies

• EPIC — Dev Box–Ready Landing Zone (FOUNDATION) governance standards exist
• FEATURE — Multi-Environment Configuration Framework

Definition of Done

• Policies validated per environment
• Documentation published