What the dashboard cannot tell you

A FinOps dashboard tells you what you are spending. It does not tell you what to do about it.

Walk into almost any Azure environment in financial services, insurance, or the broader commercial sector across APAC and you will find the same thing. Cost Management reports. Advisor recommendations. Budget alerts at the subscription level. Tagging policies, at least in the documentation.

Visibility is there. What is almost never there is accountability.

And most teams know it. The harder conversation is not whether the gap exists. It is agreeing on whose problem it actually is. Finance thinks it belongs to IT. IT thinks the business units need to own their consumption. The business units think cloud is an infrastructure cost. That conversation loops without resolution, and in the meantime, the spend continues.

Visibility is where the work begins. Knowing what you are spending, and even understanding why, is a meaningful first step. It is not the same as having an organisation where someone owns the outcome.

The FinOps Foundation defines FinOps as a cultural practice, not a tooling exercise. Their 2024 State of FinOps Report identified organisational alignment as the most consistent barrier to FinOps maturity, specifically the difficulty of getting engineering, finance, and business units to share accountability for cloud spend. The full report is at data.finops.org, and this finding has been consistent across multiple survey cycles.

The pattern is familiar to anyone who has worked inside these environments. A capable central cloud team sitting between a business that consumes and an executive layer that approves budgets. The team can see everything. They can report everything. What they cannot do, without an accountability structure they were never given, is change anything.

The dashboard shows the gap. It cannot close it.

Closing it requires three things that tooling cannot provide. A clear cost ownership model that names the individual or team responsible for each area of spend. A decision structure for contested spend, so that when the numbers do not match the budget, there is a process for resolving it rather than a meeting that ends without a decision. And executive sponsorship that treats cloud cost as a business outcome, with the same rigour applied to any other investment the organisation is accountable for.

None of those three things can be handed to an organisation from the outside. They require internal conversations that are sometimes uncomfortable, between teams that do not always agree, led by leaders who are willing to own an outcome rather than observe one. That willingness is the prerequisite. An advisory can help structure the conversation, surface what the data is actually telling you, and give your leadership team the language to act. But the organisation has to want to have the conversation first.

When those three things are in place, the dashboards become genuinely useful. The data has somewhere to go. Without them, the numbers are read and noted, and the next month looks the same as the last.

If this is a pattern your team is sitting inside right now, share it or leave a comment. The accountability gap in cloud governance is more common than most teams admit publicly, and hearing what others are navigating is usually more useful than any benchmark report.

JR Advisory is opening late April bookings for scoping calls. The Azure FinOps and Cloud Governance Review is a fixed-scope engagement that helps leadership teams surface the governance gaps behind the spend patterns and structure the internal conversations that close them. The work starts inside your organisation. The conversation starts at jradvisory.co.

Citation: FinOps Foundation, State of FinOps 2024 — https://data.finops.org