Two days on FinOps, because cloud cost is an engineering discipline wearing a finance costume. Today is visibility and allocation, who spends what and why; tomorrow is the levers that reduce it. The ordering is deliberate: optimization without allocation just makes an unexplained bill smaller.

Reading the Bill Correctly

Cost Management is the source of truth, and two distinctions prevent most misreadings. Actual cost shows charges as billed, including reservation purchases as lump spikes; amortized cost spreads those purchases across the resources that consume them, which is the view for allocation and unit economics, always. And cost versus usage: a resource can be free tier today and expensive at scale, so trend lines beat snapshots. Structure the scopes to match the org, management groups from the landing zone give you the rollups free, and use the built in views less than scheduled exports: daily amortized exports to a storage account, in the FOCUS format for tool portability, feeding whatever analytics stack September built, because serious cost analysis is a data problem and Cost Management’s UI is a viewer, not a warehouse.

The Tagging Contract

Allocation dies without metadata, and metadata dies without enforcement, so treat tags as a contract with three clauses. Clause one, the minimal schema: costcenter, owner, environment, application, nothing aspirational, four tags maintained beat fourteen abandoned. Clause two, enforcement by machinery from the policy post: deny resource groups missing costcenter, inherit tags from resource group to resources via modify policies so individual resources are correct by default, and let the IaC modules from this week set them so compliance is a side effect of deploying normally. Clause three, the escape valve: untagged spend is not ignored, it lands in a visible “unallocated” bucket on the leadership dashboard, and the platform team’s KPI is driving that bucket toward zero, because shame is a renewable resource. Shared costs, the hub firewall, the central Log Analytics workspace, ExpressRoute, need an explicit split rule (proportional to consumption where measurable, headcount or agreed percentages where not), written down once and argued about never.

Showback That Changes Behavior

The goal of visibility is a feedback loop, and the loop that works has three parts. Budgets with action groups on every subscription, thresholds at 80 and 100 percent of expected, wired to the owning team’s channel, not a finance mailbox, because the person who can turn the thing off must be the person who hears the alarm. Anomaly detection alerts enabled everywhere, they catch the accidentally provisioned GPU cluster and the runaway Log Analytics ingestion (the September cost lesson) within days instead of at month end. And a monthly rhythm: each team sees its amortized trend, its top five movers, and its unit metric, cost per transaction, per environment, per customer, whatever the business counts, because engineers optimize numbers they can move and unit costs are the number that survives growth. Nothing in today’s post reduced a single euro; it built the instrument panel. Tomorrow we fly the plane: reservations, savings plans, hybrid benefit, and the engineering optimizations that actually shrink the bill.

Cheers
Osama