AWS
Microsoft Azure
Google Cloud
Key takeaways
1
Log ingestion and retention usually drive Azure Monitor pricing. Resource count alone cannot predict costs; collection settings and retention periods matter.
2
Basic and Auxiliary offer lower ingestion rates but charge for queries. Auxiliary also charges for processing.
3
Commitment tiers discount Analytics ingestion for a daily minimum payment. Uneven daily volume can make pay-as-you-go cheaper.
Azure Monitor pricing can become harder to predict when detailed logs stay enabled after troubleshooting. A useful monitoring budget accounts for what your team needs during an incident and what it needs to keep afterward.
The small and high-volume examples below connect those choices to monthly spending, alongside practical controls and a comparison showing why steady and uneven ingestion produce different commitment costs.
Agents, diagnostic settings and application instrumentation send that telemetry to Monitor for ongoing analysis, visualization and configured alerts. Logs enter tables inside a Log Analytics workspace; metrics use their own stores.
The Azure Monitor pricing below uses East US, USD public list rates checked November 5, 2026, against Microsoft’s pricing page and retail pricing API.
Rates vary by agreement, purchase date and currency. Microsoft Sentinel-enabled workspaces use Sentinel billing meters for Basic and Auxiliary ingestion, and for Analytics ingestion when on a Sentinel simplified plan tier.
The small and high-volume examples below connect those choices to monthly spending, alongside practical controls and a comparison showing why steady and uneven ingestion produce different commitment costs.
Azure Monitor pricing at a glance
Applications and Azure resources generate event records called logs, numeric metrics and traces that follow requests through an application.Agents, diagnostic settings and application instrumentation send that telemetry to Monitor for ongoing analysis, visualization and configured alerts. Logs enter tables inside a Log Analytics workspace; metrics use their own stores.
The Azure Monitor pricing below uses East US, USD public list rates checked November 5, 2026, against Microsoft’s pricing page and retail pricing API.
Rates vary by agreement, purchase date and currency. Microsoft Sentinel-enabled workspaces use Sentinel billing meters for Basic and Auxiliary ingestion, and for Analytics ingestion when on a Sentinel simplified plan tier.
| Component | Published rate | Billing condition |
|---|---|---|
| Analytics ingestion | $2.30/GB | Pay-as-you-go (PAYG), after applicable allowance |
| Basic ingestion | $0.50/GB | Queries separate |
| Auxiliary ingestion | $0.05/GB | Processing and queries separate |
| Auxiliary processing | $0.10/GB | All incoming data; ingestion after transformation |
| Extended interactive log retention | $0.10/GB-month | Beyond included retention |
| Long-term log retention | $0.02/GB-month | Retrieval can add charges |
| Basic/Auxiliary queries | $0.005/GB scanned | Based on data scanned |
| Standard platform metric collection | Free | Advanced metrics differ |
| Metric alerts | $0.10/time series/month | After included allowance |
| Log alerts evaluated every 15 minutes | $0.50/rule/month | Additional time series extra |
These are component rates, not an all-inclusive monitoring subscription. Our Azure pricing guide explains the wider service-by-service bill.
The legacy Free Trial tier has been closed to new workspace enrollment since July 2022.
Azure Monitor free features and allowances
Microsoft includes standard platform metric collection, Activity Log collection and up to 100 Activity Log alert rules per subscription. Analytics PAYG includes 5 GB/month per billing account, while metric alerts include 10 monitored time series/month. Platform metric queries include the first one million API calls/month.The legacy Free Trial tier has been closed to new workspace enrollment since July 2022.
Azure Monitor log pricing
Ingestion and log plans
Log plans explain much of the difference in Azure Monitor pricing between workloads. A plan applies to an eligible table, so one workspace can mix plans.| Plan | Practical use | Important trade-off |
|---|---|---|
| Analytics | Continuous monitoring and frequent investigations | Higher ingestion rate; interactive queries included |
| Basic | Troubleshooting data accessed less frequently | Query charges; separately billed Simple Log Alerts |
| Auxiliary | Verbose records and audit data | Processing and query charges; slower queries; no alerts |
Microsoft’s table-plan comparison identifies eligible tables and capabilities. Required alerts and investigation speed should determine suitability before price.
Azure bills calculated record size in decimal GB, not necessarily raw JSON file size. For Auxiliary, processing applies to incoming data before transformation. Sending 100 GB through unchanged therefore costs $10 processing plus $5 ingestion, before queries.
Microsoft lists a processing charge for Analytics and Basic Logs on data filtered beyond 50% of incoming volume, but its pricing page still says the billing start date will be announced. When Microsoft Sentinel is enabled on the workspace, transformations into Analytics tables are exempt, regardless of how much data they filter.
Microsoft lists 90 days of included retention for Analytics Logs in Sentinel-enabled workspaces; check each table’s configured retention and data tier rather than assuming a 90-day default. Sentinel-enabled workspaces can use Sentinel billing meters, so check that service’s pricing separately.
Retention settings distinguish readily queryable Analytics retention from lower-cost long-term storage. Analytics retention extends up to two years; total retention can reach 12 years. Reducing Analytics retention below its included period does not reduce ingestion charges.
For Basic/Auxiliary, query cost follows data scanned within the selected time range. Set a narrow range using the Log Analytics time picker or API timespan parameter; a KQL time filter alone does not replace that scope.
Ingesting 1,550 GB of Basic logs and scanning 10,000 GB costs $775 + $50 = $825, before other charges. Older-data access follows plan-specific query rules; search jobs can add scan and result-ingestion charges.
Native custom-metric ingestion is free during preview, although metrics API queries can incur charges. This allowance is separate from the paid workspace metric meters below.
Azure bills calculated record size in decimal GB, not necessarily raw JSON file size. For Auxiliary, processing applies to incoming data before transformation. Sending 100 GB through unchanged therefore costs $10 processing plus $5 ingestion, before queries.
Microsoft lists a processing charge for Analytics and Basic Logs on data filtered beyond 50% of incoming volume, but its pricing page still says the billing start date will be announced. When Microsoft Sentinel is enabled on the workspace, transformations into Analytics tables are exempt, regardless of how much data they filter.
Retention and older data queries
Retention means how long stored records remain available. General Analytics ingestion includes 31 days; Basic/Auxiliary include 30, and Application Insights data includes 90.Microsoft lists 90 days of included retention for Analytics Logs in Sentinel-enabled workspaces; check each table’s configured retention and data tier rather than assuming a 90-day default. Sentinel-enabled workspaces can use Sentinel billing meters, so check that service’s pricing separately.
Retention settings distinguish readily queryable Analytics retention from lower-cost long-term storage. Analytics retention extends up to two years; total retention can reach 12 years. Reducing Analytics retention below its included period does not reduce ingestion charges.
For Basic/Auxiliary, query cost follows data scanned within the selected time range. Set a narrow range using the Log Analytics time picker or API timespan parameter; a KQL time filter alone does not replace that scope.
Ingesting 1,550 GB of Basic logs and scanning 10,000 GB costs $775 + $50 = $825, before other charges. Older-data access follows plan-specific query rules; search jobs can add scan and result-ingestion charges.
Application Insights billing
Workspace-based Application Insights stores application telemetry in Log Analytics. Its ingestion and retention are billed through that workspace, so count that volume once. Standard availability tests have separate execution charges; exporting data and paid notifications can also add costs.Azure Monitor metrics and alert pricing
Metrics ingestion and queries
Azure Monitor pricing for metrics depends on their type and destination. Standard platform metrics are free to collect; advanced platform metrics are a paid, opt-in feature for supported resources.Native custom-metric ingestion is free during preview, although metrics API queries can incur charges. This allowance is separate from the paid workspace metric meters below.
| Metrics meter | East US USD rate |
|---|---|
| Advanced platform samples ingested | $2 per 10 million |
| Workspace metric samples ingested | $0.11 per 10 million |
| Workspace metric samples processed | $0.05 per 10 million |
| Workspace metric query samples processed | $0.001 per 10 million |
| Platform metric API calls beyond allowance | $0.01 per 1,000 |
Workspace entries are published meter rates, not a combined charge; verify which apply to your pipeline before summing them. Managed Prometheus uses ingestion/query billing with 18 months of retention included.
Log-alert evaluation frequency matters: a five-minute rule costs $1.50/month before additional time series, versus $0.50 at 15 minutes. Simple Log Alerts use the one-minute alert pricing basis; queries against Basic logs also incur scanned-data charges. Dynamic metric thresholds add charges; notification pricing is separate from rule pricing.
The 100 GB/day tier costs $196/day, or $1.96/GB when fully used. The 500 GB/day tier costs $865/day, or $1.73/GB. Retention, Basic/Auxiliary and alerts remain separate.
Microsoft’s commitment rules specify tier-rate overage and a 31-day commitment period. Increasing the tier restarts the period; lowering it or returning to PAYG normally requires waiting, with a six-hour correction window after configuration.
Alert rules and notifications
A time series is one monitored metric for one resource and dimension combination. More resources or dimensions can therefore increase charges without adding rules.Log-alert evaluation frequency matters: a five-minute rule costs $1.50/month before additional time series, versus $0.50 at 15 minutes. Simple Log Alerts use the one-minute alert pricing basis; queries against Basic logs also incur scanned-data charges. Dynamic metric thresholds add charges; notification pricing is separate from rule pricing.
How Log Analytics commitment tiers affect costs
Commitment tiers reduce the ingestion component of Azure Monitor pricing through a fixed daily payment. They cover Analytics ingestion, separately from Azure Savings Plans and Reserved Instances.The 100 GB/day tier costs $196/day, or $1.96/GB when fully used. The 500 GB/day tier costs $865/day, or $1.73/GB. Retention, Basic/Auxiliary and alerts remain separate.
Microsoft’s commitment rules specify tier-rate overage and a 31-day commitment period. Increasing the tier restarts the period; lowering it or returning to PAYG normally requires waiting, with a six-hour correction window after configuration.
Why daily ingestion changes commitment costs
Consider two illustrative 31-day patterns, each ingesting 3,100 GB. Assume the entire 5 GB PAYG allowance is available; exclude all other charges.| Daily pattern | PAYG ingestion | 100 GB/day tier |
|---|---|---|
| 100 GB every day | $7,118.50 | $6,076 |
| 15 days at 180 GB, 15 at 20 GB, one at 100 GB | $7,118.50 | $8,428 |
PAYG is (3,100 − 5) × $2.30. The variable commitment costs 31 × $196 + 15 × 80 × $1.96: low days still incur the minimum, while high days add overage. The same monthly volume can produce different commitment costs.
If Microsoft Sentinel is enabled, check the workspace’s pricing tier and whether Sentinel data lake is enabled before applying these Monitor-only examples.
Ingestion is (31 − 5) × $2.30 = $59.80. Metric alerts add (20 − 10) × $0.10 = $1; the log rule adds $0.50. Subtotal for these charges is $61.30/month.
Azure Monitor pricing examples
These Azure Monitor pricing examples are illustrative estimates, not invoices. Both use East US USD rates and 31 days. Allowances are available independently for each scenario. Taxes, negotiated discounts, Sentinel, export, web tests, paid metrics and notifications are excluded.If Microsoft Sentinel is enabled, check the workspace’s pricing tier and whether Sentinel data lake is enabled before applying these Monitor-only examples.
Small monitoring setup
Assume 1 GB/day of Analytics logs, 31-day retention, 20 static metric-alert time series and one 15-minute log-alert rule without additional dimensions.Ingestion is (31 − 5) × $2.30 = $59.80. Metric alerts add (20 − 10) × $0.10 = $1; the log rule adds $0.50. Subtotal for these charges is $61.30/month.
High volume monitoring setup
Assume steady 500 GB/day of general Analytics logs, the 500 GB/day commitment, 90-day interactive retention, 100 static metric-alert time series and ten five-minute log rules without extra dimensions.| Monthly component | Planning calculation | Cost |
|---|---|---|
| Ingestion | 31 × $865 | $26,815 |
| Extended retention | 500 × (90 − 31) × $0.10 | About $2,950 |
| Metric alerts | (100 − 10) × $0.10 | $9 |
| Log alerts | 10 × $1.50 | $15 |
| Approximate subtotal | Charges shown | $29,789 |
Retention assumes a mature, steady-state deployment with approximately 29,500 GB beyond the included window. It is a monthly planning approximation; actual retention is prorated daily. A new workspace builds that inventory over time.
PAYG ingestion alone would be $35,638.50 with the available 5 GB allowance. The comparison shows why both daily ingestion and retained inventory belong in the budget.
Also read our Azure cost management dashboard guide for recurring exports and reporting.
Then apply Microsoft’s cost controls in this order:
PAYG ingestion alone would be $35,638.50 with the available 5 GB allowance. The comparison shows why both daily ingestion and retained inventory belong in the budget.
How to estimate and reduce Azure Monitor costs
An Azure Monitor pricing estimate needs your own quantities. Microsoft’s cost-estimation guidance recommends observing a representative subset of resources when volumes are unknown, then using the calculator.Find your actual usage and charges
Use Workspace Insights to find large tables and contributing resources. Usage and estimated costs compare ingestion pricing options. In Cost Management, group charges by meter and check the Azure Monitor, Log Analytics, Insight and Analytics, and Application Insights service names.Also read our Azure cost management dashboard guide for recurring exports and reporting.
Then apply Microsoft’s cost controls in this order:
1
Remove duplicate collection and unnecessary diagnostic categories; sample suitable application telemetry.
2
Match eligible tables to required queries and alerts before changing plans.
3
Keep logs needed for quick incident investigations readily queryable, and retain audit or compliance records for the required period.
4
Review alert frequency, dimensions and notification choices.
5
Recalculate commitment options after collection changes.
Protect incident evidence throughout. A daily cap is an emergency safeguard for Analytics and Basic logs: it can stop collection, affect monitoring and still overshoot. It does not apply to Auxiliary logs.
We start with a read-only Savings Test; purchasing requires separate authorization.
If an eligible Flex Commitment costs more than equivalent pay-as-you-go usage, we provide Cashback protection for the qualifying difference, subject to your agreement and program terms. Our protection does not cancel the underlying commitment, and we do not automatically protect existing customer-owned commitments as Flex Commitments.
We charge an agreed percentage of realized savings, so the fee applies when verified savings are generated.
Where Usage.ai fits in your Azure costs
The controls above address Azure Monitor costs directly. For supported workloads elsewhere in your Azure bill, we purchase and manage Reservations and Savings Plans through our Flex Insured Commitment Program, following your approval. These are separate from Log Analytics ingestion commitment tiers.We start with a read-only Savings Test; purchasing requires separate authorization.
If an eligible Flex Commitment costs more than equivalent pay-as-you-go usage, we provide Cashback protection for the qualifying difference, subject to your agreement and program terms. Our protection does not cancel the underlying commitment, and we do not automatically protect existing customer-owned commitments as Flex Commitments.
We charge an agreed percentage of realized savings, so the fee applies when verified savings are generated.
Plan your Azure Monitor budget
Build your Azure Monitor pricing estimate around necessary telemetry, daily ingestion and retained inventory. Compare the result with actual meters before approving changes. For supported commitments elsewhere in your Azure environment, our Savings Test can assess additional opportunities.
Use the Azure Monitor pricing calculator with regional rates, ingestion by plan, retained data, query scans, metrics and alerts. Add relevant extras and compare estimates with billed usage.
Frequently asked questions
Is Azure Monitor free?
Azure Monitor pricing includes free features and usage allowances, including standard platform metric collection. Paid ingestion, retention beyond included periods and other enabled features can still produce charges.
How do I calculate my monthly Azure Monitor cost?
Use the Azure Monitor pricing calculator with regional rates, ingestion by plan, retained data, query scans, metrics and alerts. Add relevant extras and compare estimates with billed usage.
Are Basic Logs cheaper than Analytics Logs?
Basic ingestion costs less, but queries are billed separately. Total cost depends on scanned volume and required features; lower ingestion pricing alone does not establish suitability.
Is Application Insights billed separately from Log Analytics?
Workspace-based telemetry ingestion and retention are billed through Log Analytics. Count that data once; features such as Standard web tests can add separate charges.
When do Log Analytics commitment tiers save money?
When daily eligible Analytics ingestion supports the tier’s minimum charge. Compare each day’s commitment cost and overage against PAYG; a monthly average can hide underused days.
Share
Facebook
X
LinkedIn
Reddit
