Submit feedback on
Suboptimal Table Plan Selection in Log Analytics
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Suboptimal Table Plan Selection in Log Analytics
Jurian van Hoorn
Service Category
Other
Cloud Provider
Azure
Service Name
Inefficiency Type
Suboptimal Pricing Model
Explanation

By default, all Log Analytics tables are created under the Analytics plan, which is optimized for high-performance querying and interactive analysis. However, not all telemetry requires real-time access or frequent querying. Some tables may serve audit, archival, or compliance use cases where querying is rare or unnecessary. Leaving such tables on the Analytics plan results in unnecessary spend—especially when ingestion volumes are high or the table receives data from verbose sources (e.g., diagnostic logs, platform metrics).

Azure now allows users to assign different pricing plans at the table level, including the Basic plan, which offers significantly lower ingestion costs at the expense of reduced query functionality. This provides a valuable opportunity to align cost with access patterns by assigning less expensive plans to tables that are retained for record-keeping or compliance, rather than analysis.

Relevant Billing Model

Azure Log Analytics charges based on the ingestion volume and pricing plan assigned to each table. The default plan—Analytics—offers full query capabilities but is the most expensive option. The Basic plan is intended for low-access or audit-only data and provides lower-cost storage with limited query functionality. Costs can accumulate rapidly when high-ingestion tables default to the Analytics plan despite minimal interaction or querying needs.

Detection
  • Identify Log Analytics tables assigned to the default Analytics plan
  • Analyze which tables are infrequently queried or used solely for audit purposes
  • Review ingestion volume by table to identify high-cost, low-access data
  • Check whether verbose or chatty data sources are routed to high-cost plans unnecessarily
  • Confirm with application owners whether full query functionality is required for each table
  • Assess whether table plans are intentionally assigned or left at default
Remediation
  • Assign the Basic plan to tables that are retained for audit, archival, or compliance purposes
  • Split high-volume ingestion sources into separate tables based on access needs
  • Reconfigure ingestion routes to direct non-essential logs to lower-cost tables
  • Periodically audit table plan assignments to ensure alignment with usage patterns
Submit Feedback