How to build Azure DevOps dashboards in Metabase

Azure DevOps is Microsoft's engineering platform spanning Boards work tracking, Repos code hosting, and Pipelines CI/CD. Metabase is where you turn that delivery activity into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI route that pulls live data with the Azure DevOps MCP Server and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs Azure DevOps history into a database so you can build dashboards anyone can read.

How do you connect Azure DevOps to Metabase?

Most teams combine both routes: use MCP and CLI uploads for a fast first pass, then move recurring delivery reporting to a warehouse-backed model.

What can you analyze from Azure DevOps data in Metabase?

Once work items and the related pipeline runs, pull requests, repositories data are in a database, the highest-value views are:

• Sprint and work-item flow — cycle time, throughput, and WIP from Boards state history.
• Pipeline success rate and duration — build health across projects from Pipelines run data.
• PR review health — time to first review and time to merge across Repos.
• Lead time from commit to deploy — the DORA throughput view, joining Repos commits to Pipelines deployments.
• Backlog and bug aging — how long open work and defects have been waiting, by area path and team.

Which Azure DevOps dashboards should you build in Metabase?

How do you use the Azure DevOps MCP Server with the Metabase CLI?

Pair the Azure DevOps MCP Server with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and summarized exports; the Metabase CLI's upload command loads CSV data into Metabase and creates a ready-to-query table and model.

Example workflow

• Ask the MCP server for recent work items with state timestamps, plus the latest pipeline runs.
• Export the result as CSV, keeping stable IDs, projects, states, and timestamps.
• Run mb upload csv to load it into Metabase as a table and model, then build questions and dashboards on top.

Be honest about the limits

• MCP lookups are excellent for exploration, not scheduled reporting.
• A CSV upload is a snapshot; refresh it with mb upload replace or move to the pipeline for real history.
• Work-item state transitions and pipeline run history are required for cycle-time and lead-time trends.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up Azure DevOps MCP and the Metabase CLI?

{
  "mcpServers": {
    "azure-devops": {
      "command": "npx",
      "args": ["-y", "@azure-devops/mcp", "your-org"]
    }
  }
}

Microsoft also runs a hosted endpoint at https://mcp.dev.azure.com/{organization} (public preview; requires an Entra-backed organization). Watch for community lookalikes on npm — @azure-devops/mcp from Microsoft is the official package.

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a work-items export — creates a table AND a model
mb upload csv --file azure-devops-work-items.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file azure-devops-work-items.csv

Can you generate a Azure DevOps dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Azure DevOps MCP Server and the Metabase CLI. It works end to end: if Azure DevOps tables already exist in Metabase it analyzes those; otherwise it pulls scoped, summarized data over MCP, loads it with mb upload csv, then builds the dashboard and caveats any metric that needs missing history.

Create a polished Metabase dashboard for Azure DevOps engineering analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help engineering leaders understand work-item flow, pipeline health, code review latency, and the DORA metrics from Azure DevOps data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for azure-devops tables and
  models). If durable Azure DevOps data is already present — synced from a warehouse
  or uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull a scoped, summarized export with the Azure DevOps MCP Server:
  work items, plus pipeline runs, pull requests, repositories.
  Prefer entity tables and rollups over raw logs. Write each result to a CSV,
  then load it with the Metabase CLI — run "mb upload csv --file <export>.csv" so
  each upload creates a table and a ready-to-query model. Use "mb upload replace
  <table-id> --file <export>.csv" to refresh an existing table instead of creating
  duplicates.

Step 2 — Inspect before querying:
Do not assume exact table or column names. Inspect available fields, projects,
branches, states, and timestamps, and whether history exists before creating
duration or trend cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Azure DevOps — it reads a database or CLI-uploaded tables.
- Never try to load raw build logs or event streams into Metabase; use runs,
  entities, state changes, and rollups.
- Only compute durations (cycle time, build duration, time to review) when the
  required timestamps exist.
- Exclude bot activity, draft work, and non-production environments from
  headline numbers, and keep the segmenting column explicit.
- A single CSV is a point-in-time snapshot: only build trend cards if there is a
  usable date column or multiple periods have been uploaded.

Dashboard title: Azure DevOps Engineering Overview

Sections:
1. Executive summary: Work items completed last 30 days; Median cycle time;
   Pipeline success rate; Open PRs; Deploys last 30 days.
2. Flow: Cycle time trend; items completed per sprint; WIP and aging items.
3. Pipelines: Success rate and duration by week; failed runs by pipeline.
4. Code review: PR cycle time; time to first review; review load.
5. DORA: Deployment frequency; lead time; change failure rate; MTTR if synced.

Filters: Date range, Project or Repository, Branch or Environment, Team, Status.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available data.

How do you sync Azure DevOps data into a database or warehouse?

For dashboards that need history and reliability, land Azure DevOps entities and change history in a database first, then connect Metabase to that database.

Connector options

• Managed ETL — use a connector when one covers the objects you need.
• Custom pipeline — use the Azure DevOps Analytics (OData) for control over fields, grain, and refresh cadence.
• MCP + CSV — use this for quick exploration and one-off slices.

Fivetran ships an official Azure DevOps connector (Boards data via the Analytics views). The Analytics OData feeds are the best export story in this cluster — they serve aggregated work-item, pipeline, and test data designed for exactly this kind of reporting.

Notes

• Land raw entity tables first, then build clean Metabase models on top.
• Sync state-change or audit history from day one — duration metrics can't be reconstructed later without it.
• Normalize project, work-item type, state, area or team, and state-transition-timestamp fields.

How should you model Azure DevOps data in Metabase?

Core tables

Modeling advice

• Build a clean work_items model with common columns across tools, so multi-source dashboards don't fork definitions.
• Separate entity tables (projects, repos, flags, members) from run-grain and event-grain tables.
• Exclude bots, drafts, and non-production environments from headline metrics; keep the flag as an explicit column.
• Use stable IDs for project, repo, and person joins; display names change.

Which Azure DevOps metrics should you track in Metabase?

What SQL powers Azure DevOps dashboards in Metabase?

These assume a cleaned analytical model in a warehouse (PostgreSQL dialect). Adjust table and column names to match your pipeline.

SELECT
  date_trunc('week', closed_at) AS week,
  percentile_cont(0.5) WITHIN GROUP (
    ORDER BY EXTRACT(EPOCH FROM (closed_at - activated_at)) / 86400
  ) AS median_cycle_days,
  percentile_cont(0.9) WITHIN GROUP (
    ORDER BY EXTRACT(EPOCH FROM (closed_at - activated_at)) / 86400
  ) AS p90_cycle_days
FROM work_items
WHERE closed_at IS NOT NULL
  AND activated_at IS NOT NULL
GROUP BY 1
ORDER BY 1;

SELECT
  date_trunc('week', started_at) AS week,
  COUNT(*) AS builds,
  ROUND(
    100.0 * COUNT(*) FILTER (WHERE result = 'success')
    / NULLIF(COUNT(*), 0), 1
  ) AS success_rate_pct
FROM pipeline_runs
WHERE branch = 'main'
GROUP BY 1
ORDER BY 1;

SELECT
  date_trunc('week', created_at) AS week,
  percentile_cont(0.5) WITHIN GROUP (
    ORDER BY EXTRACT(EPOCH FROM (first_review_at - created_at)) / 3600
  ) AS median_hours_to_first_review
FROM pull_requests
WHERE first_review_at IS NOT NULL
GROUP BY 1
ORDER BY 1;

What are common mistakes when analyzing Azure DevOps in Metabase?

Related

Related analytics

Related dashboards

Related integrations

FAQ