GitHub Copilot
Overview
Connect a GitHub organization or a GitHub enterprise and get Copilot seat, usage, and AI credit cost in the same views as your cloud and other AI spend - per-user usage, chat and completions, agent activity, and daily cost granularity.
Two connection types are supported, by GitHub account level:
- GitHub organization (one org) - Copilot Business. Uses a fine-grained token whose resource owner is the organization.
- GitHub enterprise (all orgs under one enterprise) - Enterprise-wide. Uses a classic token with billing scopes.
Each connection covers one GitHub organization or one enterprise. Add another connection for each additional one.
What gets tracked
Umbrella reads Copilot usage, seat, team, and billing data. The connection does not access repository contents, issues, pull requests, or organization settings.
| Signal | GitHub organization | GitHub enterprise |
|---|---|---|
| Copilot seats and usage per user | Yes | Yes |
| Chat, completions, and agent usage | Yes | Yes |
| AI credit cost | Yes | Yes |
| Daily usage granularity | Yes | Yes |
| Coverage | One organization | Every organization in the enterprise |
Which Copilot plan is supported
Individual plans (Pro, Pro+, Free) are not supported - they don't expose the organization or enterprise billing APIs Umbrella needs.
| Your Copilot plan | GitHub organization | GitHub enterprise |
|---|---|---|
| Copilot Enterprise | - | Yes |
| Copilot Business | Yes | - |
| Copilot Pro+ | - | - |
| Copilot Pro | - | - |
| Copilot Free | - | - |
Before you start
- For GitHub organization: GitHub organization owner access. The
Copilot usage metricsorganization policy must be enabled. - For GitHub enterprise: GitHub enterprise owner or billing manager access. The
Copilot usage metricspolicy must be enabled everywhere in the enterprise. A dedicated service account is recommended for the token.
Step 1: Account details
Open Cloud Connections → Add connection → GitHub Copilot to launch the wizard.
| Field | What it is |
|---|---|
| Onboard this account to (MSP Only) | Choose A customer (then pick the customer name) or My organization. |
| Display account name | Label this connection carries in Umbrella. This label identifies the connection throughout Umbrella AI. |
| GitHub connection type | Choose GitHub organization or GitHub enterprise. |
The remaining steps depend on the connection type you chose. Follow the matching section below.
GitHub organization setup
Open github.com/settings/personal-access-tokens in another tab, then follow the four token-creation steps.
Read-only accessUmbrella Cost only reads Copilot usage, seat, team, and billing data with this token.
Must be a fine-grained tokenClassic tokens are rejected for GitHub organization connections. They cannot read the billing data. Use Generate new token (fine-grained), not Generate new token (classic).
Create the fine-grained token
- Sign in as an organization owner. Open github.com as an organization owner.
- Create a fine-grained token. Choose Generate new token (fine-grained). Set the resource owner to the organization. Name it (e.g.
Umbrella Cost). - Grant three organization permissions, all Read. Under Organization permissions, set the following to Read:
- Administration
- GitHub Copilot Business
- Organization Copilot metrics
- Enable usage metrics and copy the token. In your organization settings, confirm that the Copilot usage metrics policy is enabled - without it, GitHub refuses the usage reports. Generate the token; it's shown only once, so copy it before leaving the page.
Fill in the connection fields
| Field | Value | Where to find it |
|---|---|---|
| Organization login | The slug segment of your org URL | The <login> part of github.com/orgs/<login>. Lowercase, case-sensitive. |
| Fine-grained token | The github_pat_... value from the step above | Encrypted at rest by Umbrella. |
Click Create connection.
GitHub enterprise setup
Open github.com/settings/tokens in another tab, then follow the token-creation steps.
Must be a classic token for enterpriseEnterprise connections require a classic personal access token with billing scopes. Fine-grained tokens cannot carry the enterprise billing scopes Umbrella needs.
Create the classic token
- Sign in as an enterprise owner or billing manager. A dedicated service account is recommended so token rotation isn't tied to a person.
- Generate a classic token. Choose Generate new token (classic), name it (e.g.
Umbrella Cost - Copilot Enterprise), and set an expiration. - Select the required scopes:
manage_billing:enterprise- read enterprise billing data.manage_billing:copilot- read Copilot billing data.
- Enable usage metrics everywhere. In your enterprise settings, confirm that the Copilot usage metrics policy is set to Enabled everywhere. Without it, GitHub refuses the usage reports.
- Copy the token. It starts with
ghp_and is shown only once.
Fill in the connection fields
| Field | Value | Where to find it |
|---|---|---|
| Enterprise slug | The slug of your enterprise | The slug segment of github.com/enterprises/<slug>. Lowercase. For GitHub Enterprise on GHE.com, use your subdomain. |
| Classic token | The ghp_... value from the step above | Encrypted at rest by Umbrella. |
Click Create connection.
After you connect
Umbrella pulls the last 30 days of Copilot data on first ingest, then refreshes daily within 24 hours of GitHub's own metering. The connection first appears in Pending Data state and flips to Healthy once the first batch lands.
Copilot seat cost comes from GitHub billingUmbrella does not ask for a seat contract. Billed seat cost is read from GitHub's billing data directly, so amortized and net-amortized views reflect what GitHub actually invoiced.
From here you can:
- Explore Copilot spend in the Cost & Usage Explorer, broken down by user, team, or model.
- Build a dimension to organize spend by engineering team or product group.
- Enable anomaly alerts on AI credit cost against baseline.
- Track adoption through seat utilization, chat usage, and agent activity.
Token rotation
Fine-grained tokens (organization) expire on the date you set at creation. Classic tokens (enterprise) also carry an expiration. To avoid data gaps:
- Create a replacement token in GitHub with the same scopes and resource owner.
- Update the token in Umbrella under Cloud Connections → [your connection] → Edit.
- Revoke the old token in GitHub.
Set a calendar reminder a few days before expiry so there's time to rotate cleanly.
Troubleshooting
- "Classic tokens are rejected for organizations." The organization connection requires a fine-grained token. Regenerate using Generate new token (fine-grained) with the organization as the resource owner.
- "GitHub refuses the usage reports." The Copilot usage metrics policy is off. Enable it in organization settings (or Enabled everywhere in enterprise settings) and retry.
- Wrong resource owner on the fine-grained token. For organization connections, the token's resource owner must be the organization itself - not a personal account. If you created the token with your personal account as the resource owner, delete it and regenerate.
- Missing permission on the fine-grained token. All three organization permissions must be set to Read: Administration, GitHub Copilot Business, and Organization Copilot metrics. GitHub silently returns empty results for any missing scope.
- Wrong slug. Organization logins and enterprise slugs are case-sensitive. Copy them from the GitHub URL rather than typing them.
- Enterprise token missing a scope. The classic token needs both
manage_billing:enterpriseANDmanage_billing:copilot. Easy to miss - both scopes are grouped under collapsed sections on GitHub's token screen.
Updated 25 days ago
