9.2 Cost visibility, tagging and budgets
You can say which team, product or feature caused any line on the bill.
Before:01. Cloud Foundations
A bill you cannot attribute is a bill you cannot manage, and this topic builds attribution: a tagging standard enforced from day one, cost allocation to teams and features, budgets, and anomaly alerts that reach a human in time to matter. It sits between pricing and optimisation because visibility is the prerequisite of both. The scenario it rehearses is the bill that grew by a third — with tags, that is a query; without them, it is an archaeology project conducted during an argument.
Work through these
A tagging standard, enforced from day one
Labels applied consistently from the beginning are what make a bill answerable by team or product later. Adding them retroactively across a running estate is painful enough that most people never finish.
Cost allocation, showback and chargeback
Showing teams what they spend, or actually charging it to them, changes behaviour differently, and both need the labelling above to work at all. Choosing which one fits your organisation is a real decision.
Budgets and anomaly alerts that reach a human
A budget that emails an unread address is not a control. This item is about alerts that reach someone who can act and that fire on an unusual change rather than only a total.
Reading a bill that has grown by a third
When a bill jumps, the skill is finding the cause rather than staring at the total. Working through a real increase methodically is what this item asks for.
Sign in to keep your progress.
Free resources
We haven't checked most of these for screen reader use yet.
Links last checked 29 Aug 2026.
Stuck here?
Ask a mentor. A real person answers, and they can see exactly which topic you're on. Usually within a couple of working days.
Checking your session…
Topics shown in module order.