Verified decision guide
Copilot Personal to Organization: Billing and Seat Changes
Understand automatic personal-plan cancellation when the same GitHub account receives an organization Copilot seat, refunds, policies and the billing-report path.
Direct answer · the same GitHub user account
Assignment replaces the personal paid plan under the documented path
When the same GitHub user with personal Pro/Pro+/Max receives a Business/Enterprise seat, GitHub automatically cancels the personal plan and refunds its unused billing-cycle portion pro rata. Organization policies apply.
This is a documented assignment transition, not a general promise that you can choose either personal or organization credits for each request. Separate GitHub logins and seats spanning different billing entities need their own account checks.
Verify the transition in order
- Confirm that the organization assigned the seat to the same GitHub username that owns the personal subscription. A second account is not entitlement overlap on the first account.
- In account Settings → Billing & licensing → Licensing (or Plans and usage on the original platform), verify the current plan. Organization-managed users cannot change or cancel that assigned plan through personal subscription controls.
- Check cancellation and the prorated refund for the remaining personal billing cycle. The docs state the refund basis; an exact settlement date or amount still depends on the billing record.
- Ask the administrator which organization or enterprise bills the seat and which policies and user budget apply. Current organization AI Credits pool at that billing entity; see credit pooling.
- Use the organization/enterprise billing report for organization-paid usage. Personal billing API endpoints omit usage billed through an assigned organization or enterprise license. For per-user analysis, follow charge attribution.
Do not infer these outcomes from the seat label
| Situation | Supported next action |
|---|---|
| Same user: personal paid plan → Business/Enterprise assignment | Verify automatic personal cancellation, prorated refund and organization policy. Do not add both allowances into one personal pool. |
| Several organizations within one enterprise | GitHub documents seat deduplication and a monthly billing-organization choice. That license-charge rule does not establish a universal per-request credit-payer preference. |
| Different GitHub accounts or different billing entities | Unknown — account_dependent. Inspect account authentication and each administrator's billing scope; do not invent personal-first or organization-first routing. |
| Remaining personal credits or later removal of organization access | Unknown — unresearched. These sources do not establish a credit transfer or automatic restoration of the previous personal paid plan. Check current entitlement before resubscribing. |
For a legacy annual Pro/Pro+ contract, verify the legacy contract guide as well. Cancellation credit/refund timing does not retroactively convert past premium requests into current AI Credits.
Once assigned, use organization budget controls for paid continuation. A vanished personal usage card is not proof that organization work is free.
Sources and freshness
- Copilot seat assignment and personal cancellation
- Viewing and changing Copilot plans
- Copilot organization and enterprise usage billing
- GitHub billing usage API account scope
Review monthly and on seat assignment/removal or policy changes. Reverify cancellation/refunds and billing-entity scope; multiple billing entities and separate logins require account inspection.
For current plans and allowances, see the product guide.