Share via

Is it possible to configure the sensitivity of Azure Cost Anomaly notifications?

FedericoZarelli-6386 60 Reputation points
2026-03-08T11:16:20.9066667+00:00

Azure provides an excellent feature of notifying users when a temporary anomaly took place in the cost. I would like however to have a more sensitive alert - is it possible to configure this?

Azure Cost Management
Azure Cost Management

A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-08T11:16:32.52+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Azure Cost Management’s built‑in cost anomaly alerts do not expose a user-configurable “sensitivity” setting in the portal or documented APIs. The anomaly detection behavior is managed by the service.

    What can be configured:

    • Anomaly alerts can be created and managed (who gets notified, scope, etc.) from Cost Management → Cost alerts → + Add → Alert type = Anomaly.
    • Alerts can also be created via the Scheduled Actions API for more advanced scenarios (for example, using a service principal), but the documentation only covers configuring the alert rule and viewId, not tuning sensitivity.

    To get “more sensitive” behavior today, the supported options are:

    1. Use budget alerts with tighter thresholds (for example, 90%, 95%, 100% of a smaller budget) to catch increases earlier.
    2. Combine budget/forecast alerts and anomaly alerts as part of spending guardrails so that budget alerts handle fine‑grained thresholds while anomaly alerts catch unexpected patterns.

    There is no documented way to adjust the underlying anomaly detection sensitivity (for example, to make it trigger on smaller deviations) in Azure Cost Management.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.