Skip to main content

​
Overview

The Copilot Connections page allows administrators to integrate GitHub Copilot (Business or Enterprise) with G360. Once configured, G360 can securely connect to your GitHub Copilot subscription and collect usage, adoption, and engagement metrics for analysis and reporting.

​
Accessing Copilot Connections

  1. Log in to G360.
  2. From the left navigation panel, expand Integration.
  3. Select Copilot Connections.
The Copilot Connections page displays all configured Copilot API keys.
Note: You will see a banner at the top of the page that reads “Configuration Required.” This simply means no API key has been added yet. Once you add and save a connection, this banner will no longer be relevant to that connection.

​
Copilot Connections Dashboard

The Copilot Connections dashboard provides a centralized view of all configured Copilot API keys.

​
API Key Name

Displays the user-defined name assigned to the Copilot connection.

​
Provider

Displays the source platform the key is associated with. For GitHub Copilot, this will always show as github_copilot.

​
Status

Indicates whether the connection is currently active and available for metric collection.

​
Created At

Displays the date the connection was created.

​
Last Used

Displays the date and time G360 last used this key to pull metrics. This will show Never until the first successful metric collection has run.

​
Actions

Provides options to edit or delete the connection.

​
Prepare GitHub Copilot Credentials

Before creating a Copilot connection in G360, you must first obtain a GitHub Personal Access Token and confirm your Copilot subscription type from the GitHub website. If your organization manages GitHub centrally, you may need to contact your GitHub organization owner or enterprise administrator to obtain these credentials or to grant you the required permissions.

​
Prerequisites

Before proceeding, ensure that:
  • Your organization has an active GitHub Copilot Business or GitHub Copilot Enterprise subscription.
  • You can sign in to GitHub.
  • You are an organization owner, enterprise owner, or billing manager, or you have been granted the required permission by one.
  • You know whether your Copilot subscription is tied to a GitHub Organization (Copilot Business) or a GitHub Enterprise account (Copilot Enterprise).

​
Determine Your Copilot Account Type

The Account Type field in G360 must match how your Copilot subscription is actually set up in GitHub. This determines which permissions your token needs and which API G360 will query.
  1. Sign in to GitHub.
  2. In the upper-right corner, click your profile photo.
  3. If you see Your organizations and your Copilot seats are managed inside a single GitHub organization, your Account Type is Business.
  4. If your company has a GitHub Enterprise account (visible as Your enterprises in account settings, or accessible at a URL similar to github.com/enterprises/your-enterprise-name) and Copilot seats are managed at the enterprise level across multiple organizations, your Account Type is Enterprise.
Note: If you are unsure which type applies to your company, ask your GitHub organization owner or IT administrator before proceeding, since selecting the wrong Account Type in G360 will cause the connection test to fail even with a valid token.

​
Enable the Copilot Metrics API

Before G360 can pull usage data, an administrator must confirm the Copilot Metrics API is enabled for your organization or enterprise. This is a one-time setting inside GitHub, separate from generating your token. For Copilot Business (Organization level):
  1. Sign in to GitHub.
  2. Navigate to your organization page.
  3. Click Settings.
  4. From the left navigation panel, select:
  1. Select:
  1. Locate the option Enable access to the Copilot Metrics API for this organization.
  2. Toggle this setting to On.
  3. Click Save.
For Copilot Enterprise (Enterprise level):
  1. Sign in to GitHub.
  2. Navigate to your enterprise account page, for example:
  1. Click Settings.
  2. From the left navigation panel, select:
  1. Locate the option to enable Copilot usage metrics for the enterprise and toggle it to On.
  2. Click Save.

​
Generate a Personal Access Token

G360 authenticates with GitHub Copilot using a Personal Access Token (Classic). Fine-grained tokens are not recommended for this connection, since not all Copilot metrics endpoints support them consistently across Business and Enterprise accounts. To generate this credential:
  1. Sign in to GitHub.
  2. In the upper-right corner, click your profile photo.
  3. Select:
  1. From the left navigation panel, select:
  1. From the left navigation panel, select:
  1. Select:
  1. Click Generate new token, then select Generate new token (classic).
  2. You may be asked to confirm your password or complete two-factor authentication.
  3. In the Note field, enter a descriptive name, for example:
  1. Under Expiration, select an expiration period. Choosing No expiration avoids the connection breaking later, but a defined expiration is more secure; if you set an expiration, add a calendar reminder to regenerate the token before it expires.
  2. Under Select scopes, check the following scope:
Note: The manage_billing:copilot scope works for both Copilot Business (organization-level) and Copilot Enterprise (enterprise-level) metrics, so it is the recommended scope regardless of your Account Type. Your GitHub administrator may alternatively provide a token scoped with read:org (for Business) or read:enterprise (for Enterprise) if they prefer not to grant billing-related access.
  1. Scroll to the bottom and click Generate token.
GitHub generates the token and displays it once. Copy this value immediately.
Warning: GitHub displays the Personal Access Token only once, immediately after it is generated. Store it securely before leaving the page. If it is lost, a new token must be generated.

​
Creating a New Copilot Connection

After obtaining the required GitHub credentials:
  1. Return to G360.
  2. Navigate to Integration → Copilot Connections.
  3. Click Add Connection.
The Add Copilot Connection dialog appears.

​
Connection Fields

​
Connection Name

Enter a unique and descriptive name to help you identify this connection in the future. Example:

​
Key name

Paste the Personal Access Token (Classic) generated in GitHub Developer Settings. For security purposes, this value is masked after it is entered. Click the eye icon next to the field to reveal the value and confirm you have pasted it correctly before saving.
Warning: GitHub displays the Personal Access Token only once when it is created. If you no longer have the token, generate a new one in GitHub Developer Settings.

​
Account Type

Select whether your Copilot subscription is managed at the:
  • Business level (tied to a single GitHub organization), or
  • Enterprise level (tied to a GitHub Enterprise account)
This must match what you confirmed earlier in Determine Your Copilot Account Type. Selecting the wrong option will cause the connection test to fail even with a valid token.

​
Testing the Connection

Before saving the configuration:
  1. Verify that all required fields have been completed.
  2. Click:
G360 validates the connection by verifying that:
  • The Personal Access Token is valid and has not expired.
  • The token has the required scope for the selected Account Type.
  • The Copilot Metrics API has been enabled for the organization or enterprise.
  • G360 can successfully retrieve a sample Copilot usage response from GitHub.

​
Expected Result

If the validation is successful:
  • The connection test succeeds.
  • G360 confirms that it can securely communicate with your GitHub Copilot subscription.
  • The connection is ready to be saved.
If the validation fails:
  • Verify that the token was copied correctly and has not expired.
  • Confirm that the token includes the manage_billing:copilot scope (or the alternative scope your administrator provided).
  • Confirm that the Copilot Metrics API has been enabled under your organization’s or enterprise’s Copilot settings.
  • Verify that the Account Type selected in G360 matches how your Copilot subscription is actually configured in GitHub.
  • Confirm that you have organization owner, enterprise owner, or billing manager permissions.

​
Saving the Connection

After the connection has been successfully validated:
  1. Click:
The new Copilot connection is added to the Copilot Connections dashboard, and G360 begins collecting Copilot metrics from the configured GitHub account.

​
Editing an Existing Connection

To modify an existing Copilot connection:
  1. Locate the connection in the Copilot Connections table.
  2. Click the Edit icon under the Actions column.
  3. Update the required fields.
  4. Click Test Connection to validate the updated configuration.
  5. Click Save Connection.
The updated configuration takes effect immediately after the connection is saved.

​
Deleting a Connection

To remove a Copilot connection:
  1. Locate the connection in the Copilot Connections table.
  2. Click the Delete icon under the Actions column.
  3. Confirm the deletion.
Deleting a connection removes the Copilot integration from G360 and stops future metric collection for that GitHub account.

​
Connection Status

The Status column indicates whether a Copilot connection is currently being used for metric collection.

​
Active

The Copilot connection is enabled and G360 actively collects metrics from the configured GitHub account.

​
Inactive

The Copilot connection remains configured but is disabled. No metrics are collected until the connection is enabled again.

​
Best Practices

To ensure secure and reliable Copilot integrations:
  • Use a token generated by a dedicated administrator account rather than a personal daily-use account, where possible.
  • Grant only the manage_billing:copilot scope (or the minimum alternative scope needed) required for metric collection.
  • Store Personal Access Tokens securely and rotate them before their expiration date.
  • Use descriptive connection names that clearly identify the GitHub organization or enterprise.
  • Test every connection before saving it.
  • Regularly confirm the Copilot Metrics API remains enabled in GitHub, since a policy change can silently break an existing connection.

​
Troubleshooting

​
Connection Test Failed

Verify the following:
  • The Personal Access Token was copied correctly.
  • The token has not expired.
  • The token includes the manage_billing:copilot scope (or the read:org / read:enterprise alternative).
  • The Copilot Metrics API is enabled under the organization’s or enterprise’s Copilot settings.
  • The Account Type selected matches how the Copilot subscription is actually configured in GitHub.
  • The GitHub account used to generate the token has organization owner, enterprise owner, or billing manager permissions.

​
Metrics Are Not Appearing

Verify the following:
  • The connection is marked as Active.
  • The configured Personal Access Token has not expired.
  • The Copilot Metrics API is still enabled in GitHub (this can be turned off by another administrator without notice to G360).
  • Members of the organization have Copilot telemetry enabled in their IDE, since usage will not be reflected otherwise.
  • The correct Account Type has been configured.

​
Unable to Save Connection

Verify that:
  • All required fields marked with an asterisk (*) have been completed.
  • The connection successfully passed the Test Connection validation.
  • The provided Personal Access Token is valid.
  • The GitHub organization or enterprise account still exists and the Copilot subscription is still active.