Skip to content
FinOps workspace
COST LEDGER / DECISION GUIDE

Azure Log Analytics cost optimization: workspace review

Published: 10 November 2026

Review ingestion, table plans and retention against the monitoring evidence your operations and security teams need.

Review my Log Analytics costs
Cloud infrastructure illustration in the mint and dark green Cost Ledger palette
Connect collected telemetry with its investigation purpose and billing owner.

Reconcile workspace costs before changing collection

The Azure Monitor Logs cost reference explains ingestion, retention and regional pricing. Where Microsoft Sentinel is enabled, some charges use Sentinel meters. Identify the workspace, tables, billing plan and active features before attributing a cost increase. A lower workspace subtotal is useful only when its scope is understood.

Review areaEvidence to collectOwner's decision
CollectionBillable volumes by table and originating resourceWhich events must remain available?
Table planCurrent plan, queries and dependent alertsWhich features does the use case need?
RetentionEffective retention and investigation needsHow must historical data be accessed?
Pricing tierRepresentative volume and existing commitmentDoes the remaining demand justify a tier change?
Security servicesSentinel status and relevant billing metersWhich team accepts the combined cost boundary?

Keep the review within the Azure cost optimization scope. Ask the owners of the Azure VM estate and AKS workloads to identify the telemetry sources they maintain. Record deployments or traffic changes that explain additional data before estimating an optimization opportunity.

Reduce unnecessary input with an acceptance test

Microsoft's Azure Monitor cost optimization guidance recommends reviewing collection, avoiding duplicate data and matching collection to operational requirements. Ask each owner to identify the alerts and investigation queries that depend on a proposed change. Start with an agreed sample and preserve evidence that those uses still work.

  • List the highest-volume tables and the resource owners behind them.
  • Check collection paths for duplicate or unused telemetry.
  • Agree the events and fields required for incident investigation.
  • Test a targeted change against the agreed operational queries.

The Azure Monitor Logs overview describes collection, routing and transformations before data reaches workspace tables. Confirm support for the actual source and destination before selecting a filtering design. Approve the missing-data boundary before applying a filter. Keep a record of what changes for alerting, troubleshooting and security investigation.

Compare table plans, retention and committed volume

Use the workspace table management guidance to inspect the current table plan and configuration. A candidate plan must support the required use case. Microsoft describes a trade-off for Basic Logs: lower ingestion cost with feature limitations and query charges. Check the current options against the official cost guidance before estimating a saving.

  1. Confirm the table's purpose and its dependent queries.
  2. Agree how long each category must remain available and how it will be accessed.
  3. Compare full ingestion, retention and query costs for the candidate configuration.
  4. Reassess pricing-tier assumptions after approved collection changes.

A commitment decision should use the demand expected to remain after those changes. Ask finance to compare the candidate with the existing commercial terms and any obligations already in place. Request the calculation and assumptions in an editable format. The Azure commitments review helps maintain the wider register; verify Log Analytics' own pricing-tier conditions independently.

Use a daily cap as a safeguard and measure the result

Microsoft's daily cap documentation explains that the cap can stop billable Analytics and Basic log collection, while Auxiliary tables are outside that cap. It recommends using the cap as a safeguard rather than a routine reduction mechanism. Stopping collection can affect monitoring and alerts. Do not treat the configured threshold as a guaranteed spending ceiling.

  • Assign an owner to unusual ingestion and the response procedure.
  • Document which data and downstream functions a cap can interrupt.
  • Review the approved change using the same workload and measurement period.
  • Retain the configuration, acceptance evidence and explanation of cost differences.

Measure configuration effects separately from workload effects. Compare source volumes and billed components alongside the application activity. Put accepted outcomes in the realized savings register. Include engineering effort and recurring administration in the cloud TCO review when a collection redesign needs implementation work.

The quote should identify whether it covers billing analysis, collection rules, table configuration, application logging or continuing review. Ask for editable queries and a configuration handover your operations team can maintain. Define who approves changes and who investigates a later increase in ingestion. Keep unresolved dependencies visible in the action register until the responsible owner accepts them.

Questions about Azure Log Analytics cost optimization

What should I review first for Log Analytics cost optimization?

Identify the largest billable sources and their owners, then check whether the collected data serves an approved monitoring or investigation use. Reconcile the applicable pricing plan and meters before estimating changes.

Is a daily cap a routine cost optimization method?

Microsoft recommends using it as a safeguard against unusual increases. Reaching it can stop covered log collection and affect monitoring. Review its scope and operational consequences before enabling it.

Are lower-ingestion table plans always cheaper overall?

Compare the complete use case, including query charges, retention and required features. A plan with lower ingestion pricing may not suit the queries or operational functions your team needs.

Get my FinOps quote