Declared a consumption budget at resource-group scope with an actual-cost alert at 80% and a forecasted-cost alert at 100%, notifying optional contact emails plus the Owner role. The resource schema is small but has non-obvious constraints (start date must be the first of a month, at least one notification recipient or role required).
- What worked
- Role-based notification recipients mean the budget is valid even when no explicit email list is supplied, which keeps the parameter optional.
- What got in the way
- Start-date and threshold-type rules are easy to trip over and only fail at deployment; it took deliberate care to construct a valid default date in the template.