✨ FEATURE — Subscription & Scope Boundary Definition #813
Description
Parent: #810
✨ FEATURE — Subscription & Scope Boundary Definition
Parent Epic
🎯 EPIC — Dev Box–Ready Landing Zone (FOUNDATION)
Milestone
M0 — Platform Readiness & Guardrails Locked
📝 Feature Description
Define the minimal subscription and scope boundaries required to host Dev Box-related platform resources,
including separation between prod and non-prod.
❓ Problem Statement
Unclear scope boundaries cause governance confusion, RBAC sprawl, and cost visibility issues during Dev Box deployment.
💡 Proposed Solution
Define and document:
- Subscription strategy for prod/non-prod
- Resource group strategy for Dev Box platform resources
- Ownership and responsibility boundaries for platform vs workload teams
🔀 Alternative Solutions
- Single shared subscription with no documented boundaries
🔧 Dev Box Component
- Infrastructure / Bicep Templates
- Documentation
👤 Use Case
Platform teams know where Dev Center and supporting resources should live and how boundaries are enforced.
✨ Expected Benefits
- Clear governance scope
- Predictable RBAC and policy application
- Improved cost allocation
Acceptance Criteria
- Subscription strategy documented
- Prod/non-prod boundary explicit
- Ownership model documented
Dependencies
FEATURE — Identity Foundation (Landing Zone)
Definition of Done
- Scope model documented and approved