GitHub Copilot Student subscription not recognized in VS Code (Prompting for Pro upgrade)

[Volynskyi-Kirill]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Hi everyone,

I’m experiencing an issue where my GitHub Copilot Student subscription is not being recognized within Visual Studio Code, despite being active on my account.

The Situation:

• Subscription Status: My GitHub account settings confirm that GitHub Copilot (via the Student Developer Pack) is active. I have been using it for about 3 months now.

• The Problem: VS Code continues to show that I do not have a subscription and repeatedly prompts me to "Upgrade to Pro."

• Account Verification: I have double-checked and I am definitely logged into the correct GitHub account in VS Code.

What I have tried so far:

1. Re-logging: I signed out of my GitHub account in VS Code and signed back in.

2. Extension Reinstall: I uninstalled and reinstalled the GitHub Copilot and GitHub Copilot Chat extensions.

3. Sync Check: I verified that my subscription is still valid on my GitHub Billing/Plans page.

Despite these steps, the "Pro upgrade" prompt persists, and the Copilot features remain unavailable in the editor.

Has anyone else encountered this "sync" issue between the GitHub Student status and the VS Code extension? Any guidance on how to force the editor to refresh my subscription status would be greatly appreciated.

Environment:

OS: Windows 11
VS Code Version: last
Extension Version: last

[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. ⭐