August 28, 2026: GitHub resets Copilot billing and controls

On August 28, 2026, GitHub's biggest news is not an outage. It is a bundled change to Copilot policy, billing, and product defaults that will matter for admins and buyers more than for casual users.

GitHub says new Copilot Business and Copilot Enterprise signups will reopen on September 1 for credit card and PayPal customers. But there is a catch: new seat assignments will require payment before access. For existing customers, that upfront charge behavior starts on October 1. GitHub is also keeping the posted plan prices unchanged in the docs at $19 per user per month for Copilot Business, $39 per user per month for Copilot Enterprise, and $0.01 per AI credit for additional usage. So this is not a list-price cut or increase. It is a change in when access is paid for, and how usage is metered. [1][2]

In plain language, this is GitHub moving closer to prepaid seats plus separate usage-based billing. That lowers the chance of unpaid usage for GitHub and gives enterprise buyers tighter budget control, but it also adds friction. If an admin assigns a seat and payment has not cleared, access can now depend on that payment flow. That is a finance mechanism, not just a billing footnote. [1][2]

GitHub is also reshaping the Copilot product surface. It says Copilot Chat on github.com, Copilot Chat in GitHub Mobile, and the GitHub Copilot cloud agent will converge into one unified experience no earlier than September 28. The company also says chat data will be retained for the life of the account. For teams that split work across the website, mobile, and agent workflows, that is a meaningful governance and workflow change, even though it is not yet a completed launch. [1]

A second product change lands on the same date: the default review effort level for GitHub Copilot code review changes from Lite to Balanced on September 28. That sounds small, but defaults matter. A default determines the behavior most teams get without extra setup, and review effort can influence how much signal Copilot returns, how noisy the output feels, and how much compute or credit consumption a workflow can generate. [1]

There is also a broader admin layer underneath these Copilot changes. GitHub's global model policy reached general availability on August 26 and is now being gradually enforced through September 1. GitHub says unconfigured GA models inherit the policy, and open-weight or data-retention models are disabled by default. That does not tell us which specific models customers will choose, but it does show the control plane getting stricter just as Copilot's billing and product surfaces are being reorganized. [3]

One correction from yesterday's incident thread: the August 27 Copilot AI Model Providers issue was tied to Kimi K3 through an upstream provider problem, not the earlier mistaken model name. GitHub Status says that incident is resolved. GitHub also says the August 27 billing disruption, which affected billing budget page loads and Copilot CLI session starts or continuation, is resolved as well. The public status page shows no incident today. So the operating story on August 28 is policy change, not live outage. [4][5][6]

For developers, the practical question is what changes first: access, model choice, or review behavior. The answer appears to be access. New signups reopen September 1, existing customers shift to upfront charges on October 1, and the model-policy enforcement window runs through September 1. The unified Copilot experience and Balanced review default do not arrive until September 28. In other words, GitHub is staging the changes in layers rather than flipping everything at once. [1][3]

That staggered rollout matters because it gives admins a short window to audit entitlements, payment methods, and model policy before the new defaults start applying. It also means that a short-lived billing incident from August 27, while resolved, lands just before a more structural change in Copilot collection and access. GitHub still owes a root-cause analysis for that billing disruption. Until then, the open question is whether this was a one-off service issue or a sign that the billing and Copilot session systems need more hardening. [4][5]

So the concise read for today is this: GitHub is tightening the Copilot commercial model, unifying the user experience, and changing a default that could alter code review behavior. The status page is calm now, but the next evidence worth watching is concrete and date-bound. Did the September 1 signup and payment changes land exactly as described, did the global model policy remove or disable the expected models, and on September 28, does the unified Copilot experience actually ship with the stated retention behavior and review default? Those are the falsifiable checkpoints that will tell us whether this bundle is only policy on paper or a real shift in how Copilot is bought and used. [1][3][4][5]