If your employer assigns a GitHub Copilot Business or Enterprise seat to the same GitHub account that has your paid personal Copilot plan, you normally do not need to cancel the personal plan first. GitHub documents automatic cancellation and a prorated refund for the remaining personal billing period.
The key is confirming which account receives the seat. A separate work or Enterprise Managed User account is not the same identity as your personal account.
1. Confirm the account and the intended plan
Give the administrator your exact GitHub username and confirm whether you should use that account or a separate managed work identity. Do not rely on similar display names or email addresses.
GitHub’s seat-assignment reference says that an account with Copilot Pro, Pro+ or Max has its personal plan canceled automatically when assigned Business or Enterprise access, with a prorated refund. The organization’s policies then apply. That documented rule concerns the account receiving the seat; do not assume a license assigned to a different work account cancels your unrelated personal subscription.
Before switching, note your current plan and billing date. If you want to keep personal and work identities separate, discuss the account arrangement with your administrator before any purchase or cancellation.
2. Have an authorized administrator assign the seat
For an organization-managed assignment, the owner uses the organization’s Settings → Copilot → Access controls to select the intended member or team and confirm the purchase. This is a billing action: charges begin when access is granted, not when the developer first uses it. Administrators should review the selected users and cost rather than enable every member as a troubleshooting shortcut. See GitHub’s assignment instructions.
Existing members do not all need to accept a separate, standardized “Copilot invitation.” A user who is not yet a member may receive an organization invitation as part of the documented process. Verify any invitation by opening GitHub directly and checking the organization and account; do not depend on a particular email subject.
Ask the administrator to confirm the actual assignment. If it is missing or pending, investigate membership and purchasing state. Do not repeatedly remove and re-add the seat; revocation can interrupt access and billing changes have their own timing. See the license-change reference.
3. Verify billing and connect the correct IDE account
On GitHub, open your profile menu, then Settings → Billing & licensing → Licensing. On the original billing platform, the equivalent view is Billing and licensing → Plans and usage. Check the current plan and compare the billing history with the assignment date. GitHub’s plan-management guide describes both interfaces.
For a same-account migration, verify the automatic cancellation and the refund record rather than buying another plan. If the record differs from the documented behavior, contact GitHub Support with account and invoice details through its secure support process. A refund’s appearance in your bank account is not an IDE activation test.
In VS Code, inspect Accounts → Manage Extension Account Preferences for GitHub Copilot Chat and choose the intended workspace or profile account. Follow the official setup guide. If the right account has access but the session remains stale, use the documented authentication refresh, then test a small request.
4. Handle separate accounts and policy differences
If your employer’s seat is on a different account and you no longer want your personal subscription, cancel that personal subscription deliberately from its own billing page after verifying work access. Read the confirmation: ordinary self-service cancellation retains current access until the billing cycle ends and follows different refund rules from the automatic same-account transition. Never delete the GitHub account to cancel Copilot.
Expect some behavior to change under the organization’s policies. An unavailable model or disabled feature is not necessarily a failed migration. Ask the administrator which account, clients and features are approved, and do not switch to a personal account to bypass work restrictions.
Finish by checking three things independently: the assigned account has access, billing reflects the intended arrangement, and a permitted Copilot feature works in the editor. Keep the invoice and assignment details if a support follow-up is needed.
Official documentation checked October 14, 2026. Exact billing adjustments should be verified in the account’s billing record.