Streamlining GitHub Copilot License Assignment in GitHub Enterprise Cloud

For GitHub Enterprise Cloud administrators, integrating new tools into an established environment can sometimes feel like navigating a maze. A common point of confusion arises when introducing new features like GitHub Copilot, especially if the initial enterprise setup predates these innovations.

Adding GitHub Copilot to Your Existing Enterprise Cloud

A recent discussion on the GitHub Community forum highlighted this very challenge. Rod-at-DOH, an enterprise admin, found himself tasked with assigning GitHub Copilot licenses to his organization's users. His GitHub Enterprise Cloud environment was configured years ago, long before the advent of modern AI tools like Copilot. Reading the "Getting started" and "Enterprise onboarding" documentation, Rod felt at a disadvantage, perceiving that Copilot configuration might only be straightforward during a fresh environment setup. He struggled to find clear guidance on how to assign licenses to GitHub Teams at the enterprise level within his already onboarded environment.

The Two-Layered Solution for Copilot Access

Fortunately, the community quickly provided clarity, confirming that re-configuring an entire GitHub Enterprise Cloud environment is absolutely not necessary to enable and assign Copilot licenses. The process involves a two-layered approach, leveraging both enterprise and organization-level settings.

Step 1: Enterprise-Level Enablement

The first crucial step is for an enterprise owner to enable Copilot access for the relevant organization(s) within the enterprise settings. This ensures that Copilot plans are active and available for assignment.

• Verify Enterprise Settings: In your enterprise settings, navigate to Copilot access and confirm that the organization is enabled for the correct Copilot plan.

Step 2: Organization-Level Assignment (or Enterprise-Level Direct Assignment)

Once Copilot is enabled at the enterprise level for the organization, there are two primary ways to assign seats:

Method A: Organization-Level Assignment

An organization owner can then assign seats to individuals or teams within that specific organization.

• Access Organization Settings: In the organization's settings, go to Copilot access.
• Grant Access: From here, you can grant access to all members, selected users, or selected teams.
• Verification: If you don't see the organization-level Copilot access page, double-check that you are an owner of that organization and that the enterprise has indeed enabled Copilot for it.

Method B: Enterprise-Level Direct Assignment (Recommended for Scale)

For enterprise owners, a more streamlined method exists to assign licenses directly, which is particularly useful for managing at scale and assigning to users who might not have a standard GitHub Enterprise license. This method bypasses the need for an organization owner to complete the assignment.

Here’s the recommended path:

1. Navigate to your enterprise: Go to your enterprise account page on GitHub.com.
2. Access Billing & Licensing: At the top of the page, click Billing and licensing, then click Licensing in the left sidebar.
3. Manage Copilot: Next to "Copilot", click Manage.
4. Assign to Teams/Users: Click the Enterprise Teams or All members tab.
5. Click Assign licenses.
6. Search for the specific GitHub Team or user and select them.
7. Click Add licenses.

Key Takeaway for Enterprise Admins

The core insight from this discussion is clear: adding GitHub Copilot licenses to an existing GitHub Enterprise Cloud environment is a straightforward process that does not require a complete re-configuration. By understanding the two-tiered management structure—enterprise-level enablement followed by organization-level or direct enterprise-level assignment—admins can efficiently roll out Copilot to their developer teams, enhancing developer productivity without unnecessary hurdles.