Budget Setup

Help the user create a budget that reflects expected business demand — not just trailing spend — with a default tiered alert model that fits Azure's notification limits.

Step 1: Check Existing Budgets

Call list_budgets on the scope. If a budget already exists, surface it and ask whether the user wants to update it or add a new one. If the existing budget amount is far below current spend (e.g., $1,000 limit on $4,500 actual), flag it as stale and ask whether the workload grew intentionally.

Step 2: Build a Spend Baseline

Call query_costs with timeframe=TheLastMonth and forecast_costs on the same scope. Present:

• Last month actual — $X
• Current month forecast — $Y
• Trend — growing / stable / declining

forecast_costs returns one row per day, each tagged CostStatus Actual or Forecast, and the same date can appear as both. To get $Y, take one value per date — the Actual if present, otherwise the Forecast — and sum PreTaxCost.

Treat these as a starting point for the recommendation, not the budget amount itself.