GitHub’s August 28 changelog previewed two waves of Copilot changes, effective September 1 and on or after September 28. With billing and product form shifting at the same time, September is a month where enterprise admins need to act rather than wait.
Wave One (Sept 1): Pay First, Access Second
Credit card and PayPal sign-ups for new Business and Enterprise customers reopened, with stronger account vetting — and new rules. Newly assigned seats require payment before access is granted. From October 1, existing credit card and PayPal customers move to upfront charging for all assigned seats at the start of each billing cycle. Exceeding included usage may require additional payment to keep using Copilot, and included usage may be prorated across the month.
What stays the same is equally worth recording: prices unchanged, no prorated refunds for revoked seats, mid-cycle seat additions still prorated, extra usage still purchasable, and spend controls plus usage tracking remain. Fully canceling Copilot and returning later “may trigger updated account vetting and billing behaviors.” Effective the same day is a round of model deprecations: several Copilot models retired with suggested alternatives published, including changes to GPT-5.3-Codex availability on the Student plan (see the GitHub roadmap). The overall direction is clear: from “subscribe to seats, settle later” toward prepaid seats-plus-usage — in line with the industry-wide shift to usage-based billing.
Wave Two (from Sept 28): One Experience, On by Default
The product change is bigger: Copilot cloud agent, Copilot Chat on github.com, and Copilot Chat in GitHub Mobile will relaunch as a single experience under a single policy, enabled by default. The cloud agent moves to Sandbox for speed; Copilot on github.com migrates to agent sessions — which brings an easily missed data-governance change: chat data retention extends from 28 days to “the life of the account.”
The cost of opting out is stated plainly: organizations that opt out will lose Copilot access on github.com and Mobile after launch. Admins must review and set the policy before September 28 via Copilot settings on github.com (the cloud agent option).
The same day carries an easy-to-miss default change: Code Review’s default effort level moves from Lite to Balanced. Repos or organizations that want to keep Lite must explicitly change the setting from Default to Lite before September 28 for GitHub to honor it; manual reviews can still pick a level from the Reviewers bar afterward.
Three Things for Admins
- Decide the unified-experience policy: set it explicitly in Copilot settings before Sept 28 — this is a setting where inaction means the default decides for you
- Assess the retention change: chat logs going from 28 days to account-lifetime retention is a compliance review item for any organization with a data retention policy
- Check the Code Review default: teams relying on Lite’s low-friction reviews should lock it in before the deadline
Product Observation
The substance of this shift is GitHub converging its answer to “what is Copilot”: no longer several features scattered across editor, web, and mobile, but a single default-on agent built on agent sessions. Paired with pay-first billing, Copilot is formally moving from “assistant plugin” to “infrastructure service” — and both its governance and its billing now follow infrastructure logic.
Sources
- Upcoming changes to GitHub Copilot policies and billing — GitHub Changelog
- Copilot model deprecations — GitHub Roadmap
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.