Domain 2 · Quantify Business Value
A budget per team, not per subscription.
Budgeting in the Foundation framework means setting and tracking spend across the organisation — not a single Azure subscription cap. CloudMonitor budgets bind to cost groups, fire on a five-step ladder, and carry underspend forward so finance and engineering plan against the same number.
The problem
One subscription budget for a four-product business.
A single subscription budget.
The Azure-native cost budget sits at the subscription, but the org spends by product. The two never reconcile.
Only 80% and 100% alerts.
By the time the 80% alert fires, the team has four working days to course-correct a quarter. That isn't an early warning, it's an obituary.
No carryforward.
Teams that underspend in Q1 race to use it in Q4. The budget incentivises waste at the boundary.
How CloudMonitor answers
Budgets that map to your business.
Per-cost-group budgets.
Set a budget against any node of the allocation tree — product, BU, segment. The same tree that runs invoices and anomalies.
Five-step thresholds.
50, 70, 85, 95, 100 — each routable to a different audience. Engineering hears about it at 70, finance at 85, the executive sponsor at 95.
Carryforward rules.
Define what happens to underspend at period close — carry, return, redistribute. Stops the December scramble that breaks every annual plan.
Alert routing.
Teams channel, mailbox, ITSM ticket, webhook — every threshold can take a different path. The right person hears the right step.
Outcomes
Budgets that hold the line.
5
Threshold steps, each routable
Tree
Bind to any cost-group node
Carry
Underspend rules, not Q4 scramble
See per-cost-group budgets with a five-step alert ladder.
The demo tenant ships with three budgets in flight and a routing trail to inspect.