DFdom@fradley
← ~/writing
$ cat cloud-cost-as-a-design-decision.md

Make your Azure bill predictable: cost as a design decision

Most shocking Azure bills have the same cause: nobody treated spend as a design decision. Teams created plenty of oversized resources, and nothing stopped them.

Someone sized for peak load "to be safe". Environments were stamped out at one size whether they needed it or not. A proof of concept quietly became production and kept its generous footprint. Each of those is a governance gap, not a pricing problem.

Cutting costs after the bill lands is slow and the money is already spent. It costs less to build the controls into the platform from the start. These three cover most of it:

Control What it does for you Where to read more
Budget alerts An alert at 80% of budget gives you a warning while there is still time to act Never get surprised by the Azure bill
Policy limits on what gets created Stops an oversized VM being built for a small job; anyone who needs the expensive size has to ask for it A VM size restriction in Azure Policy is the usual first one
Tags for owner and cost centre "What did we spend on this product, and who owns it?" can be answered with a query Untagged Azure resources

The test

Ask your team what you spent on a given product last month, and who owns that number. If they can answer in minutes, cost governance is probably working. If they can't, expect the next bill to be a surprise.

This is the Well-Architected cost pillar in practice: spend on purpose, and be able to account for every pound. Put the cost guardrails in the same policy layer as your security ones.

Next: the five questions a non-technical leader can ask to tell whether their cloud estate is under control.

discuss on linkedin → more writing