Azure Monitor pricing: What you pay vs. what you get

Azure Monitor doesn't have a price. It has a bill and those are very different.

There's no plan tier to pick, monthly set fee, or simple number to sanity-check against your budget. Instead, you're charged across a handful of separate meters: log ingestion, log queries, retention, alert rules, web tests, and custom metrics. Each of these metrics scale independently. Most teams don't see the full cost until the bill arrives.

This article covers what each component actually costs, where bills tend to grow faster than expected, and how OpManager Nexus compares if cost predictability matters.

How Azure Monitor charges work

The pay-as-you-go model means your bill reflects usage across every component you touch. Platform metrics and activity log collection are included at no charge by default. Everything else, especially once you're ingesting logs at any real volume, runs on consumption meters.

The Azure Monitor bill is mostly Log Analytics. Understand that, and you understand most of your invoice. Here's what each meter costs, starting with the one that matters most.

Log ingestion: The line item that surprises people

Azure Monitor classifies log data into three tiers. Analytics Logs cost $2.30/GB and give you full query, alerting, and visualization capability—this is where most teams send their logs by default. Basic Logs cost $0.50/GB but come with limited query functions and can't support the full range of alerting. Auxiliary Logs are $0.05/GB, suited to data you want to retain but rarely search.

The first 5GB per month is free. After that, every gigabyte of Analytics Logs costs $2.30.

That rate is what catches teams off guard. A modest environment sending 500GB of Analytics Logs per month runs to around $1,150 before retention, alerts, or anything else. Scale that to 2–3TB, not unusual for a mid-sized org with application logging fully enabled, and you're looking at $4,600–$6,900 on log ingestion alone.

Commitment tiers exist, but the discounts don't kick in meaningfully until you're at scale. The entry-level 100 GB/day commitment comes to $196/day, an effective $1.96/GB—about 15% off. The widely-quoted 30% discount only arrives at 5,000 GB/day.

Query costs: Basic logs aren't as cheap as they look

The obvious cost-cutting move is routing high-volume logs to Basic. The catch: Basic Logs queries are charged separately based on the amount of data scanned. If you're actively searching those logs during incidents—which is when you need them most—you're paying the ingestion and query costs.

The right approach is to route logs you won't often search to Basic or Auxiliary (verbose audit trails or raw gateway logs), and keep anything your team actually investigates in Analytics. Using Basic as a blanket cost-reduction measure tends to produce unexpected query bills.

Retention

Log data retention is free for the first 31 days. After that, interactive retention for Analytics Logs runs approximately $0.10/GB per month (up to two years), and long-term retention costs around $0.02/GB per month.

Retention costs accumulate quietly. An environment retaining 1TB of Analytics Logs beyond the free window pays roughly $100 per month in retention charges alone, on top of ingestion. Most compliance and operational requirements mandate 90-day, 180-day, or longer retention—so this line item is rarely optional.

Alerting

Alert rule billing is more granular than a simple per-rule charge, and it's easy to underestimate early when rule counts are small.

• Activity Log alerts : Free, up to 100 rules per subscription.
• Metric alerts : 10 monitored time series free per month; each additional time series after that is $0.10/month.
• Dynamic thresholds : ML-based anomaly detection instead of static values. Doubles the cost per alert rule.

Multi-resource rules : A single rule watching several resources creates one time series per resource, billed independently.

As monitoring matures and teams add coverage for more resources and failure conditions, both rule count and frequency tend to increase. The bill follows.

Availability testing

Standard web tests are priced per test, location, and month. Teams monitoring several endpoints from multiple Azure regions to catch geo-specific issues see these costs multiply quickly. Five endpoints tested from six locations is thirty test-location combinations, billed monthly.

Take a mid-sized environment: 800GB/month of Analytics Logs, 90-day retention, 150 alert rules at 5-minute intervals, and Application Insights on a dozen services. Log ingestion alone runs about $1,830/month. Retention beyond the free 31 days adds roughly $170/month on the retained volume. Alert rules at that frequency and count typically land in the $200–400/month range depending on dimension splits. Before web tests or custom metrics, that's already $2,200–$2,400/month, and it moves every time log volume or rule count changes.

What actually drives the bill higher

Most Azure Monitor cost overruns trace back to a handful of patterns.

Enabling diagnostic settings broadly during initial setup—which is quick and easy—often results in higher log ingestion than expected, particularly when verbose log categories are left on by default. Retention beyond 31 days adds ongoing per-GB charges that compound as data accumulates. Alert rule proliferation, where teams add coverage incrementally over time without auditing existing rules, pushes both rule-count and frequency costs upward. Applications instrumented with Application Insights and emitting custom telemetry generate large volumes of custom metric samples at $0.16 per 10 million. This is easy to miss in initial estimates.

None of these is unreasonable in isolation. Together, growing month over month, they make Azure Monitor hard to budget for.

Azure Monitor and application performance monitoring

Azure Monitor covers APM through Application Insights. Worth knowing: Application Insights (workspace-based) bills at the same Log Analytics rates as the rest of your telemetry. Traces, exceptions, and dependency data land in Log Analytics and are charged accordingly—there's no separate APM tier, and all the ingestion and retention costs above apply equally to your APM data.

This means APM costs are not a separate line item to budget for—they are part of your log ingestion and retention total, using the same tier structure (Analytics, Basic, Auxiliary) and the same commitment tier discounts.

Where OpManager Nexus fits

For many teams, the consumption model is the core issue. OpManager Nexus is built differently—and priced that way too. Billing is based on the number of resources you monitor, not the volume of data they produce. A 500-host Azure environment costs the same whether those hosts are generating 100GB or 1TB of telemetry per month. You know what you'll pay before the month starts.

OpManager Nexus covers Azure alongside AWS, GCP, and on-premises infrastructure from the same console, which matters when your environment extends beyond Azure.

Comparison table (Azure Monitor vs. OpManager Nexus):

Comparing OpManager Nexus against Datadog, Dynatrace, or similar platforms? The Azure Monitor alternatives article breaks down how each is priced, what each covers, and where each fits.

For the full picture on Azure observability with OpManager Nexus, start at the Azure Observability hub .

Frequently asked questions (FAQs)

1. How much does Azure Monitor cost per month?
   There is no fixed monthly cost. Azure Monitor bills across several consumption meters: log ingestion ($2.30/GB for Analytics Logs after a 5GB free allowance), retention beyond 31 days ($0.10/GB/month for interactive retention), alert rules (varies by type, frequency, and dimension splits), custom metrics ($0.16 per 10 million samples), and availability tests (per test per location per month). A 500 GB/month Analytics Logs environment pays approximately $1,150 in ingestion alone, before retention or alerts.
2. What is the cheapest way to reduce Azure Monitor costs?
   Three levers have the most impact. First, route verbose logs you rarely query—gateway logs, raw audit trails, debug output—to Basic Logs ($0.50/GB) or Auxiliary Logs ($0.05/GB) rather than Analytics Logs ($2.30/GB). Second, audit your alert rules for query frequency: rules running at 1- or 5-minute intervals cost significantly more than the same rules at 15-minute intervals. Third, at 100 GB/day or above, switch to a commitment tier—the entry tier delivers approximately 15% off the pay-as-you-go rate.
3. Does Azure Monitor charge for Application Insights separately?
   Not for workspace-based Application Insights deployments, which is the current default. Traces, exceptions, and dependency data all land in your Log Analytics workspace and are billed at the same per-GB rates as the rest of your log data. There is no separate APM tier. Classic Application Insights (non-workspace-based) has different billing behavior—if you're on a legacy deployment, verify which model applies to your workspace.
4. What is the difference between Azure Monitor Analytics Logs and Basic Logs?
   Analytics Logs ($2.30/GB) give you full KQL query support, all alerting types, and up to two years of interactive retention. Basic Logs ($0.50/GB) offer limited query capability, support for simple log alerts only, and queries are charged separately by data scanned rather than included in the ingestion rate. The right split is to keep logs you actively investigate in Analytics and route high-volume logs you rarely search to Basic or Auxiliary.
5. How do Azure Monitor commitment tiers work?
   Commitment tiers apply to Analytics Logs ingestion only—Basic Logs and Auxiliary Logs are billed at flat per-GB rates regardless of tier. The entry commitment starts at 100 GB/day ($196/day in East US), which works out to an effective $1.96/GB—approximately 15% off the pay-as-you-go rate. The widely cited 30% discount only applies at the 5,000 GB/day tier. Commitment periods run for 31 days from selection; you cannot drop to a lower tier mid-period. Any overage above the committed volume is billed at the same tier rate, not at the higher pay-as-you-go rate.