GitHub changed Copilot billing and access rules for org seats

Did GitHub change Copilot billing or access for organization seats

Yes. GitHub changed Copilot organization-seat behavior so billing and access no longer move together in every case. A seat can be billed for the rest of the current cycle after removal, while the user can still keep access until the cycle ends unless the seat is revoked. GitHub documents this for organizations and enterprises in its Copilot billing pages and license-change reference.

The part people get wrong is assuming that removing a seat always stops cost right away and removes access right away. GitHub’s current docs say the seat count change takes effect at the next billing cycle, billing for the removed seat continues until the end of the current cycle, and access can continue until that cycle ends if the seat was simply unassigned. That is different from revoking the seat, which ends access immediately.

For adding seats, the rule is simpler. GitHub says additional Copilot seats are billed for the remainder of the current billing cycle on a prorated basis, and the assigned user gets access immediately after assignment. That means access starts when the seat is granted, not when the next invoice closes.

There is also a second billing change that matters for organizations using Copilot Business or Copilot Enterprise. GitHub now measures Copilot usage with AI Credits under usage-based billing, and the docs say code completions and next edit suggestions are not billed in AI credits and remain unlimited for paid plans. If you only watch seat counts, you can miss usage charges once the shared pool is exhausted.

For organizations on GitHub Enterprise Cloud, the admin flow adds one more step. GitHub says an enterprise owner must enable Copilot for the organization before an organization owner can assign seats. That matters when someone expects the org owner to be able to turn access on alone and the button is unavailable until the enterprise setting is in place.

GitHub also distinguishes between unassigning and revoking. Unassigning a seat during the billing cycle keeps the user active until the end of that cycle, while revoking a seat cuts access immediately. If you remove an organization from an enterprise, GitHub says billing for those seats stops at the end of the cycle, but the users lose access unless they receive a seat through another organization.

The inconvenient part is that a quick cleanup can still show up on the next bill. GitHub’s changelog says customers with Copilot Business or Copilot Enterprise may notice an increase in the next bill because unassigned seats are charged for the full billing cycle in which they were active, even though access is revoked immediately. That is the kind of detail that causes invoice surprises if someone expects seat removal to be a same-day refund.

If you are trying to check this in practice, the place to look is the organization’s Copilot billing and seat management settings, not the general GitHub plan page. GitHub’s docs say seat assignment is managed by organization owners, can be handled in organization settings or via the REST API, and if all assigned seats are removed the organization’s Copilot plan is canceled.

A concrete example makes the rule easy to see. If an admin removes one Copilot seat on the 10th of a monthly cycle, the user can keep access until the end of that cycle if the seat is merely unassigned, and the organization keeps paying through the cycle. If the admin revokes the seat instead, access stops immediately, but the billing change still follows GitHub’s cycle rules.

One more thing gets mixed up often: plan changes for GitHub itself are not the same as Copilot billing changes. GitHub says changing the GitHub plan for a personal account, organization, or enterprise does not affect billing for GitHub features such as Copilot or Marketplace apps. Copilot seat changes are tracked separately from the base GitHub plan.

If your question is simply whether GitHub changed Copilot billing or access for organization seats, the answer is yes. The current rules separate assignment, access, revocation, and billing cycle timing, and that separation is what changed the day-to-day experience for org admins.

For a source of truth on your own org, check the Copilot billing page, the license-changes page, and the seat-assignment page together. Those three pages cover when access starts, when access ends, and when charges stop, which is the full picture most teams need before they remove or reassign seats.

If you want, I can also turn this into a short admin checklist for “add seat,” “remove seat,” and “revoke seat,” using the current GitHub rules.