Controlling Databricks Costs on Azure, Part 4: Budget Control & Spend Blocking
· 6 min read
This is the final part of the series. Part 1 compared the alternatives and explained our combined approach. Part 2 built the cost dashboard, and Part 3 added proactive SQL alerts. One piece is still missing: enforcement. Dashboards show and alerts warn. Neither of them stops anything. That is the job of Budget Control.
In this post, you'll learn:
- What Budget Control (Public Preview) can and cannot do today
- How we set up budgets per user and user group, and how we derived role-based limits
- How spend blocking works (currently Genie only) and how our override process looks
- How we manage the ClickOps setup as documented technical debt until Terraform support catches up