FinOps Framework
One platform, every scope of spend.
The FinOps Foundation's Scopes describe where the practice now reaches — well beyond public cloud. CloudMonitor governs each scope your Azure estate touches: cloud, AI, SaaS, licensing, and the data center.
Where FinOps reaches
Five scopes, one cost platform.
Each scope below uses the FinOps Foundation's framing. Follow any one for how CloudMonitor governs it on Azure.
Cloud
Azure-native FinOps, purpose-built for the Microsoft cloud bill and modeled on the FOCUS schema.
AI
Tokens and GPUs — GitHub Copilot, OpenAI, Claude, Cursor, plus Azure OpenAI deployments and GPU SKUs.
SaaS
Govern the third-party SaaS your teams buy on credit cards — Datadog, Snowflake, Notion, Figma.
Licensing
Azure Hybrid Benefit, BYOL, M365, Power BI, and marketplace licenses reviewed every month.
Data Centers
Hybrid and on-prem footprint costed alongside cloud spend, in the same allocation model.
Where the field is
FinOps has outgrown cloud-only.
5
Scopes governed in one platform
90%
Of practitioners now manage SaaS — State of FinOps 2026
48%
Now manage data centers alongside cloud — State of FinOps 2026
Scopes in CloudMonitor
Every scope, one allocation model.
One model
Every scope rolls into one view.
Cloud, AI, SaaS, and licensing spend land in the same cost groups, so a team’s total cost is one number — not five tools to reconcile.
Licensing
On-prem licenses, costed with the cloud.
Azure Hybrid Benefit and BYOL opportunities surface across your VMs — the licensing scope, sitting right beside compute spend.
Source: this page interprets the FinOps Scopes published by the FinOps Foundation, licensed under CC BY 4.0. The wording, examples, and product mapping on this page are CloudMonitor’s own.
Govern every scope your Azure estate touches.
The beta spans cloud, AI token, and licensing cost across your own tenant.
