What CostRadar is and what it can do
A plain-language overview of CostRadar's Azure cost monitoring, where it helps, and where it intentionally does not act for you.
CostRadar helps small and medium-sized teams understand Azure spending before it becomes a month-end surprise. It connects to Azure with read-only access, checks cost data on a schedule, and turns billing patterns into dashboard views, anomaly cards, reports, and optional notifications.
CostRadar is built for teams that need clearer day-to-day cost visibility without giving a third party the ability to change cloud infrastructure.
What CostRadar can do
- Show Azure cost trends as billing data becomes available from Azure.
- Detect unusual spending patterns from billing history, including daily spikes and weekly baseline changes.
- Display anomaly references such as
CR-000042so an alert, dashboard card, and audit log entry can be discussed consistently. - Surface Microsoft Azure Advisor cost recommendations with attribution.
- Produce reports and exports that help teams review services, resources, resource groups, and monthly trends.
- Track informational budgets and notify your team when costs appear to be moving above expected levels.
- Support owner and viewer roles so finance, operations, and engineering stakeholders can inspect the same account.
What CostRadar cannot do
CostRadar is not a real-time enforcement system. It cannot stop virtual machines, delete resources, throttle usage, apply Azure Policy, or prevent spend from occurring. For hard enforcement, use Azure-native controls such as Azure Budgets, Azure Cost Alerts, Azure Policy, and resource governance workflows.
CostRadar also does not guarantee savings. Recommendations, forecasts, anomaly signals, and stale-resource insights should be treated as decision support. Your team remains responsible for validating any change before acting in Azure.
How to read CostRadar data
Current-month costs are estimates because Azure continues to process and refine billing data throughout the month. Recent usage can arrive late, especially for pay-as-you-go subscriptions. Prior completed months are more stable.
When a number seems surprising, check the data freshness timestamp, the connected subscription, and whether the relevant Azure meter has finished posting recent usage.
When to contact support
Contact support when CostRadar shows no data after a successful connection, when a plan or billing issue needs account-specific review, when a CR-XXXX anomaly does not match the dashboard, or when you need help deciding whether a behavior is expected.