[Feature Request] Add ability to have multiple Copilot licenses (both personal and Business) under one github account

[pboushy]

Select Topic Area

Product Feedback

Body

First, I am fully aware that the current recommendation is to use a second GitHub account. Please don't comment just to say that.

I've found alot of discussions on this topic, but haven't found one that is clearly a feature request.

Request

Please add the ability to have multiple Copilot licenses, both personal and business, under one user account.

Background

I am required by the company I work for to not use work resources for personal/opensource projects.
I have GitHub Copilot for Business from the company I work for.
I want the ability to have GitHub Copilot for individual for personal/opensource projects I work on.

I don't want to have to create a separate GitHub account for work and personal. It's really nice having all contributions under one account.

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

[hades200082]

Ditto: https://github.com/orgs/community/discussions/188809

[alefranz]

I feel like this limitation is becoming an own goal for GitHub Copilot.

By preventing engineers from using a personal Copilot subscription for their experimentation, learning, and hobby projects, while simultaneously holding a Business/Enterprise seat for work, GitHub is unintentionally pushing developers toward competitors. People naturally want to explore AI tools outside of work, and if Copilot can't be used in that context, they will learn and grow comfortable with alternative products. Inevitably, those same developers will then advocate for those competing tools inside their companies.

This feels counterproductive and very unlike the long‑standing Microsoft strategy of empowering professionals to use the same tools across personal and professional contexts, which historically helped consolidate loyalty and familiarity.

Allowing dual licensing on a single GitHub account would solve this cleanly, avoid fragmentation, and keep developers within the GitHub ecosystem across all parts of their work.

We’ve already seen that GitHub can adapt licensing models when the community pushes back. The recent change allowing students to purchase individual Copilot plans, while still keeping their other student benefits, came directly after the backlash around losing access to the better models. That decision showed that GitHub is willing and able to introduce flexible licensing paths when it benefits learning, adoption, and long‑term loyalty. The same principle applies here: professionals who want to invest personally in Microsoft tooling outside of work should be supported, not pushed toward competitors simply because the current licensing model blocks them from using Copilot in their own time.