Budgets and alerts FAQs

Overview

This article answers the most common questions about budgets, anomaly detection, and alert delivery in Cost Analyzer — including threshold configuration, notification channels, escalation policies, and alert behavior.

Business value

Understanding how budgets and alerts work prevents missed overspend notifications, reduces alert fatigue, and ensures the right people are notified at the right time when cost thresholds are crossed.

How it works

Budgets in Cost Analyzer define a spend limit for a cost group over a billing period. Alerts fire when spend crosses configured threshold percentages. Anomaly detection monitors evaluate day-over-day and week-over-week spend patterns to surface unexpected changes. Both budget and anomaly alerts are delivered through notification channels — email or Microsoft Teams — and can be paired with escalation policies to route unacknowledged alerts to a secondary contact.

FAQs

1. Can I configure multiple threshold levels on a single budget?
   Yes. Cost Analyzer supports multiple threshold levels per budget — for example, 50%, 75%, 90%, and 100%. Each threshold can have its own recipient list and notification channel. This allows you to notify different people at different severity levels: an informational alert to the team lead at 75% and an escalation alert to the engineering manager at 100%.

2. Why did my budget alert not fire even though spend exceeded the threshold?
   Budget threshold evaluation runs on the import cycle. If the threshold was crossed between import cycles, the alert will fire on the next successful import. Also verify that the notification channel is correctly configured and that the recipient address or Teams webhook URL is valid. See Alert failures for a full diagnostic guide.

3. What is the difference between a budget alert and an anomaly detection alert?
   A budget alert fires when cumulative spend for the period crosses a percentage of the defined budget limit. It measures total spend against a fixed target. An anomaly detection alert fires when a statistically unusual change in daily or weekly spend is detected — regardless of whether the budget limit has been approached. Anomaly detection catches unexpected spikes earlier than budget thresholds because it reacts to rate of change, not total spend.

4. Can anomaly detection generate false positives for environments with naturally variable spend?
   Yes. Environments with high spend variability — such as development environments with frequent deployments or data pipeline workloads with irregular execution — may trigger anomaly alerts for normal operational patterns. Adjust the anomaly detection sensitivity threshold to reduce noise in high-variability environments. Review anomaly alert history monthly to calibrate the sensitivity setting. See Monitoring strategies for guidance.

5. How does an escalation policy work with a budget alert?
   An escalation policy defines a secondary notification that fires if the initial alert is not acknowledged within a configured time window. You link the escalation policy to a specific budget and threshold level. If the alert recipient does not acknowledge the alert within the escalation delay period, the policy sends a follow-up notification to the escalation contact. This ensures that critical alerts do not go unactioned if the primary recipient is unavailable.

6. Does Cost Analyzer support Teams notifications for budget alerts?
   Yes. Cost Analyzer supports Microsoft Teams as a notification channel using an incoming webhook URL. Configure the Teams channel with an incoming webhook connector, copy the webhook URL, and add it as a notification channel in Cost Analyzer. Budget alerts and anomaly detection alerts can both be routed to Teams channels. See Alert failures if Teams notifications are not delivering.

7. Can I set a budget at the resource group level rather than the subscription level?
   Yes. Cost Analyzer budgets are scoped to cost groups, and cost groups can be defined at the resource group level using the resource group dimension. Create a cost group scoped to the target resource group and attach the budget to that cost group. This allows budget tracking at a more granular level than the full subscription.

Related articles

• Cost monitors
• Automatic anomaly detection
• Escalation policies
• Alert failures
• Budget planning
• Cost analysis FAQs