Most Azure bills hide 25–35% waste in 6 line items. Here's the CSV audit, the columns that matter, and the 5 Azure-specific patterns we see on every audit.
Harinath Mekala
Founder, CARTIEAI
Azure bills are sneakier than AWS bills. Where AWS lists every line item, Azure rolls a lot of charges under "resource" entries that look benign until you sum them. The good news: 60 seconds of CSV work surfaces almost all of it.
In the Azure Portal:
AzureCosts-2026-01.csv💡 If you have multiple subscriptions, do this at the Billing Account scope. Service-by-service waste only shows up when you can see everything in one CSV.
| Column | What it tells you |
|---|---|
MeterCategory | The Azure service family (e.g. Virtual Machines) |
MeterSubCategory | The specific SKU (e.g. Dv4/Dsv4 Series) |
Quantity | How much you used |
Cost or PreTaxCost | What you paid |
ResourceLocation | Which region |
Sort descending by Cost. The top 25 rows are usually 80%+ of your bill.
MeterCategory = "Azure App Service". Sum Cost per resource. Most teams keep dev/staging plans on Premium tier for one feature they don't use. The fix is dropping back to Standard or Basic for non-prod — same web app keeps running, you cut the plan cost 40–70%.
MeterCategory = "Azure Cosmos DB". Look at MeterSubCategory rows containing Request Unit. Then check if your actual workload hits the provisioned RU/s — most teams over-provision by 3–10×. The fix is autoscale mode — same SLA, 30–60% cheaper.
MeterCategory = "Storage" AND MeterSubCategory contains "Premium SSD Managed Disks". Compare disk count vs VM count. Any disk that's not attached to a running VM is just sitting there racking up cost. Common after teams delete a VM without picking the "delete disk" checkbox.
MeterCategory = "SQL Database". Check the SKU — if you see Premium / Business Critical on databases that aren't production, you're paying enterprise pricing for a dev sandbox. Move dev to Standard or General Purpose. Median savings: $400–$1500/month per database.
MeterCategory = "Bandwidth". Inter-region traffic in Azure is $0.02/GB; egress to internet is $0.05–$0.087/GB. Most "Bandwidth" surprises come from a misconfigured Front Door or cross-region replication. Compare bandwidth cost to compute cost — if bandwidth > 8% of compute, you have an unintentional egress source.
If your Azure spend is above ~$5K/month and you don't have a Reserved Instance or Savings Plan, you're voluntarily paying 30–60% extra. Run Advisor → Reservations to see Azure's own recommendation. Most teams find $5–20K/month of immediate savings.
Pivot the CSV by:
MeterCategoryResourceLocationCost (sum)Any region you don't recognize? Old test deployment. Any service category that's >25% of your bill that you can't immediately explain? That's where the leak is.
CARTIE's free Azure bill audit ingests your CSV in seconds, ranks your top 5 cost leaks by $/month with the exact MeterCategory + SubCategory, and gives you the precise Azure CLI command to verify each. No credentials, no retention, no signup.
If you'd rather we plug into Azure and send pull requests for every leak we find, that's CARTIE for Azure.
Related: The Hidden 32% Cloud Waste No FinOps Tool Is Showing You.
Azure spend is exploding — second only to AWS in customer audits we run. This guide is the 12-pattern playbook for cutting Azure bills, with concrete portal pat…
THE FINOPS BRIEF
Built for finance & engineering teams who are tired of paying for cloud they don't use. No fluff. Just what works.
Unsubscribe anytime. We never sell your data.
ABOUT THE AUTHOR
Founder, CARTIEAI · Building in public
I'm building CARTIEAI to fix the cloud-cost problem I saw drain millions at companies I worked for — where engineering and finance kept talking past each other. If you liked this post, here's where I share unfiltered notes on building this in public: