GitHub Copilot Business and Enterprise move to upfront seat billing: Reveneau

GitHub Copilot Business and Enterprise move to upfront seat billing

GitHub told Copilot Business and Enterprise administrators on 28 August that new seat assignments will require upfront payment from 1 September, that a unified Copilot experience on the web and mobile will extend chat retention from 28 days to the life of the account no earlier than 28 September, and that Copilot code review's default effort level moves from Lite to Balanced on the same date.

Why it mattersThe chat retention change is the one to read carefully, because it turns transcripts that used to expire in a month into records that exist for as long as the account does.

GitHub published a policy and billing update for Copilot on 28 August 2026, addressed at Copilot Business and Copilot Enterprise administrators. Three changes are announced together and each has a different date and a different consequence.

Upfront seat billing

The billing change reads that "All new Copilot Business or Copilot Enterprise seat assignments will require payment for each seat before users gain Copilot access." For new customers this begins on 1 September 2026, and for existing customers it starts at the next billing cycle from 1 October 2026. Pricing is not changed, so the effect is a cash-flow one for teams that added a seat this month and paid at the end of it: from October they pay before the user opens Copilot rather than after. The changelog also notes that "if you exceed your included usage, additional payment may be required," which is the existing overage rule rather than a new one.

Unified chat experience and account-lifetime retention

No earlier than 28 September, chat on github.com, GitHub Mobile, and the cloud coding agent will be treated as one service under one policy. The line to note is that "chat data will be retained for the life of the account instead of 28 days." That is a genuine widening. Anything a developer types into Copilot chat on the web or the mobile app, or asks the cloud agent to do, now sits in GitHub's systems until the account is closed rather than expiring in a month.

The unified experience is on by default. Opting out is possible, but the trade is that opting out removes access to Copilot on the web and mobile entirely. There is no opt-out that keeps the surface and shortens the retention.

Code review default moves from Lite to Balanced

Copilot code review's default effort level changes from Lite to Balanced on 28 September, across all repositories and organizations. GitHub does not describe in the post what Balanced does that Lite does not, so the practical answer to "what will my reviewers see in the comment thread from that day" is not answered in the post itself. Teams that want to keep the current behaviour can explicitly set Lite before the deadline. This is worth doing consciously rather than by default, since a change in what Copilot writes in the review will change how much a human reviewer trusts the tool.

The retention window is the one that needs a decision

Two of these are administrative and one is a data question. The billing change matters mostly for finance and procurement. The code review default matters for whoever owns your review workflow and can be handled with a single organization-level setting. The retention change is the one that deserves an internal note, because "chat data" is a broad term that on Copilot includes questions your developers asked about code they cannot paste anywhere else. Decide before 28 September whether that retention window is acceptable for the material your team pastes into Copilot chat, and if it is not, decide whether the answer is to opt out of the unified experience or to change what people paste.

Source

Upcoming changes to GitHub Copilot policies and billing, GitHub Changelog, 28 August 2026.

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.