Error Retrieving Data after App Insights Rename

Rolan Shun 0 Reputation points
2025-10-15T12:53:59.52+00:00

I recently renamed a Azure Insights. I reconnected all my functions and apps to it without errors. When I try to view the Insights blade, all I get is "error retrieving data" anywhere.

Did I break something by renaming the resource? I have the correct instrumentation key and verified it multiple times.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
{count} votes

1 answer

Sort by: Most helpful
  1. Sandhya Kommineni 1,575 Reputation points Microsoft External Staff Moderator
    2025-10-23T04:09:46.5633333+00:00

    Hi Rolan Shun,Thanks for posting your question in Microsoft Q&A forum

    When an Application Insights resource is renamed, only the resource name (display name) changes. The underlying resource ID (GUID) and instrumentation key (ikey) remain the same, so your applications can still send telemetry without interruption.

    However, certain Azure Portal blades and dashboards such as Usage, Failures, Performance, and Availability may cache the previous resource name internally. After the rename, this cached reference can cause the portal’s front-end to fail to resolve telemetry data correctly, resulting in the Error retrieving data message.

    It’s important to note that this issue affects only the portal UI display. Telemetry ingestion continues to work as expected, and you can still view and query data successfully through the Logs (Kusto) section.

    Here are the ways to fix or work around it

    1.Clear Browser Cache or Use a Private/Incognito Window

    As a first step, try opening the Azure portal in a Private/Incognito browser window.

    Navigate to your renamed Application Insights resource.

    Check the Overview, Failures, and Performance tabs.

    If the data displays correctly in the private session, the issue was likely caused by local browser cache. Clearing your regular browser cache or continuing to use a private window should resolve the portal display issue.

    2.To verify, open the Logs blade and run a simple query such as:

    requests
    | take 5
    
    • If data is returned, your telemetry pipeline is functioning correctly, and the issue is limited to the Azure Portal view.

    3.Verify Instrumentation Key or Connection String: Even if the Ikey matches, verify that all connected services and apps use the correct connection string (particularly if you use the APPLICATIONINSIGHTS_CONNECTION_STRING setting).

    4.Delete and Recreate If Necessary: If issues persist, consider creating a new Application Insights resource with the desired name and reconnect apps, as full rename support may have limitations

    Please try the steps mentioned and let me know if they resolve the issue.

    I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes & upvote if the answer is helpful so that it can help others in the community.

    0 comments No comments

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.