FinOps Framework
Six core personas, one source of truth.
The FinOps Foundation defines six core personas — the roles that run the practice day to day. CloudMonitor gives each one the Azure cost view they actually open, from the engineer's recommendation to the CFO's one-page summary.
Who runs FinOps
Six roles. One set of numbers.
Each persona below uses the FinOps Foundation's name. The surface CloudMonitor gives them is ours.
FinOps Practitioner
The coordinator who owns the practice. The admin app is their control plane — cost groups, virtual tags, budgets, and policies in one place, with an audit trail behind every change.
Engineering
The team that turns recommendations into action. Rightsizing, idle, and commitment recommendations land scoped to the resources engineers own — read-only, so they decide what to action.
Finance
Owns budgets, forecasts, and the close. Azure cost maps to existing cost centers and budget structures, with journal-ready chargeback exports — no spreadsheet reconciliation.
Product
Connects spend to features and outcomes. Unit-economics views put cost per customer, per environment, or per release next to the bill — the denominator product actually cares about.
Procurement
Owns vendor contracts and commitment purchases. Reservation and Savings Plan analysis, ACR draw-down, and renewal tracking make the next commitment a modeled decision, not a guess.
Leadership
The C-suite sponsor. A one-page executive summary frames Azure spend against budget, trend, and business value — the view that earns FinOps a standing slot in the leadership review.
Where the field is
The personas, in this year's data.
6/6
Core personas mapped to a CloudMonitor surface
78%
Of practices now report into the CTO/CIO org — State of FinOps 2026
8–10
Practitioners run FinOps at $100M+ cloud spend — State of FinOps 2026
Personas in CloudMonitor
The view each role opens.
Leadership
The CFO’s one-page view.
The executive summary frames spend against budget, trend, and value — the surface leadership reviews without needing a practitioner to translate it.
Finance
Cost mapped to budget owners.
Finance sees Azure spend rolled into the same cost-center and chargeback structures they already run — ready to export, not re-key.
Practitioner
The practice, run from one console.
The practitioner drives cost groups, tags, budgets, and policy from the admin app — the control plane the other five personas consume.
Source: this page interprets the FinOps Personas published by the FinOps Foundation, licensed under CC BY 4.0. The wording, examples, and product mapping on this page are CloudMonitor’s own.
See the view each persona opens.
The beta runs the practitioner, finance, engineering, and leadership surfaces on your own Azure tenant.
