Group budget monitoring

Overview

Group budget monitoring sets a spending threshold for a cost management group in Cost Analyzer and alerts you when actual or amortized costs approach or exceed it. Configure the budget value, interval, and cost metric on the group, then layer on percentage thresholds or monthly risk prediction for earlier warnings.

Business value

Group budget catches cost overruns before the billing cycle closes, instead of after. Percentage thresholds and risk prediction surface overspend trends days or weeks ahead of the limit.

Prerequisites

An existing cost management group in Cost Analyzer is required. Group budget can be enabled either on an existing cost management group or while creating a new cost management group.

Required permissions

How it works

• A budget threshold is set at the cost group level. Alerts trigger when costs vary from it.
• The most recent values for the configured interval are compared against the budget and any percentage thresholds, with an alert on either breach.
• Tree view monitoring status reflects budget state: Red (100% threshold reached), Green (below budget and thresholds), Grey (monitoring disabled).
• Percentage thresholds notify you as spend approaches the limit, ahead of the default 100% alert.
• For monthly budgets, risk prediction calculates an average daily cost from the configured window of recent days, projects a 30-day total from that average, and fires an alert when the projected total exceeds the budget, reporting the estimated day the budget will be hit at the current spending rate. Risk prediction alerts fire only while the actual spend for the current month is still within the budget; once the budget is exceeded, risk prediction stops alerting for that month. Risk prediction runs independently of threshold and standard budget alerts.
• Alerts are recorded as incidents: open for 100%-threshold breaches (shown as an error state in the tree view), closed for other percentage breaches.

Steps

Use the following steps to configure a group budget, set percentage threshold alerts, manage alert configuration, enable or disable monitoring, and set up budget risk prediction. Navigate to the desired cost management group, open the Monitoring tab, and select the Group budget sub-tab to get started.

Configure a group budget

Setting up a group budget enables cost threshold monitoring on the group and activates the alerting pipeline for all subsequent threshold and risk prediction configurations.

1. On the Group budget sub-tab, click Configure if no budget has been set up yet, or Manage to update an existing configuration.
2. Enable the monitoring toggle, select the interval, choose the cost metric, and set the budget value.
3. Click Next, set the escalation policy and notification channels, then click Save.

Trends plot against the budget threshold, shown as a red dotted line. The most recent values for the configured interval are compared to the budget and percentage thresholds, with alerts on either breach.

Configure percentage threshold alerts

Percentage thresholds let you receive alerts before the full budget is reached, so you can act on overspend trends earlier in the billing cycle.

1. Set a budget value in the group budget configuration.
2. Open Alert Configuration.
3. Under Alert conditions, enter one or more percentage thresholds to alert at.
4. Click Apply.
5. Click Next > Save.

A default threshold of 100 applies if no percentage thresholds are set.

Enable or disable group budget monitoring

Use the Toggle on / Toggle off button in the group budget wizard.

Explain with AI

Explain with AI generates a Budget Insights report for the group, summarizing the current budget configuration, spend trend, threshold health, and improvement recommendations in a single view.

1. Navigate to the desired cost management group and open the Monitoring tab > Group budget sub-tab.
2. Click the (✦) Explain with AI icon in the Group budget header.

The Budget Insights report opens and includes:

• Configuration: a summary of the active monitoring settings: interval, cost metric, budget value, thresholds, escalation policy, and notification channels.
• How this budget works: a plain-language explanation of how the budget and thresholds interact for the current configuration.
• Spend trend and budget fit: a spend vs budget chart for the recent period, with the budget shown as a reference line.
• Threshold health: a visual indicator of how current spend sits relative to each configured threshold.
• Right-sizing your budget: recommendations to tighten or adjust the budget value based on recent spend patterns.
• Alert history: total, currently open, and resolved alerts for the last 30 days.
• Ways to improve: actionable suggestions such as adding a pre-breach threshold or aligning the budget more closely with current spend.

Budget risk prediction

• Budget risk prediction projects whether your current spending rate will exceed the monthly budget and estimates the day the budget will be hit.
• The prediction is calculated from the average daily cost over your configured window of recent days. If that average, when extended to 30 days, exceeds the budget, a risk alert fires. The alert includes the estimated day the budget will be hit at the current rate.
• Risk prediction alerts fire only while the actual spend for the current month is still within the budget. Once actual spend exceeds the budget, risk prediction stops alerting for that month; the standard budget alert takes over at that point.
• The window size controls the sensitivity of the prediction: a shorter window reacts quickly to recent cost spikes, while a longer window smooths out anomalies and reflects a more stable trend. Risk prediction operates independently and fires its own alert regardless of whether a threshold or standard budget alert has triggered.

Budget risk prediction is only available when the interval is set to Monthly. It does not apply to Daily or Last 7 days intervals.

1. Set the interval to Monthly and configure a budget value.
2. Open Alert Configuration under the group budget settings.
3. Set the number of days used to calculate the prediction from the current spending rate.
4. Click Apply.
5. Click Next > Save.

Configuration

Configuration tips

Two common configuration choices have an outsized effect on alert quality.

Use amortized cost for daily monitoring

When using a daily interval, prefer Amortized cost over Actual cost. Reservation purchases are charged on specific days of the month. With actual cost, this creates a visible cost spike on the purchase day that can trigger a false budget alert. Amortized cost spreads the reservation charge evenly across the reservation period, so no single-day spike appears.

If you use a monthly interval, either metric works effectively.

Configure sub-thresholds for monthly monitoring

When using a monthly interval, configure sub-thresholds under Alert conditions so you receive progressive warnings as spend accumulates, rather than a single alert only when the budget is fully exhausted.

Add multiple thresholds (for example, 50% and 80%) to receive an alert each time spend crosses a configured percentage of the budget.

Example scenario

A FinOps team sets a Monthly group budget of $10,000 on its "Production" cost group, using amortized cost to avoid reservation-purchase skew. Percentage thresholds at 50% and 80% give early warnings, and a 14-day risk prediction window flags any spend trend projected to exceed $10,000 before month-end.

Limitations

• Risk prediction alerts trigger only at a Monthly interval.
• Risk prediction alerts fire only while actual spend for the current month is within the budget. Once the budget is exceeded, risk prediction stops alerting for that month.
• Risk prediction has its own alert, separate from threshold and standard budget alerts; the two cannot be combined.
• Risk prediction does not run if there is no spending data within the configured window.

Troubleshooting

1. No alert is triggered even though spend has exceeded the budget value
   Cause: The monitoring toggle may be disabled, or cost data for the group has not yet refreshed for the current evaluation interval.
   Fix: Confirm the monitoring toggle is enabled in the group budget configuration. If data appears delayed, reset the cached data from the Essentials section and wait for the next evaluation cycle. Also verify the correct interval and cost metric are set. A Daily budget evaluates only the most recent day's spend.

2. Risk prediction is not firing despite spend trending above budget
   Cause: Risk prediction only operates when the interval is set to Monthly. It also requires spend data within the configured window. If the window is set to 3 days and no cost data exists for those days, no prediction is calculated.
   Fix: Confirm the interval is Monthly. Check the risk prediction window setting under Alert Configuration and ensure the selected cost group has cost data for the configured number of recent days.

3. Explain with AI icon is not visible on the Group budget sub-tab
   Cause: The AI Agents feature permission is not enabled on the signed-in user's role, or the Monitoring permission is below Read level.
   Fix: Ask an Account owner to enable the AI Agents permission under Specify feature permissions for the user's role, and confirm Monitoring is set to at least Read. Both conditions must be met for the icon to appear.

4. The tree view shows Red for a group but no notifications were received
   Cause: The escalation policy or notification channel may be misconfigured. For example, an invalid webhook URL, expired credentials, or an incorrect email recipient.
   Fix: Open the group budget configuration and review the escalation policy and notification channel settings. Correct any delivery issues in Managing notification channels and re-save the budget configuration.

5. Budget was updated but the chart still shows the old threshold line
   Cause: Cost Analyzer caches data and the chart may still be rendering based on the previous configuration until the cache resets.
   Fix: Click Reset cached data in the Essentials section or dashboard to force an immediate refresh.

FAQs

1. What is the difference between Group budget monitoring and Custom monitoring?
   Group budget monitoring tracks total spend for a cost management group against a single budget threshold, with optional percentage thresholds and monthly risk prediction. Custom monitoring applies rule-based criteria scoped to specific subscriptions, resource types, tags, or cost metrics, allowing more granular, targeted alerting within or across groups. Use Group budget for group-level spend accountability, and Custom monitoring when you need to track a specific segment of spend that a group-level budget would obscure.

2. When should I use the Daily interval instead of Monthly?
   Use Daily when you want to catch intraday cost spikes as they happen, rather than at the end of a billing cycle. For Daily monitoring, use Amortized cost. Actual cost records reservation purchases as a one-day spike, which causes false positives on a daily budget. Monthly is generally recommended for budget governance; Daily is better suited for anomaly-style alerting on specific cost groups.

3. Does risk prediction still fire if no percentage thresholds are configured?
   Yes. Risk prediction operates independently of threshold and standard budget alerts. It fires its own alert based on the projected 30-day spend regardless of whether percentage thresholds are set. The only requirements are that the interval is Monthly and spend data exists within the configured prediction window.

Related articles

• Automatic anomaly detection
• AI Agents in Cost Analyzer
• OpenAI setup in Turbo360