Azure Monitor pricing

Commitment Tiers allow you to reserve a fixed amount of daily data ingestion capacity for Azure Monitor and Azure Sentinel for a fixed, predictable daily fee. You can upgrade your requested tier level at any time. However, the minimum commitment period before you can opt out or reduce your capacity reservation is 31 days.

• Moving to a larger tier level: you can upgrade your level at any time. Your new tier will be effective at 12:01 AM UST on the following day.
• Reducing your selected capacity reservation: you can reduce your tier level or opt out entirely from the Commitment Tier pricing after the first 31 days. This 31-day clock resets every time you make any change (increase or decrease) to your selected tier level. Your new pricing tier choice will be effective at 12:01 AM UST on the following day.

Learn more about Log Analytics pricing models and Commitment Tiers.

Yes. Using Log Analytics Dedicated Clusters, you can move multiple workspaces into a cluster, and thus potentially take advantage of a larger Commitment Tier and it’s lower cost per GB. Learn more about billing options and requirements for Log Analytics Dedicated Clusters.

You can select a retention period up to 730 days. The retention cost is calculated on a daily granularity based on the monthly price per GB stored beyond the free days of retention (31 days) except for Application Insights data, and workspaces that have Azure Sentinel enabled. Learn about options for managing data retention.

Subscriptions that contained a Log Analytics workspace or Application Insights resource on April 2, 2018, or are linked to an Enterprise Agreement that started before February 1, 2019 and is still active, will continue to have access to use the legacy pricing tiers: Free Trial, Standalone (Per GB), and Per Node (OMS). Workspaces in the Free Trial pricing tier will have daily data ingestion limited to 500 MB (except for security data types collected by Azure Defender (Security Center)) and the data retention is limited to seven days. The Free Trial pricing tier is intended only for evaluation purposes. Workspaces in the Standalone or Per Node pricing tiers have user-configurable retention from 30 to 730 days. Learn more about legacy pricing tiers.

The decision of whether workspaces with access to the legacy Per Node pricing tier are better off in that tier or in a current Pay-As-You-Go or Commitment Tier is often difficult for customers to assess. This involves understanding the trade-off between the fixed cost per monitored node in the Per Node pricing tier and its included data allocation of 500 MB/node/day and the cost of just paying for ingested data in the Pay-As-You-Go (Per GB) tier. To evaluate this, use the pricing tier recommendation query.

Yes, workspaces created before October 1, 2016 can continue use the Standard or Premium pricing tiers but can switch at any time to a newer tier above. The pricing tier below have not been available to any new workspaces since October 1, 2016.

The older pricing model offered two tiers—Basic, and Enterprise.

Enterprise tier customers can continue to stay on the older pricing model or can switch at any time to the above pricing model. All customer subscriptions with Application Insights enabled before April 2, 2018, are billed $- per GB for any data ingested by Application Insights. However, the only situation where this is advantageous if you’ve purchased the OMS Suite. In this case, each purchased unit of the Operations Management Suite E1 and E2 plans includes an entitlement to one node of the Enterprise tier of Application Insights. Each Application Insights Enterprise node includes up to 200 MB of Application Insights data ingested per day, with 90-day data retention at no additional cost.

No. Customers who started using Application Insights before April 2, 2018, will continue to be billed $- per GB for any data ingested by Application Insights.

You can set a daily cap on the amount of data that Application Insights will accept from your application, allowing you to control your costs. After the daily cap has been reached, excess data will be ignored for the remainder of the day (in UTC time), and then will resume normally at the start of the next day.

Additionally, you can use sampling to reduce the amount of data you send to Application Insights from your application.

Learn more about managing pricing and data volume in Application Insights.

Metric queries are charged based on the number of standard API calls. A standard API call is a call that analyzes 1,440 data points (1,440 is also the total number of data points that can be stored per metric per day). If an API call analyzes more than 1,440 data points, then it will count as multiple standard API calls. If an API call analyzes less than 1,440 data points, it will count as less than one API call. The number of standard API calls is calculated every day as the total number of data points analyzed per day divided by 1,440.

Examples

1. An API call that analyzes 2,000 data points will count as 2,000/1,440 = 1.4 standard API calls.
2. An API call that analyzes 200 data points will count as 200/1,440 = 0.1 standard API calls.
3. A scenario tracking five metrics with one-minute granularity from 100 VMs a day will result in 720,000 data points, which translates to (720,000/1,440) 500 standard API calls per day.

The price of an alert rule which monitors the CPU utilization, and RAM usage (i.e. 2 metric time-series) for 10 VMs, and has dynamic threshold enabled, can be calculated as, Price of alert rule + Price of dynamic threshold. For this example, the price would be calculated as:

Total monthly price = (10 VMs * 2 metric time-series per VM – 10 free units) * price per metric time-series per month + [(10 VMs * 2 metric time-series per VM) *price per dynamic threshold per month]

The price of an alert rule which queries 1 resource event every 15-minutes can be calculated as,

Total monthly price = 1 resource * 1 log alert rule * price per 15-minute internal log alert rule per month

The price of an alert rule which monitors 10 VM resources at 1-minute frequency, using resource centric log monitoring, can be calculated as Price of alert rule + Price of number of dimensions.

Total monthly price = price per 1-minute log alert rule per month + ( 10 time series - 1 included free time series ) * price per 1-min interval monitored per month

Pricing of at scale log monitoring is applicable from Scheduled Query Rules API version 2021-02-01

The migrated alert rules and corresponding migrated action groups (email, webhook, or LogicApp) will remain free of charge. The functionality you had with classic alerts including the ability to edit the threshold, aggregation type, and the aggregation granularity will continue to be available for free with your migrated alert rule. However, if you edit the migrated alert rule to use any of the new alert platform features, notifications or action types, a corresponding charge will apply. The following are examples of cases where you will incur a charge for your alert rule:

• Any new (non-migrated) alert rule created beyond free units, on the new Azure Monitor platform
• Any data ingested and retained beyond free units included by Azure Monitor
• Any multi-test web tests executed by Application Insights
• Any custom metrics stored beyond free units included in Azure Monitor
• Any migrated alert rules that are edited to use newer metric alert features like frequency, multiple resources/dimensions, Dynamic Thresholds, changing resource/signal, and so on
• Any migrated action groups that are edited to use newer notifications, or action types like SMS, Voice Call and/or ITSM integration

Activity log, service health and resource health alert rules continue to be available at no charge.

Alert notifications are charged separately based on the type of notification used.

You will not be charged for the first 250 log alert rules with frequency 5 minutes or more. Any alert rules above the 250 log alert rules limit or lower than 5 minutes frequency will be billed per the prices listed above.