The pattern behind well-instrumented drift
The organization did the sensible things. Cost analysis is open to the teams. Budgets sit on the main subscriptions. Alerts fire. A monthly cost review shows the trend by subscription and by tag. And the Azure line keeps rising faster than anyone planned, with no single explanation.
This is not a tooling failure. Microsoft describes Cost Management as a suite of FinOps tools to “analyze, monitor, and optimize” Microsoft Cloud costs, and it does that well. The drift happens because visibility and accountability are different things, and the tool supplies only the first. A dashboard can show that a cost exists, where it sits and how fast it is growing. It cannot decide who is answerable for it, who may change it, or what the cost should be compared with. Those are management decisions. When nobody makes them, the tool reports the drift accurately every month.
Four reasons good dashboards still drift
1. The people who can see a cost often cannot change it.Microsoft’s scope documentation is explicit: the Cost Management Reader and Cost Management Contributor roles can view cost-saving recommendations, but acting on them, “such as resizing or shutting down resources”, requires access to the resources themselves. Billing-scope users “don’t have access to see or manage the actual resources in the Azure portal.” The finance analyst who spots the cost and the engineer who could remove it hold different permissions, sit in different reporting lines and often attend different meetings. Visibility lands with one group; the power to act sits with another.
2. A budget alerts an email address, not an accountable person.Microsoft says plainly that when a budget threshold is exceeded, “Resources aren’t affected, and your consumption isn’t stopped.” In the portal, a budget sends notifications to the email addresses configured on it. It can call an action group for automated responses, but only at subscription and resource group scope. A budget alert can go to a shared mailbox or a platform team that did not create the cost and cannot decide whether it is justified. The alert is delivered. Nothing happens.
3. Shared costs default to nobody.Platform services, shared networking, monitoring and security tooling are consumed by many teams and owned by none of them. Cost allocation rules can redistribute those costs, but Microsoft is careful about what they do: allocation “doesn’t affect your billing invoice,” and “all chargeback processes happen in your organization outside of Azure.” The rules also exclude purchases, including reservations and savings plans. The tool can display a split. Whether that split carries any consequence for the receiving team is an organizational choice.
4. Spend without a denominator cannot be judged.A cost that doubled may be waste, or it may be a product that is succeeding. Billing data alone cannot tell the difference. The denominator (transactions processed, customers served, orders fulfilled) lives in business systems, not in the bill. Cost Management supports exporting cost data so it can be integrated “into external systems or business processes”, but no one does that join unless an owner needs the answer.
Each of these gaps is closed by a decision, not a feature.
Run the free FinOps Signal.
The FinOps Signal is a short self-assessment of the practices that decide whether cloud spend is managed, placing each at a maturity stage.
Run the Free FinOps SignalWhat an executive should require
The executive sponsor’s job is not to configure Cost Management. It is to set requirements that make the configuration answer to accountability rather than to reporting. Four requirements do most of the work.
Every material scope has one named owner
Cost Management works within scopes: management groups, subscriptions and resource groups in the Azure resource hierarchy, and billing scopes such as EA departments and enrollment accounts or MCA billing profiles and invoice sections. Microsoft’s guidance describes using subscriptions for business units and environments, and resource groups for products.
Require a register that maps each material scope to one named person, not a team and not a distribution list. That person answers for the cost and holds, or can direct someone who holds, the resource access needed to change it. Where the person who can see the cost cannot act on it, the register should say who can.
Two structural facts matter here. First, under an Enterprise Agreement (Microsoft notes that management group scopes aren’t currently supported for Microsoft Customer Agreement accounts), management groups roll up usage-based charges only; Microsoft states they exclude purchases such as reservations and Marketplace offerings, so a management group total and the billing account total may differ. An owner of a management group should know which costs are not in their view. Second, when a subscription moves between management groups, Microsoft notes that “all historical cost moves” with it. Reorganizing the hierarchy rewrites the history each owner is judged against, so changes to it should be deliberate and recorded.
Every budget has a person behind it
A budget belongs to the owner of its scope, its amount is set by that owner, and its alerts reach that owner. Cost Management supports alerts on actual cost and on forecast cost; a forecast alert gives the owner time to act before the period closes, rather than an explanation afterwards. If a budget exists only because a central team created it, it is a reporting device, not a commitment.
Require one more thing: an expected response. A threshold crossing should produce a decision from the owner within a set time (accept the cost as justified, correct it, or escalate it), not just an email.
Shared costs follow an allocation policy someone owns
Cost allocation rules can move shared costs from source subscriptions, resource groups or tags to targets, split evenly, in proportion to total, compute, storage or network cost, or by custom percentages. Two details turn this into a governance question. The rules are created at billing account level, by an Enterprise Administrator under an Enterprise Agreement or a billing account owner under a Microsoft Customer Agreement. And once set, Microsoft says, the prefilled percentages “don’t change. All ongoing allocations use them,” until someone updates the rule manually.
So an allocation rule is a policy decision made by a small number of billing administrators, and it goes stale by default. Require that the basis for each split is agreed with the teams receiving the cost, that one person owns each rule, and that the rules are reviewed on a fixed cadence. Microsoft’s own guidance is to “revisit your allocation strategy yearly”; material shared costs may warrant more frequent review.
Tags carry ownership, enforced at creation
Microsoft calls resource tags “the only way to add your own business context to cost details.” They are also unforgiving. Tags are not applied to historical data. They must be applied directly to resources, some resource types do not include them in usage data, and tag inheritance applies subscription and resource group tags only within Cost Management, not on the resources themselves. A tagging policy introduced late cannot reconstruct who owned last quarter’s spend.
Require an owner tag and a cost-centre tag on resources at creation, enforced through policy, with untagged spend reported as its own line. Untagged spend is not a data-quality problem for the platform team. It is spend for which nobody has yet been held accountable.
Add the denominator
Ownership answers “who.” A unit measure answers “is this right.” For each material workload, the owner should name one business measure the cost is meant to scale with, and report cost per unit alongside total cost. Rising spend with a falling unit cost is a growth story. Rising spend with a rising unit cost is the conversation the sponsor needs to have.
This needs no new tooling. It needs exported cost data, a volume figure from the business system, and an owner who is asked for both every month.
Six questions for the monthly sponsor review
These questions are designed to be asked of owners, not of the FinOps team.
- Which material costs have no named owner this month? Include untagged spend and any shared cost not covered by an allocation rule.
- Which budget alerts fired, and what did each owner decide? An alert with no recorded decision is a gap in accountability, not in tooling.
- For each top workload, what was the unit cost, and which way did it move? If no one can answer, that workload has no denominator yet.
- Which shared-cost allocation rules changed, and do the receiving teams accept the basis? A split nobody accepts will not change behaviour.
- Which recommendations were viewed but not acted on, and who holds the resource access to act? This shows where seeing and acting have come apart.
- Did the management group (Enterprise Agreement) or subscription structure change? If it did, which owners’ historical figures moved with it?
A review built on these questions ends with names and decisions rather than observations.
Where this leaves the sponsor
Azure Cost Management gives an organization an accurate, timely view of its cloud spend, and the features exist to support accountability: scopes, budgets, allocation rules and tags. None of them assigns a cost to a person. That remains the sponsor’s decision, and it is the step that turns a reporting system into a management system.
Run the free FinOps Signal.
Ownership is only one of the things that decide whether cloud spend is managed or merely observed. The FinOps Signal is a short self-assessment of the practices that decide whether cloud spend is managed, placing each at a maturity stage.
Run the Free FinOps SignalPublished by the CIOQuest team. Explore the FinOps Maturity Diagnostic →