The monthly Azure cost review is happening in the wrong room. Finance can read the numbers. They cannot change what produced them. Every line on the Azure bill is the financial consequence of a decision someone made in a design meeting. The people who can fix the bill were not in the finance review.
The Bill Is a Design Document
Every cost line maps back to an architecture decision: a VM tier chosen, a service design pattern selected, a region picked, a deletion never scheduled.
Finance sees “App Service — £4,200.” An architect sees “synchronous integration layer sized for a peak that happens twice a year, running at full cost 24 hours a day.”
The numbers on the bill are correct. The problem is that nobody with the context to interpret them is in the room when they are reviewed. That is not a reporting failure. That is a governance failure — and it is producing real financial waste every month it goes unaddressed.
The Accountability Gap
In most organisations, the person who specced the VM and the person who receives the bill are different people, in different teams, with different incentives.
Architecture teams optimise for reliability and delivery speed. Cost is a downstream concern. Finance teams optimise for budget control. Architecture is upstream and invisible.
This is not a people problem. It is a structural problem. And it has a structural fix: cost must be a first-class concern at the design stage, not a reporting concern at the billing stage.
What Changes When Architecture Owns Cost
When architects are accountable for the cost consequences of their decisions, the decisions change. Not always dramatically — but consistently in the right direction.
Reservation coverage increases because the team that benefits from the saving is the same team that owns the commitment decision. Over-provisioning decreases because the architecture review now asks “what does this cost to run at this specification?” before it asks “does it meet the performance requirement?”
A quarterly architecture-cost review — not a finance review — with the engineers who made the decisions is worth more than any cloud cost management tool.
[DAN: Add a brief line about a specific situation where moving cost accountability to the architecture team changed the outcome — even an anecdote about a conversation that shifted the dynamic. This is the line decision-makers forward to their CTOs.]
The CFO should not own the Azure bill. The architects should. Not because finance is bad at their job, but because the bill is written in a language only architects can translate.
If your Azure spend is growing faster than your business is scaling, the problem is upstream of the bill. Get in touch to talk through where the architecture decisions are driving the cost.
