Grafana Cloud Enterprise Open source
Last reviewed: August 20, 2026

Install and upgrade the Azure Monitor Managed Service for Prometheus data source plugin

This document covers how to install, upgrade, and verify the Azure Monitor Managed Service for Prometheus data source plugin across different Grafana deployment environments. After the plugin is installed, refer to Configure the Azure Monitor Managed Service for Prometheus data source to set up a connection.

Before you begin

Verify the following requirements before installing:

RequirementDetails
Grafana versionA supported version of Grafana. For the full supported version list, refer to Requirements.
Network accessGrafana Cloud instances require internet access to download the plugin from the catalog. Self-managed installs need access to the Grafana website or a local plugin ZIP.
Azure accessAn Azure Monitor workspace and Microsoft Entra ID credentials or an Azure identity with permission to query it.

Install the plugin

The Azure Monitor Managed Service for Prometheus plugin is a signed plugin available in the Grafana plugin catalog on all Grafana Cloud plans and self-managed Grafana. Choose the installation method that matches your Grafana deployment.

Grafana Cloud

To install the plugin on Grafana Cloud:

  1. In your Grafana Cloud instance, navigate to Administration > Plugins and data > Plugins.
  2. Search for Azure Monitor Managed Service for Prometheus and click Install.

Plugins are automatically updated on Grafana Cloud, so no further action is required to stay current.

Note

Azure authentication must be enabled for your Grafana Cloud instance before you can query an Azure Monitor workspace. If Save & test returns 401 Unauthorized, or Azure authentication options don’t appear as expected, contact Grafana Support. For more information, refer to Troubleshooting.

Self-managed Grafana (CLI)

Install the plugin with the Grafana CLI:

Bash
grafana cli plugins install grafana-azureprometheus-datasource

Restart Grafana after installation:

Bash
sudo systemctl restart grafana-server

Docker

Set the GF_INSTALL_PLUGINS environment variable:

YAML
environment:
  - GF_INSTALL_PLUGINS=grafana-azureprometheus-datasource

Kubernetes (Helm chart)

Add the plugin to your Helm values:

YAML
plugins:
  - grafana-azureprometheus-datasource

Or use the GF_INSTALL_PLUGINS environment variable in your deployment spec:

YAML
env:
  - name: GF_INSTALL_PLUGINS
    value: "grafana-azureprometheus-datasource"

Kubernetes (init container)

If you don’t control the Helm chart, for example on a shared platform cluster, use an init container to download the plugin before Grafana starts:

YAML
initContainers:
  - name: install-plugins
    image: curlimages/curl:latest
    command:
      - sh
      - -c
      - |
        curl -sL https://grafana.com/api/plugins/grafana-azureprometheus-datasource/versions/latest/download \
          -o /plugins/grafana-azureprometheus-datasource.zip && \
        unzip /plugins/grafana-azureprometheus-datasource.zip -d /plugins/
    volumeMounts:
      - name: plugins
        mountPath: /plugins

Mount the same volume at /var/lib/grafana/plugins in the Grafana container.

Air-gapped (offline) installation

For environments without internet access:

  1. Download the plugin ZIP from the Grafana plugin catalog on a machine with internet access.

  2. Transfer the ZIP to the Grafana server.

  3. Extract the ZIP to the plugins directory:

    Bash
    unzip grafana-azureprometheus-datasource-<VERSION>.linux_amd64.zip -d /var/lib/grafana/plugins/
  4. Confirm the extracted folder is named grafana-azureprometheus-datasource and includes MANIFEST.txt. Official downloads from the Grafana website are signed.

  5. Set ownership:

    Bash
    chown -R grafana:grafana /var/lib/grafana/plugins/grafana-azureprometheus-datasource
  6. Restart Grafana.

If Grafana reports an unsigned plugin error, the copy is incomplete or didn’t come from the Grafana website. Download the official signed ZIP again, extract the full plugin directory, and match the folder name to the plugin ID and your Grafana architecture.

Verify the installation

After installing, confirm the plugin is loaded:

  1. Navigate to Administration > Plugins and data > Plugins.
  2. Search for Azure Monitor Managed Service for Prometheus and verify the plugin appears with a status of Installed.
  3. Navigate to Connections > Add new connection and search for Azure Monitor Managed Service for Prometheus to confirm it’s available as a data source.
  4. If the plugin doesn’t appear, check the Grafana server logs for errors and refer to Troubleshoot installation issues.

Upgrade the plugin

Upgrade steps depend on your Grafana deployment environment.

Grafana Cloud

Plugins are automatically updated on Grafana Cloud. No manual action is required. If you experience issues after an automatic update, contact Grafana Support.

Self-managed Grafana

To upgrade a self-managed installation:

  1. Update the plugin:

    Bash
    grafana cli plugins update grafana-azureprometheus-datasource
  2. Restart Grafana.

  3. Verify each data source connection with Save & test.

To install a specific version:

Bash
grafana cli plugins install grafana-azureprometheus-datasource <VERSION>

For Docker or Kubernetes, append the version to the plugin name:

YAML
environment:
  - GF_INSTALL_PLUGINS=grafana-azureprometheus-datasource <VERSION>

Roll back to a previous version

If an upgrade causes issues on a self-managed instance, pin an earlier plugin version. Replace the version with the last one that worked for you:

Bash
grafana cli plugins install grafana-azureprometheus-datasource 1.0.2

Restart Grafana after the rollback. For the list of released versions, refer to the Grafana plugin catalog.

Note

Rollback isn’t available on Grafana Cloud. If you experience issues after an automatic update, contact Grafana Support.

Uninstall the plugin

To remove the plugin from a self-managed Grafana instance:

Bash
grafana cli plugins remove grafana-azureprometheus-datasource

Restart Grafana after uninstalling. Existing data source configurations are preserved in the Grafana database but become non-functional until the plugin is reinstalled.

For Docker or Kubernetes, remove grafana-azureprometheus-datasource from the GF_INSTALL_PLUGINS variable and redeploy.

Troubleshoot installation issues

The following sections address common installation problems.

“Plugin not found” or install button missing

This problem usually means your Grafana instance can’t reach the plugin catalog.

Solutions:

  • Grafana Cloud: Confirm your instance has finished provisioning and try the search again. If the plugin still doesn’t appear, contact Grafana Support.
  • Self-managed: Verify the Grafana server has outbound access to the Grafana website. For environments without internet access, use the air-gapped installation method.

“Unsigned plugin” error (air-gapped installs)

This error means Grafana can’t verify the plugin signature. Official downloads from the Grafana website include a valid signature.

Solutions:

  1. Download the ZIP again from the official Grafana plugin catalog. Don’t use a copy from an internal mirror unless it is the unmodified official ZIP.
  2. Extract the full plugin directory, including MANIFEST.txt.
  3. Confirm the folder name is grafana-azureprometheus-datasource and that the ZIP matches your Grafana architecture.
  4. Restart Grafana.

Warning

Don’t resolve signature errors by adding this plugin to allow_loading_unsigned_plugins in grafana.ini. Loading the plugin unsigned disables signature verification and is a security risk. Always install the official signed plugin from the Grafana plugin catalog.