Share via

Need help to identify objects related to “Action required: Prepare for the retirement of the Azure Monitor Log Analytics beta API on 31 March 2026”

Sahil Manchanda 20 Reputation points Microsoft Employee
2026-03-27T06:30:29.08+00:00

Hi Team, we got a Service Health notification titled "Action required: Prepare for the retirement of the Azure Monitor Log Analytics beta API on 31 March 2026"

We found the service Health advisory on Azure portal

Subscription Ids:

Subscription ID:

Azure Monitor
Azure Monitor

An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.

0 comments
Answer accepted by question author
  1. Siva shunmugam Nadessin 8,405 Reputation points Microsoft External Staff Moderator
    2026-03-27T10:34:17.5566667+00:00

    Hello Sahil Manchanda,

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

    The Service Health alert you’re seeing refers to the retirement of the Azure Monitor Log Analytics “beta” Query API on March 31, 2026. After that date, any calls to the beta endpoint (for example, https://api.loganalytics.io/v1beta/query) will stop working. To get ahead of this retirement, you need to:

    Identify every “object” that’s calling or depending on the beta API. Typical  include:

    • Custom applications or scripts (C#, Python, PowerShell, CLI) invoking the beta URL

    • Azure Logic Apps or Power Automate flows using the HTTP action against /v1beta

    • Azure Data Factory or Synapse pipelines with REST dataset pointing at v1beta

    • Azure Automation Runbooks or Functions querying the beta endpoint

    • Third-party tools or dashboards referencing the beta route

    • API keys or secrets stored in your workspace’s API Access blade

    Use these methods to locate them:

    • Search your repos: grep for “api.loganalytics.io/v1beta” or “/beta/query” & Log Analytics workspace:   open each workflow and search HTTP actions for “v1beta”.
    • Azure Resource Graph:   Query resources whose properties contain “v1beta”.   Example: resources    | where properties contains "v1beta"
    • Activity Log or Diagnostic Logs on your Log Analytics workspace: – Enable Workspace Logs for “Query” operations.   – Run a Kusto query on the workspace’s Diagnostics:   OperationName == “QueryWorkspace” and RequestUri contains “/v1beta”  
    • Inventory your API keys in the portal (Workspace → API Access) so you know which scripts use them.

    Plan the migration:

    • Switch all calls from the beta endpoint (/v1beta/) to the GA endpoint (/v1/).
    • Update client code authentication if needed (bearer tokens via Azure AD).
    • Test each integration before March 2026 to ensure queries still work.

    Reference List

    • Monitoring Support for AKS-Engine retirement https://supportability.visualstudio.com/CAIProductUpdates/_wiki/wikis/CAIProductUpdates.wiki/1197405/Azure%20Retirement/Monitoring%20Support%20for%20AKS-Engine%20retirement

    • Outlook REST API v2.0 and beta endpoints decommissioning https://supportability.visualstudio.com/M365%20Release%20Announcements/_wiki/wikis/M365-Product-Updates.wiki/1443342/Exchange%20|%20Outlook%20|%20OWA/Outlook%20REST%20API%20v2.0%20and%20beta%20endpoints%20decommissioning

    • A solution I use is being retired https://supportabilityhub.microsoft.com/solutions/apollosolutions/6880a9f4-7ca4-a063-67c4-6d56604ce28d/apollo-644cd5e5-d19b-476f-b2e5-4fb1461636b2

    • Data Access API key retirement https://supportabilityhub.microsoft.com/solutions/apollosolutions/e58fa03a-b33c-05ac-1dbe-6cd17d77f9f4/5cfc5cf1-073c-4a6c-bed5-2826a04a8fe1

    • Diagnostic settings will replace the legacy solution for forwarding Azure activity logs https://supportabilityhub.microsoft.com/solutions/apollosolutions/43f23937-a72d-efcd-9772-b656c2e480d1/c88d2d0e-991b-49b1-8bc7-7da8cea24546

    • Alchemy_Misroute_AzureMonitor https://supportabilityhub.microsoft.com/solutions/apollosolutions/166a9330-13e8-1173-8808-55f87c6284b6/a61d46ea-63ed-44ee-9d39-9ca79a344f1a

    • Azure Business Continuity center – Help with Monitoring https://supportabilityhub.microsoft.com/solutions/apollosolutions/3ecc4a29-acdb-d2f3-a83f-32e69b2a9145/e563d505-52b5-425c-b4d0-871864807fcb

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-27T06:30:46.9366667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The Service Health advisory for the Log Analytics beta API retirement is surfaced correctly, but the “We were unable to fetch data” message indicates that the portal cannot load the detailed data for that advisory, including the list of impacted resources.

    To identify the impacted objects and work around this:

    1. In the Azure portal, go to Service Health → Health advisories and select the retirement advisory.
    2. In the advisory blade, use the Impacted Resources tab. This tab is where Azure lists all resources affected by a retirement event, including:
      • Resource Name
      • Resource Type
      • Resource Group
      • Region
      • Subscription ID
      • Subscription name
    3. Use the filters in the Impacted Resources tab to narrow the list by:
      • Region
      • Subscription ID
      • Resource Type
    4. If the tab still fails to load and shows “unable to fetch data,” export is not possible from the portal view. In that case, open a support request so the Azure support team can:
      • Investigate why the Service Health advisory details are not loading for the subscription.
      • Provide the list of impacted resources for the retirement.

    When the Impacted Resources tab loads successfully, select Export to CSV to download the full list of affected resources and analyze or share it internally.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.