⁉️ Copilot charges against 1x org only? I have paid plans in 2x different orgs.

[PureKrome]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Copilot in GitHub

Body

Today (2nd June) I tried to use Copilot in Visual Studio and it asked me to selected/define which org to charge all AI usage against.

In my list of options, I have 2x orgs in the drop down.

✅ So if I do work on a repo against Org 1 (which is the "selected" org in that setting drop down), I'll be charged against that org.
⁉️ If i switch to repo 2 which is part of Org 2 (which is NOT selected for AI charging) .. then what? My copilot usage will be charged against Org 1 which is totally unfair?

A repo is part of an Org. As such, I should be charging the org which is linked to the repo, right?

EDIT: And if I jump between repo's, I guess I'll need to keep switching the Org in the Drop Down. Given this, is there a 'lag' between github accurately seeing which org to charge. Eg. change the org in the drop down .. wait 5 mins .. then go? or can go straight away?

Final Thoughts (if i've got this right): this is really painful.

[mjmirza]

You are reading it right. The billing org is your active dropdown selection, not derived from the repo, so usage hits whichever org is picked even when the repo belongs to the other one.

Switch it before you start in the second org, and expect a short delay after changing it.

[PureKrome]

Thanks @mjmirza - appreciate jumping into the conversation 🤗

Wow - that's really ... unusable. Such a shame as we might have to move over to an easier model like with a competitor now.

Here's our use case:

• A consultancy
• about 50 devs
• a few hundred clients (think: projects/repos == a GH Org (for billing and security purposes)).

So we will need to charge our usage to the client we are doing work against. Some clients also need to see our usage as part of proof we are fairly charging for various line items. As a consultancy, we also need to accurately assign our costs internally, per client.

For us to constantly switch our billing-org as we jump around between different clients, during a day/week is just such a poor user experience. Literally a PITA.

If the org-billing is tied to the repo, then this would be a usable product. I'm not sure what copilot options are available without a repo which makes this problem more challenging .. but if there are non-repo copilot activities, then have a "fall back" option .. which could be the current one.

OH! just to add insult to injury, a number of my colleagues also have PERSONAL paid copilot which they want to use for their personal, private/public repo's. So how would that be billed?

This project needs some billing work/consideration please. Until then, we'll have to use a competitor.