Beyond the News
Sign in
Artificial IntelligenceWeb DevelopmentSaaSPricing & BillingAI CodingSaaS OperationsDeveloper Tools Active dossier

GitHub Copilot is moving enterprise seats to upfront billing and longer chat retention

GitHub is changing how card and PayPal customers pay for Copilot Business and Enterprise seats while also collapsing several Copilot surfaces into one default-enabled policy with much longer github.com chat retention.

Reviewed and published by Lars Jansen Updated 5 min read
Comment
First published

Key details

  1. GitHub announced the changes on August 28, 2026.
  2. New Copilot Business and Enterprise credit-card/PayPal signups begin reopening September 1, 2026.
  3. New seat assignments for affected new customers require payment before access.
  4. Existing card/PayPal Business and Enterprise customers begin upfront charging for assigned seats from October 1, 2026.
  5. Revoking a seat does not create a prorated refund; mid-cycle seat additions remain prorated.
  6. No earlier than September 28, cloud agent, github.com Chat and Mobile Chat move to one default-enabled policy.
  7. github.com chat data will be retained for the life of the account instead of 28 days after the migration.
  8. The Default Copilot code-review effort changes from Lite to Balanced on September 28.

What builders should take away

  1. Audit automated seat assignment and offboarding flows before October so they do not assume access can be granted before payment or that removals create same-cycle refunds.
  2. Review the unified Copilot policy before September 28; leaving it alone is an affirmative choice because the new experience is enabled by default.
  3. Update internal AI-data guidance if teams previously relied on github.com Chat’s 28-day retention window.
  4. If Lite code review is intentional, set it explicitly at the organization or repository level before September 28 instead of leaving effort on Default.
  5. Recheck user-level budgets and AI-credit controls because billing remains usage-based beyond included allowances even though seat prices themselves are unchanged.

What changed

GitHub announced three linked Copilot administration changes on August 28. New credit-card and PayPal Copilot Business and Enterprise customers begin returning September 1, with new seat assignments requiring payment before access. Existing card and PayPal customers move to upfront charging for all assigned seats at the start of each billing cycle from October 1. No earlier than September 28, GitHub will also merge Copilot cloud agent, Chat on github.com and Mobile Chat into one default-enabled policy; github.com chat data will then be retained for the life of the account instead of 28 days. On the same date, the Default code-review effort setting moves from Lite to Balanced.

Why it matters

The billing change affects cash flow and seat-management behavior without changing headline seat prices: removing a seat does not produce a prorated refund, while mid-cycle additions remain prorated. The policy migration is more consequential for governance because administrators who do nothing will accept a broader unified Copilot surface and much longer chat retention. Teams therefore need to review billing automation, offboarding timing, data-retention expectations and code-review defaults before the September and October cutovers.

Seat assignment becomes a payment event

Starting September 1, new Copilot Business and Enterprise seat assignments for newly reenabled credit-card and PayPal customers require payment before the user receives access. Existing card and PayPal customers move to upfront seat charging at the start of their billing cycle from October 1. GitHub says plan prices are not changing, mid-cycle additions remain prorated, and revoked seats do not receive a prorated refund.

The unified policy changes the default governance posture

No earlier than September 28, Copilot cloud agent, Chat on github.com and Chat in GitHub Mobile are scheduled to become one unified Copilot experience controlled by one policy. The unified experience will be enabled by default. Organizations that opt out lose Copilot access on github.com and Mobile after launch, so administrators need to make an explicit governance decision rather than assume existing per-surface choices will persist.

Chat retention moves from 28 days to account lifetime

As github.com Chat moves onto the agent-sessions experience, GitHub says chat data will be kept for the life of the account instead of 28 days. That is a material change for organizations whose internal policies or user expectations were built around the shorter retention period. Teams should review what developers place into Copilot conversations and whether the new retention model fits their data-handling requirements.

Code review becomes more thorough by default

GitHub is also changing the Default Copilot code-review effort from Lite to Balanced on September 28. Organizations and repositories that explicitly select Lite will stay on Lite, but any setting left at Default will inherit Balanced. That can change review depth and potentially AI-credit or Actions consumption, so teams should test the operational effect rather than treat the label as cosmetic.

What to watch next

  • Whether GitHub publishes additional migration guidance for invoiced customers or payment methods outside credit card and PayPal.
  • Whether longer chat retention gains enterprise-specific deletion or retention controls.
  • Whether the Balanced review default materially changes AI-credit or Actions consumption for typical repositories.
  • The exact launch date of the unified Copilot experience, which GitHub currently describes as no earlier than September 28.

Still unclear

  • GitHub has not said the unified experience will launch exactly on September 28; that is the earliest stated date.
  • The August 28 announcement describes credit-card and PayPal billing changes specifically, so organizations on other payment arrangements should verify their own terms.
  • GitHub does not quantify the typical usage or cost change from moving code-review Default from Lite to Balanced.

Sources

Direct reading behind this dossier.

2 sources

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment
Continue reading
Artificial Intelligence

GitHub Copilot code review can now approve pull requests

Copilot code review now moves from advisory assessment toward a governed merge gate. The public preview remains off by default, and GitHub’s current docs let administrators separate AI approval itself from whether that approval counts toward required-review policy.