Manage Copilot and users via Enterprise Teams in public preview

[Akash1134]

🆕 GitHub Enterprise Cloud now offers Enterprise Teams in public preview, streamlining enterprise user and Copilot license management experiences for businesses.

Enterprise owners can now:

• Add users directly to the enterprise without requiring organization access. These unaffiliated users do not consume a license by default.
• Create and manage groups of users in the enterprise account through Enterprise Teams.
• Enterprise accounts with Enterprise Managed Users can synchronize groups of users from their identity provider to Enterprise Teams via SCIM.
• Manage Copilot Business licenses for individuals or entire enterprise teams through the enterprise-level Copilot licensing page.

---

What Enterprise Teams enable ❓

In the coming months, enterprise owners will also be able to use enterprise teams to:

• Assign an enterprise role.
• Assign it to a number of organizations within that enterprise, granting organization membership.
• Empower organization and repository owners to assign roles to teams within their scope.

Unaffiliated users (non-EMU enterprises) 👀

For enterprises that do not use enterprise-managed users (EMU), enterprise owners can now invite unaffiliated users to their enterprise. These users will not have access to organizations or licenses by default, but can later be assigned to an enterprise team, an organization, or Copilot Business license.

If a user is removed from all organizations, they will remain in the enterprise as an unaffiliated user unless the remove from enterprise action is taken. Since users may not be automatically removed from your enterprise, we recommend reviewing your offboarding process to ensure it accounts for this change.

Copilot Business licensing updates 💼

Along with enterprise teams and unaffiliated users now being available to all enterprises, updates have been made to Copilot Business licensing. Enterprise owners can use a dedicated Copilot Business licensing page to assign users and enterprise teams. These updates provide more flexible and scalable license management for enterprises, including the ability to assign Copilot Business to users without also requiring a GitHub Enterprise Cloud license.

Join us in the comments below to share your feedback and ask questions. 👇

Learn more

To learn more, check out our documentation on Enterprise Teams, unaffiliated users, and Copilot Business licensing. If you have feedback about these new features, join us on this discussion.

⚠️ Disclaimer: The UI for features in public preview is subject to change.

[gypsaiana-design]

Hi akash

[rodwill]

Problem: Issues when moving current Copilot Business users to the new Enterprise Teams solution

Context

My Enterprise currently consists of two separate organizations:

• Org A → dedicated only to users licensed under Copilot Business (this org contains only these users).
• Org B → our main organization, which contains all users. In this org, only some of the users have Copilot Enterprise licenses, provisioned via an IdP group.

Steps to Reproduce

1. Org A was used only to assign GitHub Copilot Business licenses.
2. With the new functionality, I created an Enterprise Team, linked it to the EMU/IdP group, and assigned Copilot Business licenses to that Enterprise Team.
3. I removed the license assignment from Org A.
4. At this point, all Copilot Business users lost access to Copilot.
5. I reverted the change: reassigned Copilot Business licenses back to Org A and removed the Enterprise Team.

Expected Behavior

• Users should retain their Copilot Business access when moving license assignment from Org A to the Enterprise Team.
• The license usage report should correctly reflect Business licenses, not Enterprise.

Actual Behavior

• Users lost access to Copilot after the change.
• After reverting, users regained access, but in the GitHub license information it now shows that they are consuming Enterprise licenses instead of Business.

Additional Notes

• The licenses were initially working fine under Org A.
• Org B (main org) already mixes users with and without Copilot Enterprise licenses via IdP group.
• The issue seems to be related to how license consumption is being reported when moving from an org-level assignment (Org A) to an Enterprise Team assignment.

[raymondtiu]

Hi @rodwill, I am part of the Product team for this launch. Do you mind if I reach out to you by email to help you troubleshoot? If so, I can reach out to the email registered in your GitHub account and continue the conversation.

[jmaixl]

We also had the same issue with moving from org-level assignment to Enterprise Team assignment.

1 organization had a "Copilot" team, backed by IdP. We assigned Copilot license to an Enterprise team for that same IdP team. Then disabling the organization's Copilot access resulted in users losing access. Reverting this restored access.

[raymondtiu]

@jmaixl we are looking into this issue. Note that sometimes it might take up to 15 mins for the Copilot license assignment to be completed for an enterprise team. If you remove the organization access before that, it might result in an access gap.

Do you also have this issue besides the access loss?

After reverting, users regained access, but in the GitHub license information it now shows that they are consuming Enterprise licenses instead of Business.

[adcloeshelle]

Is there a way to grant access to individual repos to these Enterprise teams? We would especially like this for Personal Repos - someone in the company creates a POC repo that we don't want in our main Organization, but we also want everyone on the team to easily have access to view it.