GitHub sets new Copilot billing, policy and code review deadlines for businesses

GitHub has outlined three upcoming Copilot administration changes that affect billing, policy control, and code review defaults for Business and Enterprise customers. The update matters less as a feature launch than as an operations deadline: teams that buy Copilot directly by credit card or PayPal, manage Copilot access across web and mobile surfaces, or rely on Copilot code review defaults now have dates to put on the calendar.

What is changing

Starting September 1, 2026, GitHub says it will begin reenabling new Copilot Business and Copilot Enterprise signups for customers paying by credit card or PayPal. New seat assignments will require payment before access begins. Existing customers should expect the related billing changes from October 1, 2026, including upfront charges for assigned seats at the start of the next billing cycle. GitHub says Copilot Business and Enterprise prices are not changing, and that spend controls, usage tracking, and additional AI credit purchases will remain available.

A second change lands no earlier than September 28, 2026. GitHub plans to merge Copilot cloud agent, Copilot Chat on github.com, and Copilot Chat in GitHub Mobile into a unified Copilot experience and policy. After launch, the unified experience will be enabled by default. GitHub also says chat data on github.com will be retained for the life of the account instead of 28 days because the web chat experience will move to the agent sessions model used by Copilot cloud agent.

Why teams should care

The practical risk is configuration drift. A company that treats Copilot as a coding assistant may miss the policy impact of agent sessions, mobile chat, and longer data retention being governed together. Admins should check whether the default unified policy matches internal rules for AI tools, source code handling, and employee devices before the September 28 date.

Copilot code review is also getting a new baseline. GitHub says the Default setting for Copilot code review will use Balanced effort starting September 28 for existing and new repositories and organizations. Teams that prefer Lite can keep it only by explicitly selecting Lite at the repository or organization level before the deadline.

• Review payment method and seat assignment workflows before September 1.
• Confirm unified Copilot policy choices before September 28.
• Set code review effort explicitly if Default is not the right operational choice.

CyberOGZ reads this as a governance update more than a product upgrade. Copilot is becoming a broader workspace service, which makes default settings more consequential for finance, security, and engineering leaders.

Sources

• github.blog

Cover photo by Lukas Blazek on Pexels, used under the Pexels License.