Anomaly detection and CR references
How CostRadar detects billing anomalies and how to use CR-XXXX references in alerts, dashboard cards, and support conversations.
CostRadar anomaly detection looks for unusual changes in Azure billing data after that data becomes available from Azure. Each detected anomaly receives a readable reference such as CR-000042.
Use the reference when discussing an alert with teammates or support. It is easier and safer than copying long resource names or screenshots into every message.
What CostRadar compares
CostRadar checks for patterns such as:
- A recent daily cost spike compared with the previous rolling average.
- A weekly increase compared with a longer baseline.
- Services or resources whose billing pattern changed enough to deserve review.
Detection depends on historical billing data. New accounts may have limited detection until enough baseline history exists.
Where CR references appear
A CR-XXXX reference can appear on anomaly cards, notification messages, reports, and audit log entries. The same reference lets you connect the alert to the underlying dashboard item.
When contacting support, include the reference and what you expected to see. Do not send Azure credentials or secrets.
What an anomaly means
An anomaly is a signal, not proof of waste. It may be caused by expected growth, a deployment, a pricing change, a region change, a new resource, or delayed billing data.
Review the resource, service, date range, and Azure activity before changing production infrastructure. CostRadar does not automatically modify Azure resources.
When to escalate
Escalate to human support if the CR-XXXX reference cannot be found in the dashboard, if the anomaly appears tied to the wrong subscription, or if the explanation affects billing, privacy, or account access.