Who owns the dashboard?

Most hyperscale cloud environments are well instrumented. The harder question is who owns what the dashboard is telling them.

Precision matters here, because the word accountability gets used loosely in the cloud cost conversation.

Receiving the bill is not accountability. Monitoring spend is not accountability. Tagging resources to indicate which business unit provisioned them is not an act of accountability. Accountability is a named individual or body with the authority to change the spending pattern, and the organisational expectation that they will act on it. That is a higher bar than most environments reviewed across Australia and APAC have cleared.

The most common pattern in financial services organisations, encountered repeatedly across the region, is a capable central cloud team sitting between a business that consumes and an executive layer that approves budgets but does not own outcomes. That team can see everything. They can report everything. What they cannot do is change anything without navigating a conversation that no one has formally chartered for them.

This is where change management becomes consequential and is almost always underinvested. The tools are available. The data is there. What is missing is a function dedicated to helping teams adapt: translating the numbers into new ways of working, building the internal consensus that makes cost accountability a shared norm rather than a contested imposition. Without that role, governance frameworks become shelf documents, and the data continues to report a problem nobody is formally positioned to solve.

Microsoft's Azure Cost Management documentation is thorough and technically excellent. It describes how to view costs, set budgets, configure alerts, and analyse trends. What it cannot do, because it is a product and not an organisation, is determine who should be held accountable when the trend is wrong.

The FinOps Foundation defines three operational phases: Inform, Optimise, and Operate. Most organisations encountered across APAC are operating somewhere in the Inform phase. The information exists. The operating model to act on it does not. That gap is not a tooling problem. It is a governance design problem.

The organisations that move past that gap share one thing in common. They build a coalition, not just a committee. Engineering, finance, risk, and the business units bearing the most consumption responsibility all have a seat at the table, a shared understanding of their accountability, and champions within each function who keep the direction aligned. The move toward cloud operations and AI operations is not a mandate that lands and takes hold. It is a team of people working together, with ownership assigned and the direction set, making it work in practice.

An environment with clear cost ownership, a structured review cadence, cross-functional champions, and executive sponsorship for cloud financial decisions does not need more dashboards. It needs fewer conversations about what the data means, because the accountability is already assigned.

The Azure FinOps and Cloud Governance Review is a fixed-scope engagement that surfaces the governance gaps, not just the spend patterns. If your organisation has visibility without accountability, April is a good time to address it. jradvisory.co.

How has your organisation approached the accountability question in cloud or AI operations?

Worth a share if someone on your team is navigating the same conversation.

Sources:

Microsoft. Azure Cost Management documentation. https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/overview-cost-management

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

FinOps Foundation. FinOps Framework phases. https://www.finops.org/framework/phases/