GitHub Copilot Code Review adds billing and access controls
GitHub adds Copilot Code Review controls for organization billing and externally licensed requests. Exact settings, defaults and limits.
GitHub's October 8 update lets organizations choose centralized billing for Copilot Code Reviews and restrict requests funded by external Copilot licenses. These are controls for code review, not a change automatically inherited by every Copilot agent.
On October 8, 2026, GitHub announced two administrative changes for Copilot Code Review. Organizations can choose how review requests made by licensed users are billed, and administrators gain more control over which licensed accounts may request a review in a repository. These options address cost allocation and request authorization in a particular review workflow, not a global transformation of all GitHub Copilot agents.
What changed exactly?
By default, GitHub says a Copilot code review requested by a member with a Copilot license consumes that member's own entitlement. If the quota is exhausted, the review request fails. An organization owner can instead choose to charge the organization that owns the repository. This requires AI Credits paid usage to be enabled for that organization, and a budget can optionally be configured.
For teams this can make shared review costs easier to manage, but it is not a promise of free or unlimited reviews. Administrative decisions still determine budgets and who bears the bill. Organizations should inspect the relevant Copilot policy before changing it and monitor usage against the budget they actually enable.
Who benefits and what remains uncertain?
The second option concerns review requests from accounts using an externally provided Copilot license. GitHub says that, by default, anyone with a paid Copilot license and access to the repository can request a review. Organizations and repository administrators can enable Only allow Copilot code review to be triggered by authorized users, restricting such requests to qualifying organization- or enterprise-provided licenses.
When that restriction is enforced at the organization level, repository administrators cannot disable it locally. This is relevant when contractors, multiple teams or personal Copilot subscriptions participate in the same codebase. It is not a substitute for repository access controls, and it does not establish that generated code-review findings are correct, complete or free of false positives.
GitHub documents the settings in its organizational Copilot policies and code-review controls. AgentenCode treats the release as evidence about a particular Code Review service. The adjacent GitHub Copilot Coding Agent profile provides broader context, but the new billing and license policies should not be inherited by unrelated agent capabilities without a separate source.
Frequently asked questions
Will Copilot Code Review automatically bill organizations?
No. GitHub says member billing remains the default. Organization billing is an optional setting that requires paid AI Credits usage.
Can organizations restrict externally licensed review requests?
Yes. An optional policy can require qualifying organization or enterprise-provided Copilot licenses for review requests. Repository access remains a separate control.
Source verification
Primary sources and product scope
Official documentation. No independent benchmark or implied cross-product functionality.