---
title: Copilot licence and budgets on GitHub Enterprise
date: 2026-11-09
tags: github, copilot, enterprise, billing
summary: Notes on managed users, the Copilot access in the Enterprise licence and the budgets I tried for AI credits. Budget has room for improvement.
---

Here are some topics I came across as part of the migration and managing GitHub in general. The migration itself is in [the planning memo](/p/2026-11-09-planning-the-migration-to-ghe-com/).

## Managed users

The current setup has it, that each person sign in with their personal account and we invite them into the organization and adding GitHub Enterprise and Copilot licence. That account is private so it is also used for private things.

This is a problem with Copilot. If the company licence is on a personal account, nothing stops the person from using it for a private project. All the usage is billed back to the company.

Another way to set it up is using managed user account. They are created and controlled by the company through the identity provider. From the [docs](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts):

- Sign-in only through the identity provider.
- No contact with repositories outside the enterprise: no push, issues, pull requests, stars or forks.
- Repositories under the user's own account must be private, if the enterprise allows them at all.
- No signing up for Copilot Pro or Copilot Free. Copilot only comes from the enterprise.

So work and private are separated accounts. The downside - a company-managed account can't contribute to open source or any public repository. Also the repo is private or internal and this begs the question: what do we do with customer who wants access to it? GitHub itself says managed users are [not the best solution for every customer](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users).

## The Copilot licence

As I was planning the migration with my colleague, I saw a post on GitHub blog about the Copilot licence: [GitHub Enterprise now includes access to GitHub Copilot](https://github.blog/changelog/2026-10-28-github-enterprise-now-includes-access-to-github-copilot/).

What it means:

- With a GitHub Enterprise Cloud licence there is **no separate Copilot licence** and no Copilot seat charge.
- Same features and models as Copilot Enterprise, but **no AI credits included**. Every request is billed against the enterprise budget.
- If the budget is at the limit, the seat stays. Code completion and next edit suggestions still work. Chat, code review and the cloud agent stop working.
- The older plans: Copilot Business ($19 per user per month) includes $19 of AI credits per seat, Copilot Enterprise ($39) includes $39. The credits are pooled across the company ([announcement](https://github.blog/news-insights/product-news/github-copilot-is-moving-to-usage-based-billing/)).

If you want this, ask your GitHub salesperson. Currently, there are no self-service way and as we want to migrate it to GHE.com, it is the perfect time to do it.
My main gain is, not having to manage the Copilot licence and GitHub Enterprise licence separately. The Copilot is now part of the Enterprise licence.

## Budgets

I struggle with the right way to manage budget for users. The [Copilot budget docs](https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/billing/budgets-for-usage-based-billing) list these:

| Budget | What it caps |
|---|---|
| Universal user-level | Each user's total AI credit use, including included credits |
| Cost center user-level | The same per member, with an amount set per cost center. Overrides universal |
| Individual user-level | One user. Overrides the other two. Optional end date |
| Cost center budget | The metered charges of the whole cost center, after the included pool is used |
| Included usage control (cost center) | How much of the included pool a cost center may use |
| Organization budget | Metered charges for seats billed to that organization |
| Enterprise budget | Metered charges of the whole enterprise, not the licence fees |

The first three are per person and only exist for Copilot AI credits. The rest cap a group.

What I tried:

- **One universal budget per user.** Works fine, simplest, and the one I still have in use - so I don't have to set a limit for each person.
- **Cost centers with teams and different budgets**, for example 100 USD per person in one group and 200 USD in another. Switching a person to another group was a pain. I had to remove them from one team and add them to the other, each step sends a notification email. If it happens inside the billing month, the budget of that person starts at 0 in the new group. So people can only be moved cleanly at the end or start of a month. After two months of trying I deleted them again and came back to:
- **Individual override with or without an end date.** So if a person needs more budget, I increase it. If they only need temporarily more budget there is also an option to set valid until end of month.

Still on the hunt for a better way to manage budgets.
