Purpose
Section titled “Purpose”Cost management makes cloud spend visible, attributable, and controllable across migration waves and steady-state operations.
For migration landing zones, this requires a shared financial control model across platform teams, application teams, and business stakeholders.
Core cost governance building blocks
Section titled “Core cost governance building blocks”- Costs and Billing (central domain): Use the cost and billing domain as the central baseline for spend transparency, governance responsibilities, and reporting logic. Documentation
- Billing Accounts: Define Billing Accounts as structural boundaries for ownership, invoicing context, and financial accountability. Documentation
- FOCUS: Use the FOCUS model to standardize and normalize cost data for transparent analysis and cross-team financial reporting. Documentation
- Resource Labeling: Enforce consistent labels to map technical usage to accountable teams, products, environments, and cost centers. Documentation
How these elements work together
Section titled “How these elements work together”- Financial structure layer: Billing Accounts define where costs are accumulated and who is accountable for them.
- Data standardization layer: FOCUS provides a consistent cost-data model across services and teams.
- Allocation and ownership layer: Resource labels connect cloud usage to business and engineering ownership.
- Operating layer (FinOps): FinOps establishes a recurring cycle of visibility, optimization actions, and accountability tracking.
FinOps in the landing zone context
Section titled “FinOps in the landing zone context”FinOps should be embedded from the beginning of landing zone design, not added after migration waves start.
- Visibility: Build shared transparency for platform, shared services, and workload spend.
- Accountability: Assign clear cost ownership per Billing Account, team, and service domain.
- Optimization: Maintain an active optimization backlog with regular review cadence.
- Governance: Tie budget thresholds and escalation paths to named owners and decision forums.
Key design decisions
Section titled “Key design decisions”- Allocation model boundaries: Define how spend is allocated across Billing Accounts, products, teams, and environments.
- Data model standardization: Decide how FOCUS and internal reporting dimensions are implemented consistently.
- Label strategy: Define mandatory labels and quality controls for reliable allocation and chargeback/showback.
- Budget and escalation model: Establish thresholds, ownership, and response workflows.
- FinOps cadence: Define review frequency, optimization governance, and tracking of realized savings.
Typical outputs
Section titled “Typical outputs”- Cost taxonomy and ownership model: Standardized mapping across Billing Accounts, labels, and responsible teams.
- Cost reporting baseline: FOCUS-aligned financial views for trend analysis and stakeholder reporting.
- Budget guardrails: Defined thresholds with documented escalation and decision ownership.
- FinOps operating model: Regular review rhythm with prioritized optimization backlog and outcome tracking.
Related Target Operating Model guidance
Section titled “Related Target Operating Model guidance”Governance and Decision Making and Measurement and Continuous Improvement assign FinOps decision rights and turn financial signals into improvement actions.
Anti-patterns to avoid
Section titled “Anti-patterns to avoid”- No Billing Account strategy: Spend is visible only at aggregate level without clear accountability.
- Inconsistent or missing labels: Usage cannot be attributed to products, teams, or environments.
- No data standardization: Cost views differ by team and cannot be compared reliably.
- FinOps only as reporting: No recurring optimization process and no ownership for improvement actions.