Copilot Team-Level Usage Metrics API Now Available

GitHub's Copilot usage metrics API now exposes team-level data. Map users to teams, join with per-user reports, and slice adoption metrics by team without building external attribution.

Copilot Team-Level Usage Metrics API Now Available

TL;DR

  • New user-teams API endpoint lets you map Copilot usage to specific teams
  • Join user-teams report with per-user metrics to slice adoption, active users, and code generation by team
  • Teams with fewer than 5 Copilot seats are excluded; multi-team users count toward each team's total

New

  • User-teams report endpoints — Two new REST API endpoints return signed NDJSON downloads mapping each Copilot-licensed user to their team memberships, enabling team-level aggregation without external attribution logic
  • Team-level metric breakdowns — Slice completions, chats, CLI usage, code review, and cloud agent activity by team, language, IDE, feature, or model
  • Step-by-step join guidance — Official docs now include the join recipe, day-level aggregation, and rolling-window patterns for multi-day reporting

Important Notes

  • API-only in this release — no dashboard UI for team metrics yet
  • Teams with fewer than 5 Copilot-seated users are excluded from the report
  • Users in multiple teams have their activity counted in each team's aggregate, so team totals cannot be summed to org/enterprise totals
  • Available to enterprise admins, org owners, billing managers, and custom roles with the View Enterprise Copilot Metrics permission

Endpoints: GET /enterprises/{enterprise}/copilot/metrics/reports/user-teams-1-day and GET /orgs/{org}/copilot/metrics/reports/user-teams-1-day. See the team-level metrics docs for join examples and aggregation patterns.

Source: GitHub Changelog