Alerts, digests, webhooks, and budget tracking
What CostRadar notifications and budget tracking are intended to do, with careful boundaries around enforcement and timing.
CostRadar can help your team notice cost changes, but notifications are informational. They depend on Azure billing data availability and CostRadar's scheduled checks.
Anomaly alerts
When enabled for your plan and configured channels, CostRadar can send anomaly notifications after a scheduled detection run finds a new billing anomaly. Alert timing is not real time because Azure billing data is not real time.
Use Settings → Alerts → Anomaly alert emails to enable or disable anomaly email, then save. The saved recipient under Emails is preferred for anomaly notifications as well as weekly digests, even when the weekly digest is disabled. Without that recipient, anomaly email falls back to the billing, contact, or account address. Slack and Teams are optional additional destinations, not a requirement for email.
Alerts may include the affected service, severity, estimated impact, and a CR-XXXX reference you can open in the dashboard.
Webhooks and team channels
Growth and Business plans include webhook-based alert delivery for supported team channels. These integrations send CostRadar notifications to a channel you configure. They do not give CostRadar control over your Azure resources or chat workspace.
For step-by-step setup, see Microsoft Teams webhook notifications or Slack webhook notifications.
If a webhook stops working, check whether the receiving channel still accepts incoming webhook requests and whether the URL was rotated or removed.
Weekly digests
Weekly digest emails summarize recent spend, open anomalies, and notable services when the feature is enabled for the account. Growth/Business weekly digests run on Mondays at 08:00 UTC. The weekly digest switch does not control anomaly emails. Digests are meant for review, not financial close.
Budget tracking
CostRadar budget tracking lets you set monthly targets at the account or subscription level. Budget tracking is informational only. CostRadar cannot enforce budgets, stop Azure spend, disable resources, or guarantee that a notification arrives before a budget is crossed.
Budget values drive dashboard forecast warnings. For outbound subscription-budget notifications, configure a subscription forecast rule on the Alert Rules page. Entering a budget alone does not configure an outbound notification rule.
For hard controls, configure Azure-native budgets, cost alerts, policy, and operational approval workflows.
Settings and invitation feedback
If settings cannot be loaded, editing is blocked until a successful reload rather than showing assumed defaults. After an interrupted save, reload to confirm the stored values before retrying.
Team Access returns a shareable invitation link even when its email cannot be confirmed. Provider acceptance is not proof of inbox delivery. If the UI reports that the email was not confirmed, copy and share the generated link manually instead of repeatedly generating invitations.
When to contact support
Escalate if alerts are configured but not arriving, a digest goes to the wrong recipient, a webhook test fails repeatedly, or budget status appears inconsistent with the dashboard.