Copilot Business can now take over your personal account

[versile2]

Select Topic Area

Product Feedback

Copilot Feature Area

Copilot in GitHub

Body

I upgraded my personal account to Copilot Pro+ specifically to learn Copilot’s full feature set and workflows. However, because I am a member of an organization that has assigned me a Copilot Business license with restrictive policies, my personal Pro+ subscription is effectively unusable.

The issue is not cost or intent—I am explicitly paying for expanded personal access—but organizational enforcement appears to override personal licensing with no opt-out, no per-context toggle, and no visibility into what is being restricted. This makes it difficult to experiment, learn, or evaluate Copilot outside the scope of my employer’s policy.

I understand why organizations need centralized controls. What is missing is a clean separation between organizational context and personal context. As it stands, a single organization membership can silently nullify a paid personal subscription across all repositories and environments.

This creates a poor experience for contributors who:

work in multiple organizations,
contribute to open source in a personal capacity, and
are trying to responsibly learn Copilot without violating employer policy.

At minimum, clearer messaging and an explicit “personal Copilot context” would help. Ideally, personal subscriptions should remain usable outside organizational repositories, regardless of org-level enforcement.

I’ve opened a support ticket, but given the number of similar reports, this feels like a product design gap rather than an edge case.

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