Add azure devops plugin for grafana dashboard

Navpreet Kaur 40 Reputation points Microsoft Employee
2026-07-20T14:01:09.3466667+00:00

Add azure devops plugin for grafana dashboard to create dashboards for azure pipelines

Azure Managed Grafana
Azure Managed Grafana

An Azure service used to deploy Grafana dashboards for analytics and monitoring solutions.


Answer accepted by question author
Suchitra Suregaunkar 16,620 Reputation points Microsoft External Staff Moderator
2026-07-20T17:28:14.3066667+00:00

Hello Navpreet Kaur

To create Grafana dashboards for Azure Pipelines (and other Azure DevOps entities like Projects, Repos, Builds, Releases, Deployments), you need the Azure DevOps data source plugin, which is a Grafana Enterprise plugin. Below are the exact, officially supported steps depending on how you run Grafana.

If you're using Azure Managed Grafana (recommended on Azure):

Azure DevOps is listed as a supported Grafana Enterprise data source in Azure Managed Grafana (Standard tier + Grafana Enterprise add-on).

Steps:

  1. Enable Grafana Enterprise on your Azure Managed Grafana workspace. Follow the official Microsoft Learn guide: Enable Grafana Enterprise — this is a prerequisite because Azure DevOps is not a core (free-tier) data source. Reference: https://learn.microsoft.com/en-us/azure/managed-grafana/how-to-grafana-enterprise
  2. Install the Azure DevOps plugin: In the Azure portal, open your Managed Grafana workspace → Overview → Endpoint to launch the Grafana UI. Then go to Administration → Plugins and data → Plugins, search for Azure DevOps, and install it. (Enterprise plugins become installable once step 1 is complete.)
  3. Add the data source: In Grafana, go to Connections → Data sources → Add new data source, pick Azure DevOps, and configure:
  • URL: https://dev.azure.com/<YourOrganization>
  • PAT: a Personal Access Token from Azure DevOps with read scopes for Project & Team, Code, Build, and Release. Click Save & test.
  1. Import the pre-built pipeline dashboards: Open the newly added data source → Dashboards tab → click Import on:
  • Project overview – summary of projects, repositories, builds, and pipelines
  • Repository overview – repo and PR activity

You can then build your own panels using the query editor to visualize Pipelines – List and Pipelines Runs – List for Azure Pipelines specifically.

Reference: [grafana.com]

If you're running self-hosted / OSS Grafana: The Azure DevOps data source is an Enterprise plugin, so you need either Grafana Cloud Pro/Advanced or an on-prem Grafana Enterprise license (Grafana OSS alone won't work).

Azure DevOps has a built-in Grafana service hook to post annotations to your Grafana dashboards whenever a Release deployment completes.

Great for correlating deploys with metrics.

Below are the Steps:

  1. Go to https://dev.azure.com/{orgName}/{project_name}/_settings/serviceHooks.
  2. Create Subscription → Grafana → Next.
  3. Choose event Release deployment completed and set filters (pipeline name, stage, status).
  4. Enter your Grafana URL and Grafana API token.
  5. Test → Finish.

Reference: https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/grafana?view=azure-devops

Please have a look into below limitations:

  • Template variables do not support multi-select (single selection only).
  • Alerting is not supported on this data source (Metrics and Annotations only). [grafana.com]

If you're already on Azure Managed Grafana, the fastest path is: Enable Grafana Enterprise → install the Azure DevOps plugin → add data source with PAT → import the "Project overview" dashboard. That gets you Azure Pipelines visualizations in minutes.

Hope this helps, please mark it as "Upvote" if the provided information is helpfull.

If you have any other queries, Please feel free to ask us.

Thanks,

Suchitra.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

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.