Skip to content

How to connect GitHub Copilot

This guide creates a GitHub Personal Access Token (PAT) so CloudMonitor can read Copilot usage and billing data from your organization or enterprise. Allow about 10 minutes. You need to be an organization or enterprise owner to complete it.

Step 1 — Enable the Copilot Metrics policy

Section titled “Step 1 — Enable the Copilot Metrics policy”

Open your organization or enterprise settings → Copilot → Policies. Set Copilot metrics to Enabled everywhere. Without this policy, GitHub’s metrics endpoints return empty reports.

Enterprise admins can apply the policy across every child organization in one step.

Step 2 — Create a token

Section titled “Step 2 — Create a token”

CloudMonitor accepts either a classic PAT or a fine-grained personal access token. A GitHub App is also supported and will be preferred in v2 — for now, a PAT is the supported path.

For a classic PAT, open Personal access tokens (classic) and grant these scopes:

  • read:org (organization scope) or read:enterprise (enterprise scope)
  • manage_billing:copilot (organization) or manage_billing:enterprise (enterprise)

For a fine-grained PAT, open Fine-grained tokens, select your organization as the resource owner, and grant:

  • Organization permissions → Copilot business: Read-only
  • Organization permissions → Members: Read-only

Set an expiry of 90 days or shorter. CloudMonitor reminds you to rotate the token 14 days before expiry.

Step 3 — Add the token in CloudMonitor

Section titled “Step 3 — Add the token in CloudMonitor”

In the CloudMonitor Admin App, go to Settings → AI providers → GitHub Copilot → Add connector.

Paste:

  • The token from Step 2
  • Your organization slug (e.g. my-org) or enterprise slug (e.g. my-enterprise)
  • The scope: Organization or Enterprise

Click Verify.

Step 4 — Confirm the 14-day backfill

Section titled “Step 4 — Confirm the 14-day backfill”

CloudMonitor pulls the most recent 14 days of usage as proof the connector works. You should see:

  • Active and engaged user counts per day
  • IDE code completion volume broken down by editor, language, and model
  • IDE chat counts
  • Pull request summaries, if your team uses them

If the totals look right, click Save.

Step 5 — Wait for the first full refresh

Section titled “Step 5 — Wait for the first full refresh”

Polling runs daily at 06:00 UTC, after GitHub finalizes the previous day’s report overnight. The first full day of data appears in your reports the morning after Step 4.

What’s next

Section titled “What’s next”