What happened
GitHub announced three upcoming changes to Copilot policies and billing. Starting September 1, 2026, new Copilot Business and Enterprise customers paying by credit card or PayPal will begin to regain the ability to sign up, with new seat-payment and account-vetting requirements. Existing customers using those payment methods will see billing changes starting October 1.
GitHub’s August 28 changelog describes three separate changes rather than one new Copilot release. The first concerns Copilot Business and Copilot Enterprise billing. GitHub says it will start reenabling sign-ups for new customers paying by credit card or PayPal on September 1, while strengthening account vetting and updating the billing experience for those payment methods. The source does not specify why sign-ups were previously disabled or what the strengthened vetting will require.
Under the new billing process, every newly assigned Business or Enterprise seat must be paid for before the user receives Copilot access. At the beginning of the next billing cycle, all assigned seats will incur an upfront charge. GitHub says this requirement will also apply to existing Business and Enterprise customers using a credit card or PayPal beginning October 1. Seats added during a billing cycle will continue to be prorated from the assignment date through the end of that cycle.
GitHub says Copilot Business and Enterprise list prices are not changing. It also says that removing a seat will not produce a prorated refund, with the removal reflected in the next monthly billing cycle. Additional usage beyond included allowances will remain available for purchase, while spend controls, usage tracking and the option to buy additional AI credits will remain available. The source does not give the included allowances, overage rates or any examples of the resulting bills.
The second change brings Copilot cloud agent, Copilot Chat on github.com and Copilot Chat in GitHub Mobile into a single Copilot experience no earlier than September 28. GitHub says the services will use one policy, the unified experience will be enabled by default, cloud agent will use Sandbox for a faster cloud experience, and Copilot on github.com will move fully to the agent-sessions experience. Chat data will then be retained for the life of the account instead of 28 days, matching the existing cloud-agent experience. The same date is when Copilot code review’s Default setting will move from Lite to Balanced for existing and new repositories and organizations.
Why it matters
The changes affect when organizations pay for Copilot access, how long some chat data is retained, whether users keep access after opting out of a unified experience, and the resources used by automatic code reviews. GitHub says prices themselves are not changing, but organizations may face different payment timing and additional charges when included usage is exceeded.
For organizations, the most immediate practical effect is a change in cash flow and access control. GitHub’s stated requirement that a newly assigned seat be paid before access begins means administrators may need to coordinate seat assignment and payment more closely. The upfront charge at the next billing-cycle start also changes when the cost of assigned seats appears. GitHub says prices are unchanged, but unchanged prices do not necessarily mean unchanged payment timing or monthly totals.
The policy consolidation also makes Copilot’s data-retention rules more consequential. Under the announced change, chat data associated with Copilot on github.com will be kept for the life of the account rather than 28 days. The source does not define what data is included, how deletion requests will work, whether retention varies by plan or region, or how administrators can audit the retained material. Those omissions matter for teams assessing source-code confidentiality, employee records and internal retention policies.
Access could also change for teams that choose not to adopt the unified experience. GitHub says no action is required to keep Copilot available on github.com and GitHub Mobile, but users or teams that opt out will lose access to Copilot on those services after launch. That makes the policy setting an access decision, not merely a preference about interface design. Business and enterprise administrators are specifically told to review the policy before September 28.
The code-review change may alter the amount of work Copilot performs by default. GitHub describes Balanced as a higher default effort level than Lite, but the source does not quantify the difference in review depth, latency, cost or resource consumption. Organizations that want to preserve Lite must explicitly select it at the organization or repository level before September 28. The change therefore affects repositories that remain on the generic Default setting, including automatically requested reviews; manually requested reviews can still use a selected effort level from the pull-request Reviewers bar.
What to watch next
Administrators should review Copilot settings before September 28, when the unified experience and Balanced code-review default are scheduled to begin. Key unknowns include how account vetting will work in practice, how much additional usage may cost, and how the new retention period will affect organizations with stricter data-governance requirements.
The first deadline is September 1, when GitHub says it will begin reenabling Business and Enterprise sign-ups for new credit-card and PayPal customers. The announcement does not say whether access will return everywhere at once, how long account vetting will take, or whether customers using other payment arrangements are affected. Those details will determine whether the change is a broad reopening or a limited restoration for particular account types.
Administrators should check settings and policy documentation before September 28. GitHub says the unified Copilot experience will launch no earlier than that date, so the timing is explicitly not final. Teams that opt out may lose Copilot access on github.com and GitHub Mobile, while teams that leave code-review settings at Default will receive Balanced. The source does not state whether GitHub will provide additional warnings, migration controls or reporting before either change takes effect.
Billing teams should watch the first affected cycles, especially for assigned seats, mid-cycle additions, revoked seats and usage above included allowances. GitHub says revoking a seat will not generate a prorated refund and that extra usage may require further payment, but it does not publish the relevant prices or explain whether charges are calculated identically across Business and Enterprise plans. Actual invoices and updated documentation will be needed to clarify the financial impact.
Data-governance and engineering teams should seek more information about the unified policy, Sandbox and lifetime chat retention. The source establishes that these changes are planned, but it does not provide technical details about Sandbox isolation, the scope of retained chat data, administrative deletion controls, audit logs or regional handling. It also does not report user testing, performance measurements or independent assessments of the new policy. Until those details are available, the public impact can be described only in terms of the announced rules and their likely administrative consequences.