Clear answers for Azure cost monitoring in CostRadar
Read client-facing guidance on connecting Azure, interpreting cost data, managing plans, and knowing when to contact human support.
Account deletion, data retention, and privacy boundaries
What customers should know about deleting a CostRadar account, retained records, and data access boundaries.
Alerts, digests, webhooks, and budget tracking
What CostRadar notifications and budget tracking are intended to do, with careful boundaries around enforcement and timing.
Anomaly detection and CR references
How CostRadar detects billing anomalies and how to use CR-XXXX references in alerts, dashboard cards, and support conversations.
Connecting Azure with read-only access
How CostRadar connects to Azure using a service principal, subscription Reader, and Storage Blob Data Reader for storage exports.
Why Azure cost data can be delayed
How Azure billing data timing affects CostRadar charts, current-month estimates, and anomaly detection.
Billing, cancellation, downgrade, and refund help
Support-level guidance for CostRadar billing questions, cancellations, downgrades, and refund review.
Plans, trial, annual billing, and limits
Current support-level guidance for CostRadar plans, trial access, annual billing, and subscription or viewer limits.
Reports, exports, Advisor recommendations, and cost allocation
How CostRadar reports, exports, Azure Advisor recommendations, and allocation views should be used.
Team roles, viewer access, and the audit log
How account owners and viewers work in CostRadar, and what the audit log records.
Troubleshooting Azure connection and no-data issues
Common fixes for Azure connection errors, cost pull failures, no data, access denied, and expired client secrets.
Using Azure Cost Management Storage Export with CostRadar
How to configure Azure Cost Management exports to a storage account and connect those exported files in CostRadar.
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.
When to escalate to human support
Situations where the support bot should hand off to a person for account, billing, privacy, or ambiguous product issues.