FinOps Framework
Six FinOps principles, mapped to a CloudMonitor surface.
The FinOps Foundation defines six principles every practice runs on. CloudMonitor turns each one into something you can open and use on an Azure tenant — not a poster on the wall.
The framework's foundation
Six principles. One operating model.
Each principle below uses the FinOps Foundation's wording. The explanation of how it shows up in CloudMonitor is ours.
Teams need to collaborate
Finance, engineering, and leadership read the same numbers. Shared cost groups, a Microsoft Teams bot that routes each anomaly to the team that owns it, and reports tuned per audience mean no one argues about whose figure is right.
Business value drives technology decisions
Spend sits next to the outcome it buys. Unit-economics views put cost per customer, per environment, or per release beside the Azure bill, so scaling a workload up or down is a value call backed by data — not a hunch.
Everyone takes ownership for their technology usage
Every resource rolls up to a named cost group with an accountable owner. Engineers see their own spend inside the Fabric app they already open each week, not a separate console they never sign in to.
FinOps data should be accessible, timely, and accurate
Azure billing lands daily in FOCUS format, is validated on every refresh, and reaches the Fabric app within hours. Cost anomalies surface the day they happen — not buried in a reconciliation three weeks after the invoice.
FinOps should be enabled centrally
One central place defines tags, budgets, policies, and cost groups; every team consumes that standard instead of rebuilding it. The admin app is the control plane, and the reports are how the standard reaches the rest of the org.
Take advantage of the variable cost model of the cloud
Rightsizing, idle-resource detection, and commitment analysis run continuously and surface as recommendations — baseline workloads sit on reservations while everything else stays elastic. CloudMonitor is read-only, so your engineers keep the keys and decide what to action.
Where the field is
The principles, in this year's data.
60%
Run a centralized FinOps enablement model — State of FinOps 2026
78%
Of FinOps teams report into the CTO/CIO org — State of FinOps 2026
6/6
Principles mapped to a CloudMonitor surface
The principles in CloudMonitor
What the principles look like on screen.
Business value
Spend, mapped to the business.
The FinOps overview frames Azure cost against effective spend, total savings, and the cost groups driving it — so leadership reviews value, not just a number that went up.
Ownership
Every cost group has an owner.
Smart Tags allocate spend into cost groups by rule, each with an accountable owner. Distributed ownership replaces a central team policing everyone else’s bill.
Accessible and timely
Alerts where teams already work.
Anomalies post to Microsoft Teams the day they happen, routed to the owning team — accessible, timely data in the place collaboration already lives.
Source: this page interprets the FinOps Principles published by the FinOps Foundation, licensed under CC BY 4.0. The wording, examples, and product mapping on this page are CloudMonitor’s own.
Run all six principles on your own Azure tenant.
The beta brings each one to life — shared cost groups, FOCUS data, anomaly routing, and read-only recommendations — on your own Azure data.
