Clarification on Azure Monitor Log Analytics beta API retirement alert when no direct beta API usage is found

Question

Hi,

We received the Service Health notification titled “Action required: Prepare for the retirement of the Azure Monitor Log Analytics beta API on 31 March 2026”.

After reviewing our codebase and services, we did not find any direct usage of the Log Analytics beta query APIs. We are not programmatically querying Log Analytics data via custom scripts or services.
If no direct beta API usage is present, can this alert be considered informational with no action required?

Answer 1

Hello Adebisi Thompson,

Thank you for reaching out to the Microsoft Q&A forum.

Yes — in your scenario, this can be treated as informational only, with no immediate action required, provided your assessment is accurate.

A few quick validations to be 100% sure

 When you can safely ignore it

You are not calling Log Analytics REST APIs with paths like:

/v1/workspaces/{workspaceId}/query (older/beta variants)

No usage of preview SDKs or custom integrations querying Log Analytics

You rely only on:

• Azure Portal queries (Logs blade)
• Azure Monitor features (alerts, workbooks, etc.)
• Standard SDKs using GA endpoints

Double-check these edge cases

Sometimes usage is indirect:

Automation scripts (PowerShell/CLI) using older modules

Third-party tools or internal apps querying Log Analytics

Legacy integrations using preview API versions

If none of the above apply, the retirement of the beta API will not impact your environment, and the notification is just a broad Service Health advisory.

 

If the answer is helpful, Please do not forget to  and “up-vote” this can be beneficial to other community members.

Thanks,

Siva shunmugam.

Answer 2

The retirement notification is not purely informational; action is required if any component in the environment still calls the Azure Monitor Logs Query beta endpoints or uses the batch operation.

Key points from the retirement guidance:

1. Beta API version retirement (March 31, 2026)
   The Logs Query API beta version is being deprecated. The required migration step is to change the path from beta to v1 in any API calls. Examples of affected endpoints include:
   • https://api.loganalytics.azure.com/beta/
   • https://api.loganalytics.io/beta/
   • https://api.applicationinsights.azure.com/beta/
   • https://api.applicationinsights.io/beta/
2. Batch operation retirement (March 31, 2028)
   The batch query operation is also being deprecated. The guidance is to split batch queries into single queries.
3. What to do if no direct usage is found in code
   Even if there is no custom code or scripts using these endpoints, the alert can still be relevant if:
   • Third‑party tools, integration platforms, or monitoring add‑ons are configured to query Log Analytics or Application Insights using beta endpoints.
   • Legacy scripts, automation accounts, or pipelines outside the main codebase are using beta or batch.
   The notification means Azure has detected at least some usage of the retiring features in the subscription/tenant. To treat the alert as “no action required,” it is necessary to verify that all callers (including external tools and older automations) have migrated to v1 and are not using batch.
4. How to validate and remediate
   • Inventory any tools or services that query Log Analytics or Application Insights via REST or SDKs.
   • For any that construct URLs manually, confirm they use /v1 instead of /beta and do not call batch.
   • If any beta usage is found, update the endpoint path to v1 as described in the migration guidance.

If, after checking all integrations (not only the main codebase), there is truly no remaining beta or batch usage, then no further technical change is required; the notification can then be treated as informational for the environment.

---

References:

• Migrate from Logs Query API batch operation and beta version