How can a GitHub Team organization purchase Copilot Business for 4 members when the Copilot settings are missing?

[Varatharajan-Raja]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Copilot in GitHub

Body

Question

I am an owner of a GitHub organization that is currently on the GitHub Team plan. The organization has four members, and we want to purchase GitHub Copilot Business for all four users.

However, I cannot find any Copilot section or purchase option in the organization settings. I checked the organization settings, including the "Code, planning, and automation" section, but there is no Copilot or Copilot Access menu.

Current setup

• Organization plan: GitHub Team
• Number of organization members: 4
• Desired product: GitHub Copilot Business
• Desired number of licenses: 4
• I am an owner of the organization
• The organization should remain on GitHub Team unless an Enterprise upgrade is genuinely required

What I found in the documentation

GitHub's documentation says that new self-service Copilot Business sign-ups for organizations on GitHub Free and GitHub Team have been temporarily paused since April 22, 2026.

The documentation also describes using a dedicated enterprise account to manage Copilot Business licenses without adopting or paying for GitHub Enterprise licenses. It appears that users can be added directly to that enterprise and assigned Copilot Business licenses.

Questions

1. Is contacting GitHub Sales and requesting a dedicated Copilot-only enterprise account currently the only supported way for a GitHub Team organization to purchase new Copilot Business licenses?

2. Can we keep our repositories and existing organization on GitHub Team while assigning Copilot Business licenses directly to the same four users?

3. Should our existing GitHub Team organization remain separate from the dedicated enterprise account, with only the users added directly to the enterprise?

4. Can our existing organization be connected to the dedicated enterprise without causing us to be charged for GitHub Enterprise licenses?

5. Is there another self-service or support-assisted purchasing method for a small organization that only needs four Copilot Business seats?

6. Is there an announced date for self-service Copilot Business purchasing to become available again for GitHub Team organizations?

[pravendrarj]

Hi @Varatharajan-Raja ,

Your understanding is correct. The missing Copilot option is expected under the current purchasing restriction, not necessarily an account-permission problem.
Since April 22, 2026, GitHub has temporarily paused new self-service Copilot Business sign-ups for organizations on GitHub Free and GitHub Team.

With my experience of configuring GH enterprises for my customers, I can say that Yes, the GitHub sales team can assist you. However, approval or rejection of your request is at the total discretion of GitHub Team.

However, what you can do is...... create a GitHub Enterprise with personal account, but do not create an organization within that enterprise. add your 4 users as unaafiliated users and activate the Copilot. Then assign them a Copilot Business license at enterprise level.

The users can remain members of the existing Team organization while also being direct members of the Copilot-only enterprise. Their Copilot licence is associated with their personal GitHub account, so they can authenticate in their IDE and use Copilot while working with repositories in the Team organization.

You should not add or transfer the existing Team organization to the dedicated enterprise if your objective is to avoid GitHub Enterprise licences. GitHub’s setup documentation explicitly says not to create organizations in the dedicated enterprise because adding users through an organization assigns GitHub Enterprise licences. Users should instead be invited directly to the enterprise.

Therefore, the answers are:

Is Sales currently required? Yes. GitHub’s documented setup instructs customers to contact GitHub Sales to purchase Copilot for the dedicated enterprise.
Can the organization remain on GitHub Team? Yes. Keep it separate and assign Copilot Business directly to the same four personal accounts through the dedicated enterprise.
Should the users be added directly to the enterprise? Yes.
Should the Team organization be connected to the enterprise? No, not if you want to avoid GitHub Enterprise licensing.
Is another self-service Copilot Business method currently documented? No. Individual Copilot plans are self-service alternatives, but they do not provide the centralized licensing, policy management and business protections of Copilot Business.
Has GitHub announced when self-service purchasing will return? The documentation currently describes the pause as temporary but does not provide a reopening date.

[Raph049]

It could be that You're not an organization owner or the organization is managed by an Enterprise that hasn't enabled Copilot.

[RoopanshG]

Hey @pravendrarj ,

I think we're in a very similar situation to this post. We want Azure SSO/Entra ID linked to Copilot for Business licences, while continuing to keep all our repositories in Azure DevOps. Really, we're only interested in the Copilot coding capabilities, not GitHub repos, projects, or other cloud features.

Can I ask what will be the best setup for us? Do we need a paid GitHub Enterprise subscription, or will a free Enterprise account/container available and sufficient? Only sales can create this free container, right? The support team's emails are just confusing us more by the terms they are using, their billing and licensing is so annoying for some reason.

Also, can we be paying just USD $19/user for the 10 Copilot Business users, or do will we have to use GitHub Enterprise licences (USD $21/user) on top of that? If yes, why will Github Enterprise Accounts' cost be for per user, it should be just a one-off creation cost for an account, right?

We're hoping to avoid paying for GitHub Enterprise if possible, since we don't plan to use GitHub for source control and only want the Copilot functionality.

Thanks so much for your help in advance!

[pravendrarj]

hi @RoopanshG
I understand and that is where the GitHub EMU (non-GHE) instance comes into the picture.
Create and enterprise , do not create any Organization, set up SSO, Auto-provisioning with IdP and other steps. Setup billing with CSP partner Azure sub.
then Billing and licensing --> Licensing --> copilot --> Manage

if you dont see this option, then may be GH sales team can help.
However, if you are looking for a CSP partner and CSP discounts, let me know... I can ask my team to get in touch with you.

[pravendrarj]

@RoopanshG you will be paying only for GHCP business licenses and not the GH Enterprise base license.

[RoopanshG]

Thanks so much @pravendrarj :).
Much appreciated

[AdityaBarmade]

Thanks for the detailed writeup — this matches what I've found too. Here's what I can confirm from GitHub's official docs and other threads on this:

1. Is contacting Sales for a dedicated Copilot-only enterprise the only route?
   Yes, currently that's the supported path. GitHub paused new self-serve signups for Copilot Business on GitHub Free and Team plans as part of efforts to keep the Copilot experience reliable, and existing Copilot Business customers aren't affected and can keep adding seats normally. For new Business subscriptions on a Team-plan org, going through Sales for a dedicated enterprise account is the workaround people are being pointed to.
   The New Stack

2. Can you keep your existing org on Team while assigning Copilot Business licenses to the same 4 users?
   Yes — based on another confirmed thread on this exact setup, this is officially called a "dedicated enterprise for GitHub Copilot Business." Your repos and org stay on Team; the 4 users get added directly to a separate enterprise account solely for license assignment, and you pay only the $19/user/month Copilot Business rate — not GitHub Enterprise Cloud seat pricing.

3. Should the org remain separate, with only users added to the enterprise?
   That matches what Sales sets up — the enterprise account exists just to hold Copilot licenses, not to absorb your organization or repos.

4. Will connecting to the dedicated enterprise trigger Enterprise Cloud charges?
   Per the same source, no — you're only billed for the Copilot Business seats, not Enterprise Cloud licensing, as long as it's set up as a dedicated Copilot-only enterprise.

5. Any other self-service or support-assisted method for just 4 seats?
   Not currently — self-serve is paused for Free/Team orgs regardless of seat count, so Sales contact is the only route right now, even for small orgs.

6. Any announced date for self-serve to reopen?
   Not that I've found. GitHub's changelog only says they'll share an update when self-serve signups reopen — no ETA given as of now.

Recommendation: Reach out via github.com/enterprise/contact or your account rep and explicitly request a "dedicated enterprise for GitHub Copilot Business" — that phrasing gets you to the right internal process quickly based on others' experience.

[d1fallah]

1. Is contacting GitHub Sales the only supported route right now?

Yes. Because direct self-service sign-ups for standalone GitHub Team and Free organizations are temporarily paused, reaching out to GitHub Sales (or GitHub Support) to set up a dedicated Enterprise Account structure is currently the primary official path to purchase new Copilot Business seats.
2. Can we keep our existing GitHub Team organization and repositories intact?

Yes, absolutely. You do not need to migrate your repositories or change your core workflow. Your organization remains on the GitHub Team plan, and your existing repositories stay exactly where they are.
3. Should our Team org remain separate or be linked to the Enterprise account?

You can link your existing GitHub Team organization directly under the newly created Enterprise Account structure. Linking your organization allows you to easily manage and assign Copilot licenses to your existing organization members without altering their org membership.
4. Will connecting our org to an Enterprise Account trigger GitHub Enterprise license fees?

No. Linking a GitHub Team organization to an Enterprise Account does not automatically upgrade or bill your members for GitHub Enterprise Cloud seats ($21/user/mo). As long as you only assign GitHub Copilot Business licenses through the enterprise management portal, you will only be billed for your GitHub Team plan + your 4 Copilot Business seats.
5. Is there another self-service alternative for a 4-person team?

Currently, there is no self-service toggle available in the organization settings for standalone Team orgs. The Sales/Support-assisted path creating an Enterprise management layer was specifically put in place by GitHub so small teams can still acquire Copilot Business without forced plan upgrades.

(Note: While individual users can purchase Copilot for Individuals personally, that lacks centralized org billing, policy management, and IP indemnification, so the Sales-assisted route remains best for business use).
6. Has GitHub announced a date for re-enabling self-service sign-ups?

Not yet. GitHub has not provided a specific public timeline or date for when self-service Copilot Business purchasing will resume for standalone GitHub Team organizations. Keep an eye on the GitHub Blog or the GitHub Public Roadmap for official announcements.
Recommended Next Step

Fill out the Contact Sales form on GitHub or open a ticket with GitHub Support, explicitly mentioning:

"We are a 4-member GitHub Team organization looking to purchase 4 GitHub Copilot Business seats via a dedicated Enterprise Account while direct self-service is paused."

[ZainAlabdin878]

unfortunately, it's stopped for enterprise as well, that's my case. thank you

…

________________________________ From: Pravendra Rajput ***@***.***> Sent: Friday, 24 July 2026 11:00:31 To: community/community ***@***.***> Cc: ZainAlabdin878 ***@***.***>; Mention ***@***.***> Subject: Re: [community/community] How can a GitHub Team organization purchase Copilot Business for 4 members when the Copilot settings are missing? (Discussion #202413) Hi @ZainAlabdin878<https://github.com/ZainAlabdin878> , if you see the original discussion, varadharajan has GitHub organization with GitHub Team plan and not a Github enterprise plan. Github has paused the Copilot enrollments for teams and Org-only plans — Reply to this email directly, view it on GitHub<#202413?email_source=notifications&email_token=AJA6574SIACEGBGVK3FTWXD5GMJR7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGYYTMNZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17761679>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJA6577BWPB7NELAFU3NBJT5GMJR7AVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBUGYYTINBZUF3AE>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AJA657YJV4R6G3M76AHDC335GMJR7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGYYTMNZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/AJA6575EK2GMXEGKCDTW74T5GMJR7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGYYTMNZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[ZainAlabdin878]

I am the owner and yes the organization is managed by an enterprise but the challenge is that I can neither enable copilot in the organization nor the enterprise so I'm stuck! Thank you

…

________________________________ From: Raph049 ***@***.***> Sent: Friday, July 24, 2026 3:36 PM To: community/community ***@***.***> Cc: ZainAlabdin878 ***@***.***>; Mention ***@***.***> Subject: Re: [community/community] How can a GitHub Team organization purchase Copilot Business for 4 members when the Copilot settings are missing? (Discussion #202413) It could be that You're not an organization owner or the organization is managed by an Enterprise that hasn't enabled Copilot. — Reply to this email directly, view it on GitHub<#202413?email_source=notifications&email_token=AJA657Y7GIN252FWDMQDOT35GNJ6FA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGY2TKNZSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17765572>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJA6573MLS7TJLDLVOD7RTL5GNJ6FAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBUGYYTINBZUF3AE>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AJA65753RFJ7FEXYDR2JAR35GNJ6FA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGY2TKNZSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/AJA65723VCVWZVVXBACZF7L5GNJ6FA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGY2TKNZSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>