Skip to main content

​
Overview

The GitHub Copilot integration connects your Copilot Business or Copilot Enterprise subscription to G360. G360 then collects Copilot seats, daily usage, pull request activity, and billing from GitHub and shows them on the GitHub Copilot Metrics dashboard. Setup takes about 10 minutes and has six steps:
  1. Find your account type
  2. Find your enterprise slug (Enterprise only)
  3. Turn on the Copilot Metrics API
  4. Create a GitHub token
  5. Add the connection in G360
  6. Check that data arrives

​
Before you start

You need:
  • An active GitHub Copilot Business or GitHub Copilot Enterprise subscription.
  • A GitHub account that is an organization owner, enterprise owner, or billing manager. If you are not, ask one of them to do steps 3 and 4 for you, or to give you the permission.
  • Access to G360 as an administrator. Only administrators see Integrations.
Keep a text editor open. You will copy one or two values from GitHub (your enterprise slug, if you have one, and your token) and paste them into G360 in step 5.

​
Step 1: Find your account type

G360 reads Copilot differently for an organization and for an enterprise, so you must pick the right Account Type.
1

Sign in to GitHub

Sign in to github.com.
2

Open your profile menu

Click your profile photo in the upper-right corner.
3

Identify your account type

  • If you see Your enterprises and your company’s Copilot seats are managed there, your account type is Enterprise.
  • Otherwise, your account type is Business. Your Copilot seats belong to one organization under Your organizations.
Write down: Business or Enterprise.
If you pick the wrong account type in step 5, saving the connection fails even with a valid token. The account type cannot be changed later; you would have to delete the connection and add it again. If you are not sure, ask your GitHub organization owner or IT administrator.

​
Step 2: Find your enterprise slug (Enterprise only)

Skip this step if your account type is Business. The enterprise slug is the short name of your GitHub Enterprise account. It is part of the enterprise’s web address.
1

Open your enterprises

On GitHub, click your profile photo → Your enterprises.
2

Open your company's enterprise

Click your company’s enterprise.
3

Copy the slug

Look at the address bar. It shows https://github.com/enterprises/<slug>. Copy the part after /enterprises/.
Example: for https://github.com/enterprises/acme-corp, the slug is acme-corp. Write down: your enterprise slug.
If you do not see Your enterprises, you are not a member of the enterprise. Ask your GitHub enterprise administrator for the slug.

​
Step 3: Turn on the Copilot Metrics API

GitHub only shares Copilot usage when an administrator turns this on. You do it once.
1

Open your organization

On GitHub, go to your organization’s page, for example https://github.com/acme.
2

Open settings

Click Settings.
3

Open Copilot policies

In the left panel, click Copilot, then Policies.
4

Enable the API

Find Copilot Metrics API access (Enable access to the Copilot Metrics API for this organization) and set it to Enabled. Click Save if a save button appears.
GitHub only produces usage reports for an organization or enterprise with at least 5 active Copilot users in the last 28 days. Seats and billing are collected either way.

​
Step 4: Create a GitHub token

G360 signs in to GitHub with a Personal Access Token (classic).
1

Open Developer settings

On GitHub, click your profile photo → Settings. In the left panel, scroll down and click Developer settings.
2

Open Tokens (classic)

Click Personal access tokens → Tokens (classic).
3

Start a new token

Click Generate new token → Generate new token (classic). Confirm your password or two-factor code if GitHub asks.
4

Name the token

In Note, type a name, for example G360 Copilot.
5

Set the expiration

In Expiration, pick a period. If you pick a date, set a reminder to replace the token before then.
6

Select the scope

Under Select scopes, tick manage_billing:copilot. Leave everything else unticked.
7

Generate and copy the token

Scroll down and click Generate token. Click the copy icon next to the new token (it starts with ghp_).
Write down: the token.
GitHub shows the token only once. If you leave the page without copying it, delete it and create a new one.
Business only: create the token from an account that manages Copilot in only the organization you want to connect. G360 finds the organization from the token, and refuses a token that manages Copilot in several organizations.
Fine-grained tokens are not recommended: not every Copilot endpoint accepts them.

​
Step 5: Add the connection in G360

1

Open the GitHub Copilot integration

In G360, click Integrations in the top bar, then the AI Coding tab. On the GitHub Copilot card, click Connect (or Manage if a connection already exists). The Copilot Connections page opens.
2

Start a new connection

Click Add Connection. The Add Copilot Connection dialog opens.
3

Fill in the fields

4

Test the connection

Click Test Connection.
  • You should see Connection Test Successful — Token is valid and has Copilot access.
  • If you see an error at the top of the dialog, go to Troubleshooting, fix it, and click Test Connection again.
5

Save the connection

Click Save Connection. G360 checks the token against your organization or enterprise again before it saves.
You should see:
  • Connection Added — Connection added successfully.
  • Project Created — Project “<Connection Name>” was created for this connection and its first sync has started. Daily sync runs at 12:00 AM IST.
  • The connection in the Copilot Connections table, with Status Active.
For an Enterprise account, Test Connection checks the token only; the enterprise slug is checked when you click Save Connection. If the test says the token has no Copilot admin access to any organization but you are an enterprise owner, click Save Connection: the save checks the token against your enterprise.

​
Step 6: Check that data arrives

The first sync starts as soon as you save and collects the last 28 days. It can take a few minutes for a large organization.
1

Open Projects

Click Projects in the top bar.
2

Check the sync status

Find the project named after your connection. Its Sync Status shows In Progress while the first sync runs, then Succeeded.
3

Open the dashboard

In the left navigation panel, expand AI Coding Tools and click GitHub Copilot.
4

Select the project

Pick the project in the Project filter.
You should see seats and usage for the last days.
  • GitHub publishes each day’s usage the next day, so the newest data is always from yesterday.
  • Only members with Copilot telemetry enabled in their IDE appear in usage.
  • GitHub does not share developers’ email addresses. New GitHub logins can be matched to an existing person in Users and Teams → User Mappings.

​
The Copilot Connections page

Use the search box above the table to find a connection by name.

​
Edit a connection

1

Open the connection

In Copilot Connections, click the Edit icon on the connection’s row. The Edit Copilot Connection dialog opens.
2

Change the fields

Change the Connection Name, or paste a new token in API Key. Leave API Key blank to keep the current token (Leave blank to keep the current key unchanged.). Account Type and Enterprise Slug cannot be changed.
3

Save

Click Update Connection.
  • Test Connection in this dialog checks the saved token. A new token is checked when you click Update Connection.
  • Renaming changes nothing else.
  • A new token for the same organization or enterprise clears the connection’s Copilot data from the dashboard; the next sync loads it again. Seat history is kept.
  • A new token must read the same organization or enterprise as the old one. To connect a different one, add a new connection.
  • If a sync of this connection is running, the update is refused: A sync of this connection is in progress. Try again when it finishes.

​
Delete a connection

A connection linked to a project cannot be deleted. Saving a connection links it to its project, so unlink the project first.
1

Delete the connection

In Copilot Connections, click the Delete icon on the connection’s row.
2

Confirm

In Delete Key, click Yes.
You should see Key Deleted — Connection deleted successfully.
  • G360 stops collecting from that organization or enterprise, and its Copilot data is removed from the dashboards.
  • Its sync schedule is removed. Its run history is kept.
  • If the connection is still linked to a project, the delete is refused: Cannot delete connection. It is associated with project ‘<name>’. Unlink the project first.
  • If a sync of this connection is running, the delete is refused. Wait a few minutes and try again.
  • People known to G360 only through this connection are marked inactive. They become active again automatically if any connected source sees them again.

​
How syncing works

  • The first sync starts when you save the connection and collects the last 28 days. After that, G360 syncs every day at 12:00 AM IST.
  • Each sync collects every new day up to yesterday and fills in any day of the last 28 that was missed, so a failed or skipped sync heals itself.
  • If GitHub rate-limits G360 briefly, the sync waits and continues. If the limit lasts longer, the sync stops and the next sync collects the missed days.
  • If GitHub is down, or the token expired or was revoked, the sync stops and shows the reason. Replace the token if needed; the next sync collects the missed days.

​
Troubleshooting

Check each of these, then click Test Connection again:
  1. The token was copied completely (use the eye icon), has no spaces before or after it, and has not expired.
  2. The token has the manage_billing:copilot scope (or read:org / read:enterprise).
  3. The GitHub account that created the token is an organization owner, enterprise owner, or billing manager.
  4. Business only: the account manages Copilot in exactly one organization. Multiple orgs found with Copilot access means it manages several; use a token from an account that manages only the one you want.
  5. Enterprise only: see the note in step 5.
  1. Account Type matches step 1.
  2. Enterprise only: the Enterprise Slug matches the address github.com/enterprises/<slug> exactly.
  3. Click Test Connection to see the reason, and work through the checks above.
  • Key with name … already exists: another connection uses this Connection Name. Choose a different name.
  • A project named … already exists: a G360 project already has this name. Choose a different Connection Name.
  • A connection with this token already exists: another connection uses this token.
  • A connection for … already exists: another connection already reads this organization or enterprise. Each organization or enterprise can have only one connection; edit the existing one instead.
Wait a few minutes for the sync to finish, then try again.
Unlink the project from the connection first, then delete the connection.
  1. Wait for the first sync to finish (Sync Status in Projects shows Succeeded).
  2. Remember the newest data is from yesterday.
  3. Check the project selected in the Project filter is the one created for the connection, or pick All.
  4. Check the Copilot Metrics API is still enabled (step 3). Another administrator can turn it off without G360 being told.
  5. Check the organization or enterprise has at least 5 active Copilot users, and that members have Copilot telemetry enabled in their IDE.
  6. Check the token has not expired.

​
Best practices

  • Create the token from a dedicated administrator account rather than a personal one.
  • Give the token only the manage_billing:copilot scope (or the read-only alternative).
  • Replace the token before it expires.
  • Name connections after the organization or enterprise they read.
  • Check now and then that the Copilot Metrics API is still enabled.