Service Health: retirement of the Azure Monitor Log Analytics beta API on 31 March 2026

Hello Hans-Ole Larsen, the alert is telling you that somewhere you’re still calling the Logs Query API’s “beta” endpoints, which have to be switched over to the GA (v1) path by 31 March 2026. Unfortunately there’s no “magic” portal page that lists “beta” calls for you—you have to hunt them down in your code or in your workspace’s diagnostic logs. Here’s how you can review your usage:

1. Search your code/repositories, scripts and ARM templates for any of these patterns: • https://api.loganalytics.azure.com/beta/... • https://api.loganalytics.io/beta/... • https://management.azure.com/.../api/query?api-version=2017-01-01-preview (preview = beta) If you find any, change them to use the v1 path or a stable API-version.
2. Enable and collect Log Analytics diagnostic logs (Category: “Query”) for your workspace:
   • In the Azure portal go to your Log Analytics workspace → Diagnostic settings → Add
   • Send the logs to the same or another Log Analytics workspace
3. In that workspace, run a quick Kusto query to spot any beta‐endpoint usage: AzureDiagnostics | where Category == "Query" | where url_s contains "/beta/" If you see rows returned, that gives you the timestamp, client IP, user agent or calling application—use that to track down who’s issuing the beta call.
4. Update any libraries or tools (SDKs, PowerShell modules, ARM templates, Logic Apps, API Management policies, custom apps, etc.) so they point to the v1 endpoints.
5. Re-run the Kusto query above to confirm all “/beta/” calls have disappeared.

Hope that helps you pinpoint where the beta API is still in use!

Reference documentation

– Migrate from Logs Query API batch operation and beta version

Hans-Ole Larsen hi,

this alert usually means something in ur tenant is still calling the old Log Analytics beta endpoint even if u cannot see the word beta in ur code, most of the time it is not main application code but some old script automation account Logic App PowerShell module or even third party monitoring tool still using api.loganalytics.io instead of the newer monitor endpoint. U cannot see this directly inside Log Analytics tables, because the beta API usage is tracked at the identity and endpoint level, not inside the workspace.

The practical way to review it is to check entra sign in logs for service principals and filter for calls to api.loganalytics.io, that endpoint is the old API.

At Entra admin center open Enterprise Applications find apps that have access to Log Analytics open Signin logs and check the resource or URL being accessed. If something is calling api.loganalytics.io, that is the beta usage.

If u cannot find anything obvious the safest way is to open a ticket and ask msft to provide the application id that triggered the service health alert because they can see exactly which identity is still hitting the legacy endpoint.

rgds,

Alex