If your organisation pays for Copilot Business or Enterprise, your September invoice can come in larger than August's without anyone on your team changing a single setting. Here's exactly what changes and what to check before it happens.
What changes on 1 September
GitHub moved Copilot from premium request units to usage-based AI Credits on 1 June 2026, and gave organisations elevated included credits for the first three months as a launch promotion. That promotion ends 31 August. From GitHub's own billing announcement:
| Plan | Price/seat | June–Aug included | From 1 Sept | Change |
|---|---|---|---|---|
| Business | $19/mo | $30 in credits | $19 in credits | −37% |
| Enterprise | $39/mo | $70 in credits | $39 in credits | −44% |
| Pro | $10/mo | $10 | $10 | — |
| Pro+ | $39/mo | $39 | $39 | — |
The subscription price doesn't move. What moves is how much usage is included before a seat starts drawing on whatever spend policy your admin configured. Individual Pro and Pro+ plans were never part of this promotion, so nothing changes for them.
The part that stops people panicking
Code completions are not billed in credits. Inline suggestions and Next Edit Suggestions stay unlimited on every paid plan. Credits meter chat, agent mode, and premium model usage — the token-consuming interactions, priced against each model's published rate.
So if your team mostly uses Copilot as autocomplete, this change may cost you nothing. If your team leans on agent mode and premium models, it's the difference between a flat monthly number and a variable one starting in September.
That distinction is the whole question, and only your own usage data answers it — not this post.
What to actually do before 1 September
1. Read your August usage. In your organisation's Copilot billing view, find credits consumed per seat during August. That figure was measured against a $30 (Business) or $70 (Enterprise) allowance. Compare it to $19 or $39 — the number it'll be measured against from September.
If a seat burned $24 of credits in August, it was comfortably inside the promotional allowance and will be over the standard one in September.
2. Check your spend policy. GitHub's language is that organisations "can choose whether to allow additional usage at published rates or cap spend." That admin setting is what actually happens at the ceiling: either an overage bill, or agent features stopping for developers mid-sprint.
Neither option is wrong. Both are bad to discover by accident three days into September. Pick one deliberately and tell your team which one you picked.
3. Only then ask whether the plan still fits. If a meaningful share of seats will exceed the standard allowance every month, the honest comparison is your all-in per-seat cost against the alternatives — not the sticker price on either side.
One source correction
Several third-party write-ups of this change describe overage as opt-out — implying it happens automatically unless an admin actively prevents it. GitHub's own wording is that organisations choose whether to allow additional usage or cap spend, which reads as a choice, not a default.
We couldn't confirm the opt-out framing on GitHub's own pages, so we're not repeating it here. Check your own admin settings rather than trusting anyone's description of the default — including ours.
How the alternatives price
At 50 seats, Copilot Business is $11,400/year before any overage. Cursor Teams at $40/seat is $24,000/year for the same headcount. That gap is wide enough that Copilot stays the cheaper option through a substantial amount of overage — worth calculating rather than assuming in either direction.
Claude Code at $20/month is the other shape worth pricing separately: it runs alongside any editor rather than replacing it, and is strongest at exactly the whole-task agent work that burns Copilot credits fastest. For a team where a few developers do most of the agent-heavy work, pairing a cheap seat for everyone with a stronger standalone tool for those few can beat upgrading the whole org to a pricier tier.
FAQ
What happens to Copilot pricing on 1 September 2026?
The subscription price doesn't change. The promotional AI Credit allowance ends: Business drops from $30 to $19 of included credits per seat per month, Enterprise from $70 to $39. Individual Pro and Pro+ are unaffected.
Will my Copilot bill go up in September?
Only if your team consumes more credits than the standard allowance. If your August usage per seat exceeded $19 (Business) or $39 (Enterprise), the excess now falls outside the included allowance.
Are code completions billed as AI Credits?
No. Completions and Next Edit Suggestions stay unlimited on all paid plans. Credits meter chat, agents, and premium model usage.
What happens when we run out of credits?
Depends on your organisation's spend policy — GitHub says orgs choose between allowing additional usage at published rates or capping spend. Check that admin setting before 1 September.
Full breakdown and the alternatives comparison: https://devtoolsreview.com/pricing/copilot-ai-credits-september-2026/
Verified against GitHub's own billing announcement and plans page, August 2026. We earn nothing from any link in this post and aren't enrolled in an affiliate programme for any tool mentioned.
