Getting charged thousands again for log analytics. I specifically set the budget limit to $200 and it still went over $5000

Question

Here is the tracking ID for my previous case: TrackingID#

Answer 1

Hi Ryan Thomas,

To get refund I would suggest you raise Billing Support ticket for further assistance.

Please follow below steps:

Azure Billing support request link: create a support request.

1.From the resource menu, in the Help section, select Support + Troubleshooting. In the Support + Troubleshooting pane on the right, type "Billing" in the search box, select Billing, and then click Next.

2.Select the subscription and click Next. You will be presented with some suggestions to resolve your issue. If none of these apply, please follow the steps below.

3.Scroll down and you will find an option to Contact Support. From there, select Create a support request.

4.Enter the problem description (Issue type - Billing, Subscription, Summary - Billing, Problem type - Assistance with Bill, Problem subtype - Help with a billing discrepancy)

5.If the solutions appear again, click on 'Return to support request'. Click Next, and you will then be able to create the billing support ticket.

Kindly let us know if the above suggested solution helps or you need further assistance on this issue.

Thanks,

Suchitra.

Answer 2

Is there any way I can get a refund for this? The log analytics workspace wasn’t being used for anything and i shouldn’t be charged this much when the container app wasn’t even using it

Answer 3

Hi Ryan Thomas,

Thanks for reaching out to Microsoft Q&A.

Here's what’s happening and how to move forward.

1. Budgets vs. actual usage
   • Azure Budgets only send alerts when you hit thresholds; they don’t block or stop usage.
   • The only way to automatically stop resource consumption is via a spending limit, and that only applies to Free Trial or certain offers. Pay-As-You-Go subscriptions don’t enforce a hard stop once a budget fires.
2. Drill into Cost Analysis
   • Go to Cost Management + Billing → Cost analysis
   • Filter by Service name = Log Analytics and group by Resource or Resource group to see exactly which workspace (or diagnostic setting) drove the $5 k.
   • In your screenshot, you ingested ~2.17 M GB at $2.30/GB, which is why the bill ballooned.
3. Common root causes
   • High-volume diagnostic settings: for example, sending Container Apps or App Service metrics/logs at “AllLogs” or high retention
   • Enabling platform logs (activity logs, resource logs) with default retention can backfill large volumes
   Check Diagnostic Settings on each resource (e.g. Container Apps, App Service, Event Hubs) and: • Disable any unwanted streams • Lower retention • Route only essential metrics