GitHub had stopped accepting new sign-ups for the team variants of its coding assistant since 22 April. From 1 September, companies can again book licences for GitHub Copilot Business and Copilot Enterprise. This clears the way for organisations that were unable to conclude new contracts in the meantime.
Copilot is an assistant that makes code suggestions directly in the development environment, completes functions and answers questions about the project context. Business and Enterprise differ from the single-seat offerings primarily through central administration: licences are assigned via the organisation, and policies apply team-wide rather than per person.
What the forced pause meant in practice
There is no reliable information on the reasons for the block, so speculation is left aside here. What matters is the effect: teams that had planned an introduction in spring or summer had to find alternatives or postpone. Anyone who used this time for an evaluation can now go into the rollout with clearer requirements.
For planning, this also means: do not rely in project plans on a single provider being permanently and unrestricted available. An assistance function in the development environment should remain interchangeable, without work processes depending on it.
Rollout: start small, stay measurable
A rollout rarely succeeds by distributing all licences at once. A staged approach has proven effective:
- Pilot group of a few developers, ideally across different project types – legacy maintenance behaves differently from new development.
- Clear question for the pilot: where does assistance measurably save time, where does additional review effort arise?
- Fixed duration and a date on which it is decided whether and to what extent a rollout will take place.
- Documentation of experiences, so that teams joining later do not start from scratch.
Expectations are important. An assistant delivers suggestions, not verified results. Anyone who promises productivity gains without factoring in the review effort merely shifts work to another point in the process.
Set rights and policies centrally
The team variants offer administration at organisation level – and that should be configured before the first licence assignment. Clarify in advance:
- Who may assign and revoke licences? Ideally this is tied to existing roles in identity management, not to individuals.
- For which repositories does use apply, and for which not? Customer projects with special contract clauses must be explicitly regulated.
- How are suggestions that resemble third-party code handled? Corresponding filter functions should be active and documented.
- What happens during offboarding? A licence that is not revoked costs money and remains an open access point.
Data protection: involve early on
With assistance systems that send code to an external service, two questions must be answered: what data leaves the company, and what happens to it there? Both belong in the processing documentation, not in a verbal agreement.
In practice this means: check the provider's contractual documents to see whether use of the transmitted content for training models is excluded, and record the result. Involve data protection officers and – where present – works councils before licences are distributed. Subsequent prohibitions are more expensive than clarification in advance.
A second point concerns secrets in source code. Credentials, keys and tokens have no place in repositories anyway. With an assistant that processes file contents as context, a bad practice becomes a concrete risk. A scan of the codebase before the rollout is time well invested.
Bring quality assurance along
If more code is produced in less time, the bottleneck shifts towards review and testing. Anyone introducing assistance without automated tests, static code analysis and binding review rules will mainly get technical debt faster – that is, rework that costs time later.
It therefore makes sense to look at quality assurance at the same time: are the pipelines robust? Is test coverage keeping up? Are there rules ensuring that generated code is reviewed just as thoroughly as hand-written code? These questions decide more about the benefit than the choice of tool.
Training as part of the rollout
Handling assistance systems is a skill that develops. Precise task descriptions, evaluating suggestions, sensible use of project context – nobody learns this simply through an assigned licence. An accompanying format in the team, whether a regular exchange or a short internal training session, pays off faster than additional licences.
The environment is also moving on: a one-day online event on AI-supported software development is scheduled for 16 September 2026, which will cover, among other things, the new agent protocols. Such protocols govern how AI components communicate with tools and data sources – a topic that goes beyond pure code completion and is likely to play a role in coming generations of tools.
What this means for projects
The reopening of new sign-ups removes a blockage, but does not replace an introduction strategy.
Anyone booking licences now should have clarified rights allocation, data protection documentation and review practice beforehand – otherwise effort arises in places where it was not visibly planned.And because tools and availabilities change quickly, the same applies to web and software projects as elsewhere: set up processes robustly, keep tools interchangeable.
Sources
- New registrations for GitHub Copilot Business and Enterprise permitted again — heise developer News
- Information day "AI for software developers" online on 16 September 2026 — heise developer News