Step-by-Step Copilot License Activation Guide
From order confirmation to your first accepted suggestion in the editor — here's exactly what to click, in order.
Last updated:
To activate a GitHub Copilot license: (1) the organization owner assigns the seat to a developer's GitHub account in Settings → Copilot; (2) the developer installs the Copilot extension in their IDE; (3) the developer signs in with the same GitHub account; (4) Copilot suggestions appear in the editor immediately. Most activations complete in under 5 minutes per developer.
Once your Copilot seats are purchased, activation is a five-step process. Most teams complete it in 20-30 minutes. This guide assumes you've already received an order confirmation from Copilot or GitHub and you have admin rights on the target organization.
Step 1: Verify the Organization
Sign in to GitHub and go to your organization's Settings. Confirm that your account shows as Owner. If you only see Member, an existing owner needs to elevate you before you can manage Copilot.
Step 2: Open Copilot Settings
From the org settings sidebar, navigate to Copilot → Access. You should see your seat allocation reflected here within a few minutes of purchase. If seats haven't appeared after 15 minutes, contact support — that's almost always a billing-account mismatch.
Step 3: Configure Policies First
Before assigning seats, set your org policies. The defaults we recommend:
- Suggestions matching public code: Block
- Copilot Chat: Enabled
- Copilot in pull requests: Enabled (Enterprise)
- Telemetry / prompt collection: Disabled
Setting these before users sign in means they get the right experience from suggestion one.
Activate policies before seats. It's much easier than retrofitting policy changes after developers have built habits.
Step 4: Assign Seats
Under Access, choose Assign to selected users (recommended) or Assign to all members. Bulk-add by typing usernames or by selecting an existing team. Each user receives an email notification automatically.
Step 5: Developer Sign-In
Each developer needs to:
- Install the Copilot extension in their IDE (VS Code, JetBrains, Visual Studio, Neovim, or Xcode).
- Sign in with their GitHub account — the same one that's been assigned the seat.
- Open any code file and start typing — suggestions should appear within seconds.
Troubleshooting
If a developer signs in but doesn't get suggestions, 9 times out of 10 it's one of: wrong GitHub account selected in the IDE, SSO session not authorized for the Copilot org, or a stale extension version. Have them run the IDE's Copilot: Status command — it surfaces the right error.
That's it. Once the team is signed in, you're done. If you'd like activation handled for you, our team can take care of it end-to-end — or see pricing to get started.
Frequently Asked Questions
Common questions related to this guide — sourced from real searcher queries.
After your seat is assigned: (1) install the GitHub Copilot extension in your IDE; (2) sign in with the GitHub account that received the seat; (3) start typing — inline suggestions appear immediately. Most activations complete in under five minutes per developer. Copilot typically issues the seat within 24 hours of order confirmation.
An organization owner cancels seats from Settings → Copilot → Access on the GitHub organization page — you can revoke individual seats or disable Copilot entirely. The license is active until the end of the current billing period. For Copilot-managed annual plans, cancellation within 14 days of activation qualifies for a full refund.
To cancel a GitHub Copilot subscription: individuals go to Settings → Billing and plans → Plans and usage → Copilot → Cancel. Organization owners go to Settings → Copilot → Access on the org page. The subscription stops at the end of the current period. Our annual plans include a 14-day money-back guarantee.
Yes — GitHub Copilot Chat supports Claude Sonnet as a selectable model alongside the OpenAI GPT models and Google Gemini. The model picker is in the Copilot Chat toolbar. Copilot Enterprise customers get priority access to the highest-tier Claude variants.
Yes — GitHub Copilot Chat supports web search through the @web participant (in VS Code) or the Bing-powered web tool in GitHub.com Copilot Chat. The agent can fetch up-to-date documentation and Stack Overflow answers and cite them in the response.
Check the official GitHub Status page — it lists current incidents affecting Copilot, Actions, Packages, and other services. If Copilot is degraded, completions may be slow or temporarily unavailable; suggestions resume automatically once the incident is resolved. Copilot does not operate the Copilot service.