Skip to main content
Azure - FinOps Platform

FinOps Maturity Self-Check

FinOps Capability Assessment (preview)

A deeper self-check against the FinOps Framework's full 22 Capabilities, not just its 4 Domains. Ratings here are saved separately from the Domain-level ratings on the Domain Overview tab.Step 3 of 5
Why this matters

This is still a preview: all 4 Domains now have real Capability-level questions, but there's no Capability-level action plan yet, and this wizard's ratings don't (yet) reconcile with the Domain-level assessment — a later update will connect the two.

Choosing how and where a system is built in Azure (which service tier, which region, which compute option) with cost as a real factor in that decision, not an afterthought.

Why it matters: It's far cheaper to design a cost-efficient system up front than to re-architect an expensive one later — most of a workload's lifetime cost is locked in at the design stage.

Paying a lower price for the same Azure resources through Reservations, Savings Plans, or other commitment-based discounts.

Why it matters: Azure's on-demand price is rarely the best available price for steady, predictable workloads — committing ahead of time can cut real, ongoing cost with no change to what you're actually running.

Making sure your Azure resources are the right size, actually running when needed, and not sitting idle or over-provisioned.

Why it matters: An oversized VM or a forgotten disk that nobody's using still costs money every day — this is usually the fastest, most direct way to cut waste without changing what your systems do.

Understanding the environmental impact (carbon emissions) of your Azure usage alongside its cost.

Why it matters: The same changes that cut cost — running only what you need, right-sizing, retiring idle resources — usually cut carbon impact too, and more customers/regulators are starting to ask about it.

Managing software licenses and SaaS subscriptions (not just raw Azure compute/storage) so you're not over-paying for unused seats or under-licensed for what you actually run.

Why it matters: Licensing and SaaS costs are often longer-term commitments than cloud compute — a bad licensing decision is much harder and slower to undo than resizing a VM.