Skip to main content
AI NewsAI NewsAuto PublishingSEOCopilotGitHub Enterprise CopilotCopilot Standalone企业许可

GitHub Enterprise Starts Including Copilot Access: Fewer Seat Decisions, More Budget Control

The model starts with account-team enterprises while self-serve subscriptions roll out later

ENHE AI5 min1 views
GitHub Enterprise Starts Including Copilot Access: Fewer Seat Decisions, More Budget Control

Key takeaways

GitHub announced on October 28, 2026 that enterprises working with a GitHub or Microsoft account team can include Copilot access for every licensed GitHub Enterprise Cloud user. The new access model does not include monthly AI credits per seat. AI usage is metered from the first request against the enterprise budget. Users without a GitHub Enterprise license can receive equivalent access through Copilot Standalone for $10 per user per month. Code completion and next edit suggestions continue without an available budget, while Chat, code review, and cloud features require budget. This article helps administrators verify eligibility, compare licensed and standalone populations, and prepare a controlled transition without disrupting current subscriptions.

Eligible Enterprise licensed users can receive included Copilot access.
The model has no monthly AI credits per seat; usage is metered from the first request.
An exhausted budget does not remove access, but Chat, code review, and cloud features are affected.

By ENHE AI · 2026-10-30 · AI-assisted drafting and editorial checks.

Direct answer: Confirm the contract channel before planning a transition

Current availability targets GitHub Enterprise Cloud organizations working with a GitHub or Microsoft account team. Self-serve access is staged and current self-serve subscriptions are unaffected, so administrators should not change contracts based on the announcement alone.

Separate licenses, Standalone access, and AI budget

Licensed Enterprise users can enter the included-access model. Enterprise members without an Enterprise license may use Standalone at $10 per user per month. Both have the same features and models as Copilot Enterprise, but neither includes monthly AI credits per seat, and usage starts against the enterprise budget from the first request.

A work context related to this task, not a product interface or test result. Image: Unsplash.
A work context related to this task, not a product interface or test result. Image: Unsplash.

Prepare four evidence sets before migration

Export the Enterprise licensed-user list, non-licensed user needs, one month of AI usage, and the current Copilot contract. Record the budget ceiling, alert owners, cost attribution, and rollback date. Change subscriptions only after the account team confirms the model and effective date.

What changes when the budget is exhausted

Code completion and next edit suggestions continue without budget. Copilot Chat, code review, and cloud features require available budget. Exhaustion does not remove the seat or access entitlement. Acceptance testing should check each feature instead of treating a successful sign-in as proof.

Frequently asked questions

Can a self-serve subscription switch today?

Not necessarily. GitHub says self-serve availability will open in stages and current subscriptions are unaffected.

Does the $10 monthly Standalone price include AI credits?

No. Standalone and included access meter AI usage from the first request against the enterprise budget.

Why this matters

The purchasing question shifts from the number of Copilot seats to who holds an Enterprise license, who needs Standalone, and how AI budget is attributed and alerted. User lists and budget evidence matter more than product names.

Related tools and reading

These pages support the same task, workflow, or risk boundary.

Conclusion

Do not cancel current Copilot subscriptions immediately. First obtain eligibility confirmation from the GitHub or Microsoft account team, then export licensed users, non-licensed users, and current usage. Set budgets and alerts, and validate feature behavior with a small cohort before changing the wider contract.

What this means for everyday users

Code completion and next edit suggestions continue without budget. Copilot Chat, code review, and cloud features require available budget. Exhaustion does not remove the seat or access entitlement. Acceptance testing should check each feature instead of treating a successful sign-in as proof.

Related tutorials

Related reading

How to Migrate After the GitHub Copilot Billing Preview App Retirement

GitHub confirmed on August 4, 2026 that the Copilot Billing Preview app has been retired and is no longer available. Copilot spend now belongs in GitHub billing settings, including the AI Usage page, budgets, user-level budgets, cost centers, usage-pool allocation, downloadable reports, and the Billing API. Migration is more than replacing a bookmark. Export a final baseline from the old reporting process, map fields, time zone, currency, owners, thresholds, and notifications to the new controls, then run both reporting paths for one complete billing cycle where possible. Reconcile totals, users, cost centers, pools, exports, and alerts before archiving the old workflow. Document API authentication, pagination, rate limits, retries, and failure ownership without exposing credentials.

GitHub Copilot Code Review Adds Organization Billing and External License Controls

GitHub added organization-level billing and license controls to Copilot code review on October 8, 2026. By default, a licensed member's own Copilot entitlement pays for a review, and the review can fail when that quota is exhausted. Organization owners may instead charge the organization that owns the repository, provided paid AI Credits usage is enabled, with an optional budget. Owners and repository administrators can also restrict requests made with a personal or other external Copilot license. This guide explains how to choose the billing source, test authorized and unauthorized request paths, verify budget behavior, and preserve human review. Changing who pays does not grant access by itself, and organization-level restrictions can prevent repository administrators from loosening the rule.

GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts

GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.

Anthropic Expands AI for Science: How Researchers Can Check Access to Claude Credits

Anthropic expanded its AI for Science program on October 28, 2026, highlighting partnerships with 20 scientific foundations, institutions, and research groups that will distribute free Claude credits for high-impact projects. The announcement says researchers use Claude for hypothesis generation, experiment design, data analysis, and communicating findings. It does not provide one universal application form or promise credits to every scientist; eligibility and distribution depend on each partner. This article helps researchers identify the relevant organization, define a bounded research task, document data and review requirements, and separate confirmed access from editorial advice before putting AI safely into a scientific workflow.

GitHub Copilot Fusion Is GA: How to Choose Standard, High, or Max

GitHub made Copilot Fusion generally available on October 28, 2026. Instead of choosing a model for each step, users select Standard, High, or Max effort while Fusion routes and orchestrates models through single-model, cascade, or critique workflows. Administrators control which models Fusion may use and whether it is the default. The feature is available across all Copilot plans in VS Code, the Copilot app, Copilot CLI, and JetBrains IDEs. Each model used is billed at its standard rate; paid plans receive a temporary 30% discount on model costs. This guide shows how to compare the three effort levels with one task, fixed acceptance criteria, elapsed time, and complete usage evidence.

GitHub Copilot Can Generate and Edit Images: Check Cost, Watermarks, and File Output First

GitHub introduced a public preview for generating and editing images in Copilot on October 28, 2026. A user can describe an asset in VS Code, the GitHub Copilot app, or Copilot CLI. The selected reasoning model calls a dedicated tool powered by GPT Image 2.5 Flare, previews the result inline, and saves it into the project. The preview is available to Pro, Pro+, Business, and Enterprise plans. Image tokens are billed separately from the chat model against AI credits, and the visible “Made with AI” watermark is optional and off by default. This guide provides a bounded asset test covering input, output location, review, disclosure, and cost evidence.

Sources

Table of contents

Latest Insights