GitHub reopens Copilot Business signups with upfront billing

GitHub is gradually reopening Copilot Business and Copilot Enterprise signups for organizations paying by credit card or PayPal. The access change comes with a billing shift: newly assigned seats must be paid for before users receive Copilot access, and existing customers on those payment methods move to upfront seat charges from the start of the next billing cycle, beginning October 1, 2026.

What GitHub is reopening

The reopening applies to new Copilot Business and Enterprise customers paying by credit card or PayPal. GitHub says the rollout will happen over the next couple of weeks, so an organization may not see the signup option immediately. Customers using another commercial arrangement are outside the scope of this notice.

GitHub paused some self-serve business signups earlier this year while it worked on service availability, account vetting, and billing reliability. The new changelog entry describes a staged return rather than a claim that every account is enabled at once.

The seat and usage changes

For card and PayPal customers, GitHub now says:

• New seat assignments require payment for each seat before the assigned user can use Copilot.
• At the beginning of the next billing cycle, assigned Business and Enterprise seats incur an upfront charge. Existing customers begin seeing this change from October 1, 2026, subject to their billing-cycle start.
• If a team exceeds its included usage, additional payment may be required to continue using Copilot.
• Included usage may be prorated during a partial month to match seat-cost proration.

An independent implementation analysis reaches the same operational reading and separates this change from Microsoft 365 Copilot billing. That distinction matters for administrators comparing budgets across GitHub and Microsoft products.

What administrators should check

Before assigning seats, confirm which payment method and commercial plan the organization uses. Treat October 1 as the earliest stated start date for affected existing customers, not as a universal invoice date: GitHub ties the charge to the next billing-cycle start.

Administrators should also review how included usage, overage authorization, and seat proration appear in their billing settings. A team that previously relied on delayed or manual cleanup may need a purchase-control review before enabling more seats.

Sources and scope

GitHub’s changelog is the primary source for the staged reopening and billing terms. The independent analysis provides corroborating context, including the distinction between GitHub Copilot Business/Enterprise and Microsoft 365 Copilot. Neither source indicates a general price change to the plan itself; the confirmed change concerns signup availability, upfront seat payment, proration, and possible overage charges.