[BUG]: Enterprise Copilot seat assignment blocked access to feature, prevents creating personal subscription

Thanks for taking the time to fill out this out! :bow: By submitting this issue, you agree to follow our Code of Conduct.

What happened?

What did you do? What happened? What did you expect to happen?

Sorry for the awkward wording.

tl;dr: My day job bought Copilot for the organisation, but chose to disable the CLI feature. I want to use it for a side project on my personal machine, but can't subscribe as I'm already assigned an enterprise seat.

Background

My GitHub account, which I use for personal and also within an organisation, has been assigned an Enterprise Copilot seat by one of the organisations I contribute to. In Billing summary > Add-ons > GitHub Copilot I see:

You are assigned a seat as part of a GitHub Copilot Enterprise subscription managed by (ORG).
I see that Setting up GitHub Copilot in the CLI says:

If you have a GitHub Copilot Individual subscription, you can install the GitHub Copilot in the CLI extension without needing to enable it for your organization.

If you are part of an organization with a GitHub Copilot Business subscription, the organization owner will need to enable Copilot in the CLI in the Copilot settings. You can then install the GitHub Copilot in the CLI extension.

And under Enabling or disabling Copilot in the CLI at the organization level says:

An organization owner can enable or disable Copilot in the CLI for the organization.
Under Settings > Copilot, I see my organisation has disabled this feature:

Copilot in the CLI: Disabled This setting has been set by (ORG) administrators. Learn more about Copilot in the CLI.
However, I want to use it on my personal machine to contribute outside this organisation which has provided me the Copilot Enterprise seat. I am happy to pay for a personal subscription, as I reiterate Setting up GitHub Copilot in the CLI which says:

If you have a GitHub Copilot Individual subscription, you can install the GitHub Copilot in the CLI extension without needing to enable it for your organization.

But under Settings > Billing > Add-ons there's no way for me to subscribe, as the message explaining I'm assigned the seat by the organisation, has replaced the functionality to create a personal subscription.

What I'd expect:

✅ My organisation should be able to choose which features they assign me
✅ I can use those features when logged in to my organisation (including their enterprise login Okta etc. extra layer of authentication)
❌ If one organisation provided me Copilot in the IDE and block the CLI feature, I should still be (but am not) able to buy the feature they didn't provide.
❌ in other words, I should be able to pay for use of Copilot in the CLI for personal use, or for use in my own organisation, even if none of my organisations have provided it to me.

Workarounds

I'm sure if I created a new GitHub account I'd be allowed to create a personal subscription, but then I'd have to move all my repositories over to that account. (there's problems with that, e.g. GitHub pages custom domain CNAMEs point to that account). This is the first GitHub feature that would require separate accounts :(

Versions

What versions of the relevant software are you running? For example: gh v2.37.0, gh-copilot v0.5.2-beta

$ gh --version
gh version 2.50.0 (2024-05-29)
https://github.com/cli/cli/releases/tag/v2.50.0

$ gh copilot --version
version 1.0.3 (2024-05-08)

Relevant terminal output

Please copy and paste any relevant terminal output. Please check your output before submission to ensure sensitive information is redacted.

gh copilot explain "sudo apt-get"

✗ Error: User is not authorized to use this Copilot feature

To start using GitHub Copilot in the CLI, request access from your organization admin.

no option to subscribe :(

github / gh-copilot