GitHub Copilot Enterprise Access troubleshooting in VS Code

[jsinha-lab]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Hi team,

I was recently granted the GitHub Copilot Enterprise Access role through Access Manager.

However, I'm still unable to use Copilot in VS Code. After restarting VS Code and my Mac, Copilot continues to prompt me to upgrade to GitHub Copilot Pro.

When I click Upgrade and sign in with organization account, it redirects me to the GitHub billing page, which makes me think my Enterprise entitlement isn't being picked up.

Has anyone seen this before or know if there's an additional setup step required ?

Any suggestions would be appreciated. Thanks!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[initial-d]

I would first separate two things that sound similar but are not always the same:

1. Being granted a role/permission through Access Manager.
2. Having a Copilot seat/license assigned to the exact GitHub account that VS Code is signed into.

GitHub’s Copilot docs describe a Copilot seat as the license that gives a user access under an organization or enterprise plan, and users must be assigned a seat to use Copilot features under that plan:

https://docs.github.com/en/copilot/reference/copilot-billing/seat-assignment

I would check this in order:

1. Ask an org/enterprise owner to confirm that your exact GitHub username appears under the organization’s Copilot access page, not only in Access Manager.

   Path for org owners is usually:

   Organization -> Settings -> Copilot -> Access
   

   Docs: https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-access/grant-access

2. Open this while signed in as the same account you use in VS Code:

   https://github.com/settings/copilot
   

   If that page still says you need to upgrade to Pro or does not show your organization/enterprise entitlement, the problem is probably license assignment, team sync, org membership, or enterprise policy rather than VS Code.

3. In VS Code, make sure the active GitHub account is the same one that received the seat. This matters a lot if you have both a personal account and an organization/managed-user account.

   I would try:

   • Command Palette -> GitHub: Sign Out
   • Command Palette -> GitHub Copilot: Sign Out
   • reload VS Code
   • sign back in with the exact GitHub account that has the Copilot Enterprise seat

4. If your company uses Enterprise Managed Users, make sure VS Code is signed into the managed enterprise user, not a personal GitHub.com account with a similar email.

5. If the seat was assigned through a team, ask the admin to confirm the team membership has synced and that Copilot access is enabled for that organization. A pending org invitation or stale IdP/team sync can look like “access granted” administratively while the user still has no usable seat.

The redirect to the billing page usually means the extension/browser session is not seeing an active Copilot entitlement for the signed-in account. So the fastest test is: does github.com/settings/copilot show the enterprise/org plan for that same account? If not, fix the seat assignment first. If yes, refresh the VS Code GitHub/Copilot sign-in token.