Every subscription, one normalized total
CostMon pulls daily cost from the Azure Cost Management Query API for each subscription you connect. Costs from many subscriptions roll up into one number.
Azure cost monitoring
CostMon connects to Azure Cost Management's Query API. It turns the cost of each subscription into one daily view. A jump in one service is visible within days, before the invoice.
Azure spend spreads across subscriptions. Cost Management shows one subscription at a time. Nobody sees the total until finance reconciles the invoice, weeks later. Reservations lapse without notice. Disks and public IPs from deleted VMs keep billing. A rise in cost has no early signal.
Cost anatomy
Alerts
CostMon's default rule watches every service on your account from the day you connect it. An alert always shows up in your CostMon feed. Add an email, Slack, or webhook channel to send it somewhere else too.
A VM scale set left scaled out after a load test, holding VM spend well above its baseline.
A monthly Azure budget alerts you when the month passes its cap. When a reservation lapses, usage returns to pay-as-you-go pricing and pushes the total up.
Sample alert, illustrative
Anomaly: azure / Virtual Machines spend spike azure / Virtual Machines was $260.00 on 2026-08-03 — 73% above its 14-day average of $150.00. Severity: warning Occurred on: 2026-08-03
To find what to cut, the recommendations list flags idle spend and commitment gaps to review.
Why CostMon
CostMon pulls daily cost from the Azure Cost Management Query API for each subscription you connect. Costs from many subscriptions roll up into one number.
Each cost row keeps its service name and region. A jump on one line, such as Virtual Machines, points you to where to look in the Azure portal.
Teams on Azure and AWS compare both clouds on one chart. A subscription that grows while its AWS twin stays flat stands out without a spreadsheet.
CostMon connects via an Azure AD app registration granted Cost Management Reader only. That role reads cost data. It has no rights to change a VM, a disk, or a resource group.
Getting started
Grant a service principal Cost Management Reader on the subscription. CostMon never requests write access to your resources.
CostMon calls the Query API on a schedule. Each result row becomes a CostMon cost entry with the fields every source shares.
Open a daily view of Azure spend by service and region. A scale set left scaled out after a load test lifts the Virtual Machines line, and a rule fires.
FAQ
Through an Azure AD app registration (service principal) granted Cost Management Reader on the subscription, read-only and scoped to billing data. CostMon never requests access to your VMs, storage, or resource configuration.
No. CostMon reads from the Cost Management Query API. Azure spend then appears on the same chart as AWS, GCP and the rest of your stack.
CostMon's background scheduler syncs Azure Cost Management data on a regular cadence, so the dashboard reflects a daily view rather than a monthly statement.
Yes. Every Azure row carries a service name and a region. To roll spend up by team, match an allocation rule on the Azure source, a service name or the connector.
A flat monthly rate per plan. It's never a cut of your Azure bill or the savings CostMon helps you find. Free includes 2 connectors; Professional and Enterprise include unlimited connectors.
Connectors
AWS, GCP, and Azure for cloud. Anthropic, OpenAI, Amazon Bedrock, Vertex AI / Gemini, and Helicone for AI and LLM spend. Snowflake and Databricks for the data cloud. Datadog, GitHub, and Vercel for the rest of the stack. Add CSV import for any tool without a native connector. That's 14 connectors, all normalized into the same unified view.
Connect a provider and CostMon builds a daily baseline for it. From there, a spike reaches your team as an alert.