How to build SharePoint dashboards in Metabase

SharePoint is a Microsoft 365 content and intranet platform for sites, lists, document libraries, files, pages, permissions, and organizational knowledge. Metabase is where you turn that operational activity into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI routethat pulls live data with the Work IQ SharePoint MCP and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs SharePoint into a database so you can build dashboards anyone can read.

How do you connect SharePoint to Metabase?

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

What can you analyze from SharePoint data in Metabase?

• Knowledge-base freshness by site — built from sites and content items and the related lists, list items, libraries data your sync exposes.
• Content ownership and coverage — built from sites and content items and the related lists, list items, libraries data your sync exposes.
• Stale files and pages — built from sites and content items and the related lists, list items, libraries data your sync exposes.
• Site and library activity — built from sites and content items and the related lists, list items, libraries data your sync exposes.
• Permission and sharing risk — built from sites and content items and the related lists, list items, libraries data your sync exposes.

Which SharePoint dashboards should you build in Metabase?

How do you use the Work IQ SharePoint MCP with the Metabase CLI?

Pair the Work IQ SharePoint MCP with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and 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 recently updated, stale, or ownerless sites and content items.
• Export the result as CSV, keeping stable IDs, owners, containers, status or type, 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.
• Change events or snapshots are required for reliable freshness and activity trends.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up SharePoint MCP and the Metabase CLI?

{
  "mcpServers": {
    "sharepoint": {
      "url": "https://agent365.svc.cloud.microsoft/agents/tenants/{tenantId}/servers/mcp_SharePointRemoteServer"
    }
  }
}

# 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 sites-and-content-items export — creates a table AND a model
mb upload csv --file sharepoint-sites-and-content-items.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file sharepoint-sites-and-content-items.csv

Can you generate a SharePoint dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Work IQ SharePoint MCP and the Metabase CLI. It works end to end: if SharePoint tables already exist in Metabase it analyzes those; otherwise it pulls scoped 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 SharePoint content & knowledge analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help team and program leaders understand content freshness, ownership, knowledge coverage, workspace activity, and stale-content risk from SharePoint data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for sharepoint tables and
  models). If durable SharePoint 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 export with the Work IQ SharePoint MCP: sites and content items,
  lists, list items, libraries. 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, dates, owners,
containers, status values, and whether change/activity history exists before creating
duration or trend cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  SharePoint — it reads a database or CLI-uploaded tables.
- Only compute durations when the required start/end or event timestamps exist.
- Exclude archived, deleted, canceled, or test objects from active-population cards.
- Avoid individual performance leaderboards; use owner views for balancing and cleanup.
- 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: SharePoint Content & Knowledge Overview

Sections:
1. Executive summary: Total active content; Freshness rate; Owned-content rate;
   Content updated last 30 days; Stale high-priority content.
2. Freshness: Content by age bucket; stale content by workspace/container and owner.
3. Coverage: Missing owners, descriptions, classifications, or required topic coverage.
4. Activity: Created vs updated by week; active contributors and containers.
5. Governance: External sharing, orphaned content, and permission risk when available.

Filters: Date range, Project/board/database, Status, Owner, Team, Work type.

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 SharePoint data into a database or warehouse?

For dashboards that need history and reliability, land SharePoint data 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 Microsoft Graph SharePoint APIs for control over fields, history, and refresh cadence.
• MCP + CSV — use this for quick exploration and one-off slices.

Sync sites, lists, list items, document libraries, drives, files, pages, users, and permissions with Microsoft Graph; use audit data when you need usage rather than metadata activity.

Notes

• Land raw tables first, then build clean Metabase models on top.
• Keep change events or daily snapshots if you need trends and duration metrics.
• Normalize owner, container, content type, lifecycle, created, updated, and reviewed-date fields.

How should you model SharePoint data in Metabase?

Core tables

Modeling advice

• Build a clean content_items model with common columns across tools.
• Separate current-state fields from change events, activity, or snapshot history.
• Exclude archived, deleted, test, and duplicate objects from active-population metrics.
• Use stable IDs for owner, project, and item joins; display names can change.

Which SharePoint metrics should you track in Metabase?

What SQL powers SharePoint dashboards in Metabase?

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

SELECT
  container_name,
  COUNT(*) AS content_items,
  COUNT(*) FILTER (
    WHERE updated_at >= CURRENT_DATE - INTERVAL '90 days'
  ) AS fresh_items,
  ROUND(
    100.0 * COUNT(*) FILTER (
      WHERE updated_at >= CURRENT_DATE - INTERVAL '90 days'
    ) / NULLIF(COUNT(*), 0),
    2
  ) AS freshness_rate
FROM content_items
WHERE archived_at IS NULL
GROUP BY container_name
ORDER BY freshness_rate ASC;

SELECT
  container_name,
  COUNT(*) AS content_items,
  COUNT(*) FILTER (WHERE owner_id IS NOT NULL) AS owned_items,
  ROUND(
    100.0 * COUNT(*) FILTER (WHERE owner_id IS NOT NULL)
    / NULLIF(COUNT(*), 0),
    2
  ) AS ownership_coverage
FROM content_items
WHERE archived_at IS NULL
GROUP BY container_name
ORDER BY ownership_coverage ASC;

SELECT
  date_trunc('week', occurred_at) AS week,
  container_name,
  COUNT(*) AS activity_events,
  COUNT(DISTINCT actor_id) AS active_contributors
FROM collaboration_events
GROUP BY 1, 2
ORDER BY 1, 2;

What are common mistakes when analyzing SharePoint in Metabase?

Related

Related analytics

Related integrations

FAQ