GitHub Copilot plans compared
The exam loves “which plan?” scenarios. You need to know who each plan is for, who manages it, and what extra it adds.
The plans
| Plan | For | Key points |
|---|---|---|
| Copilot Free | Individuals trying Copilot | Limited monthly completions and chat messages |
| Copilot Pro | Individual developers | Paid, higher limits, more models. Free for verified students, teachers and maintainers of popular open source projects |
| Copilot Pro+ | Power users | Largest allowance and access to the full set of models |
| Copilot Business | Organizations of any size | Central seat and policy management, content exclusions, audit logs |
| Copilot Enterprise | Large organizations on GitHub Enterprise Cloud | Everything in Business plus knowledge bases, custom models, pull request summaries |
The older name for Pro was Copilot Individual, and Business was sometimes called Teams. The exam may still use those names.
Business versus Enterprise
Both plans are managed by an organization or enterprise. The difference is the extra capability and the licensing.
- Business works for companies whose code lives on GitHub, but also for companies using other hosts such as Bitbucket or Azure DevOps. It does not require GitHub Enterprise Cloud. Access can be tied to your identity provider when the organization uses enterprise-managed users or SAML.
- Enterprise requires GitHub Enterprise Cloud. It adds features that use your own organization’s context, such as knowledge bases (curated sets of Markdown docs that Chat can answer from) and custom models trained on your private code patterns.
Custom models give responses that follow the practices and patterns in your repositories. They do not guarantee correctness or speed.
Features available everywhere
Inline code suggestions and Copilot Chat work in all supported IDEs. Features tied to github.com, such as pull request summaries, belong to higher plans. When a question asks what works in every IDE, the answer is suggestions and Chat.
Administration
Organization owners:
- Assign or remove seats.
- Set policies, for example allow or block suggestions that match public code, and enable Copilot Chat.
- Configure content exclusions.
- Review the organization audit log. It records admin actions, not code suggestions.
Admins can also use the REST API to list seat assignments and to get usage metrics for the organization.
Exam traps
- A solo contractor uses Pro. Business is for managed seats, even for a small team.
- Business does not require GitHub Enterprise Cloud. Enterprise does.
- Audit logs track administrator activity. They do not track lines suggested or individual suggestions.
- Policies are set in settings pages, not in a repository file.
- Free for open source is not automatic for everyone. Verified students, teachers and maintainers of popular projects qualify.
Practice questions
Choose an answer, then review the explanation to check your understanding.
1. A freelance developer works on many customers' projects, and none of the customers object to Copilot. Which plan fits best?
Show answer
Answer: C.A single developer buying for themselves uses Copilot Pro. Business and Enterprise are for organizations that manage seats.
2. A company stores code in Azure DevOps and wants central policies and seat management. Which plan do they use?
Show answer
Answer: C.Copilot Business does not require GitHub Enterprise Cloud, so organizations with code elsewhere can still manage seats and policies.
3. Which Copilot plan adds knowledge bases and custom models on top of the Business features?
Show answer
Answer: B.Copilot Enterprise adds organization-level features, such as knowledge bases, custom models and deeper github.com integration. It needs GitHub Enterprise Cloud.
4. Where does an organization owner assign Copilot seats and set Copilot policies?
Show answer
Answer: B.Seats and policies are managed in organization settings, Copilot (or at enterprise level), not in files.