Connecting to GitHub
Connect your GitHub Enterprise Cloud account to CloudZero to bring your GitHub cost and usage data into a unified view of all your cloud and SaaS spend. CloudZero organizes your GitHub costs, along with your other costs, into categories (called Dimensions) that matter most to your business. For example: business unit, team, product, feature, environment, customer, or virtually anything else. Once connected and organized, you can quickly answer questions about your spend that matter to your stakeholders.
This guide covers creating a classic personal access token in GitHub and configuring the connection in CloudZero. CloudZero pulls data from GitHub's Enhanced Billing Platform, including Copilot seat costs, per-user premium-request usage by model, and Actions, Packages, and Git LFS usage. The connection is read-only.
This connection supports GitHub Enterprise Cloud only. Organization-scoped billing accounts are not supported.
What you need
- CloudZero user with data configuration permissions
- A GitHub Enterprise Cloud account with the enterprise owner or billing manager role
- A dedicated service account for generating the personal access token. Tokens generated against a personal account surface CloudZero's automated reports on that user's GitHub activity page.
Step 1: Find your enterprise slug
Your enterprise slug is the identifier in your enterprise URL. For example, in https://github.com/enterprises/acme-corp, the slug is acme-corp.
- Sign in to GitHub as an enterprise owner or billing manager.
- Navigate to your enterprise account and copy the slug from the URL.
Step 2: Create a classic personal access token in GitHub
For full details, see GitHub's personal access token documentation.
GitHub's enterprise billing endpoints require classic tokens (prefixed
ghp_). Fine-grained personal access tokens are not supported.
- In GitHub, navigate to Settings > Developer settings > Personal access tokens > Tokens (classic), or open your token settings directly.
- Select Generate new token (classic). Reauthenticate if prompted.
- Enter a descriptive Note (for example, "CloudZero Integration").
- Set an Expiration that matches your security policy.
- Under Select scopes, enable
manage_billing:enterpriseandmanage_billing:copilot. - Select Generate token.
- Copy the token and store it securely. GitHub does not display the token again after creation.
Step 3: Configure the connection in CloudZero
- In CloudZero, go to Settings > Cloud Connections.
- Select Create Connection + and select the GitHub tile.
- Enter a Connection Name. This label identifies the connection throughout CloudZero.
- Enter the Enterprise Slug from Step 1.
- Enter the Personal Access Token from Step 2.
- Select Create Connection.
What to expect
After you connect, CloudZero begins ingesting your GitHub cost and usage data. Your GitHub costs appear in Explorer and Analytics within 24 hours. Once data is available, you can view costs broken down by organization, repository, Copilot seat holder, model, and any Cost Centers you have configured in GitHub.
From there, your GitHub costs work like any other cost data in CloudZero. For example, you can organize them by team or product using Dimensions, track trends in Dashboards, set Budgets, or ask questions in the AI Hub.
Have questions or feedback? Reach out to your account manager.
Updated 17 days ago
