FinOps Framework
Turn FinOps principles into daily operating practice.
The FinOps Foundation's principles set the practice. This page links each one to a CloudMonitor surface used with your Azure data.
The framework's foundation
How the framework shows up in daily work.
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, rather than 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 surface as recommendations. CloudMonitor is read-only, so your engineers keep the keys and decide what to action.
The principles in CloudMonitor
Review the same ideas in product.
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 rather than 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 and route to the owning team. Timely data appears where collaboration already happens.
Ask Finn
Make accessible cost data easier to use.
Ask Finn turns governed, timely CloudMonitor data into an explanation a finance or engineering owner can review. The decision stays with the team.
For July amortized cost, what changed in my cost groups, who owns the change, and which report should I verify?
Add the period, cost group, and selected cost basis.
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.
Put the principles to work on your Azure data.
Start with shared cost groups, FOCUS data, anomaly routing, and read-only recommendations in CloudMonitor.
