Azure Managed Grafana
An Azure service used to deploy Grafana dashboards for analytics and monitoring solutions.
Can someone please start looking into 2608050030007864
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 82%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Yashwant Shettigar
0
Reputation points Microsoft Employee
This issue is related to grafana prometheus plugin loading issue after upgrade.
Azure Managed Grafana
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 93%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
Venkatanaidu Madamanchi 0 Reputation points Microsoft External Staff Moderator2026-08-06T09:11:32.5466667+00:00 Thank you for contacting Microsoft Support.
I understand that you are experiencing a Prometheus** plugin loading issue in Grafana after an **upgrade. I will be happy to assist you with the investigation.
To help us identify the root cause, could you please provide the following details?
- What are the current versions of Grafana and the Prometheus** **plugin after the upgrade?
- Are you receiving any specific error** messages, warnings, or error **codes when the plugin fails to load? If so, please share the exact error message and a screenshot if available.
- Was the upgrade performed manually or through an automated** deployment/upgrade **process?
- Were any changes made to the Grafana configuration, data sources, authentication settings, or underlying environment before the issue began?
- Could you also share the relevant Grafana logs captured during the plugin loading failure?
Once we have this information, we can perform a detailed analysis and help determine the cause of the issue.
Looking forward to your response.
Regards,
Venkat.M
Mail: v-vemadamanc@microsoft.com
-
Yashwant Shettigar 0 Reputation points Microsoft Employee
2026-08-06T09:57:38.1533333+00:00 @Venkatanaidu Madamanchi Please find details below :
What are the current versions of Grafana and the Prometheus** **plugin after the upgrade?- Are you receiving any specific error** messages, warnings, or error **codes when the plugin fails to load? If so, please share the exact error message and a screenshot if available.
- Error message: *"Managed_Prometheus_aks-mw-shared-dev-southcentralus plugin failed. Error: Could not load plugin"
*
- Was the upgrade performed manually or through an automated** deployment/upgrade **process?
- It was automated upgrade of Grafana done by Azure Managed Grafana user
- Were any changes made to the Grafana configuration, data sources, authentication settings, or underlying environment before the issue began?
No changes done to environment with respect to any configuration, data sources, authentication settings, etc. This occurred only after the automated updates were pushed - Could you also share the relevant Grafana logs captured during the plugin loading failure?
I am not able to locate logs for Grafana
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 65%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
Sreetheja Adusumilli 965 Reputation points Microsoft External Staff Moderator2026-08-08T07:02:47.6+00:00 Hello @Yashwant Shettigar ,
Thank you for sharing the details. After reviewing the behavior, the "Could not load plugin" error appears to be occurring before Grafana even reaches the authentication or query stage. This is important because it suggests we're dealing with a plugin loading issue rather than a permissions, authentication, or connectivity problem.
What makes this particularly interesting is that the issue started immediately after the automatic upgrade from Grafana 13.0.2 to 13.1.0 on August 5th and is reproducible for all users, even in private browsing sessions. Based on that behavior, this appears less likely to be related to your tenant configuration and more likely related to how the plugin is being delivered or loaded after the upgrade.
For context, beginning with Grafana 13, Azure authentication for Prometheus is provided through the Azure Monitor Managed Service for Prometheus plugin. Existing data sources are expected to migrate automatically during the upgrade process. Since your data source type already shows "Azure Monitor Managed Service for Prometheus," the migration itself appears to have completed successfully. The current issue is that the plugin is not loading correctly.
Regarding Grafana logs, there's no need to spend time searching for server-side logs. In Azure Managed Grafana, those plugin logs are not exposed to customers. The most useful information will come directly from the browser.
To help narrow this down, I'd recommend the following:
- Open the failing data source page with DevTools running. Press F12 → Network tab → check Disable cache → reload the page. Filter on plugin. This matters because it shows you the literal HTTP response for the plugin asset, which is the one thing that separates "asset missing" from "asset broken." To verify: You should see a request for the plugin's module.js under a /public/plugins/… path. Note its status code. 404 or 403 = the plugin asset isn't being served correctly by the platform — that's service-side and not fixable from your end.
- Switch to the Console tab and capture the red error. Don't summarize it — copy the full stack trace. A module-load exception with a version mismatch reads very differently from a straight fetch failure, and it changes who needs to fix it. To verify: You have a JS error referencing the plugin path or a SystemJS/module import failure.
- Check the plugin's install state in the Azure portal. Open your Azure Managed Grafana workspace → Plugin management. Installed plugins appear at the top of the list with an Installed tag. Note that plugin management can only be done here — not from the Grafana UI, and not from Azure CLI. To verify: The plugin is listed with the Installed tag. If it isn't there at all while data sources of that type exist, your workspace is in an inconsistent post-upgrade state and that's worth flagging immediately.
- Test with a freshly created data source on a non-production workspace (do not delete the existing one — removing a data source used by dashboards breaks those dashboards and produces errors or empty panels). In Grafana: Connections > Data sources > Add data source → select Azure Monitor Managed Service for Prometheus → paste the query endpoint from your Azure Monitor workspace Overview page into Prometheus server URL → Authentication = Azure Auth → Azure Authentication = Managed Identity → Save & test. To verify: Save & test returns success. If a brand-new data source hits the identical load error, the migration is definitively cleared as the cause and it's the plugin delivery in 13.1.0.
One important note: creating a new data source is purely a diagnostic step. If the underlying plugin cannot load, recreating the data source will not resolve the issue, but it will help us confirm whether we're dealing with a platform-level plugin problem introduced after the 13.1.0 upgrade.
At this point, the browser Network and Console logs will be the most valuable evidence for determining the next steps.
Documentation References
- Connect Grafana to Azure Monitor managed service for Prometheus — https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/prometheus-grafana?tabs=azure-managed-grafana — covers the Configure Grafana section (Grafana 13 authentication change) and the Azure Managed Grafana data source creation steps**3**
- How to manage data sources in Azure Managed Grafana — https://learn.microsoft.com/en-us/azure/managed-grafana/how-to-data-source-plugins-managed-identity — covers the supported data sources table and the Grafana 13 Azure-auth note
- How to manage Grafana plugins — https://learn.microsoft.com/azure/managed-grafana/how-to-manage-plugins — covers Plugin management in the Azure portal
Kindly let us know if the above helps or you need further assistance on this issue.
-
Venkatanaidu Madamanchi 0 Reputation points Microsoft External Staff Moderator
2026-08-09T09:02:02.97+00:00 Hello @Yashwant Shettigar
Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.
Thank you
-
Venkatanaidu Madamanchi 0 Reputation points Microsoft External Staff Moderator
2026-08-11T05:27:01.79+00:00 Hello @Yashwant Shettigar
I hope you are doing well.
This is a gentle follow-up regarding our previous communications. We have not yet received a response from you, and we would appreciate an update on the status of the issue.
Could you please let us know if the information or recommendations provided have helped resolve your concern? If you are still experiencing the issue or require any further assistance, please reply to this email with an update, and we will be happy to continue supporting you.
If we do not hear back from you, we may proceed with closing the case. However, you can always contact us again if you need additional assistance in the future.
Thank you for your time and cooperation. We look forward to hearing from you.
Regards,
Venkat.M
Sign in to comment
Sign in to answer