On November 18, 2026, GitHub made team plugin defaults generally available for Copilot Business and Enterprise. Team maintainers and organization owners can select plugins in their organization team’s Customize Copilot tab for direct members using VS Code, the Copilot app or Copilot CLI.
Team defaults give direct members a shared starting point, not a compulsory configuration. Members can turn them off where policy permits; people who belong only through a child team do not inherit them.
A plugin packages reusable Copilot capabilities, such as task instructions and connections to external tools. A marketplace is the catalogue those plugins come from. Adding the catalogue does not enable everything inside it.
Add a marketplace, then select its plugins
Before choosing tools, check that each intended recipient is signed in to GitHub in their client and can read the marketplace’s repository. GitHub’s marketplace guide specifies both requirements; belonging to an organization does not automatically grant access to its private repositories. Also check each plugin’s supported clients, because some packaged components work only in particular clients.
Follow the documented team setup:
Open your organization team on github.com and select Customize Copilot.
Browse the built-in, enterprise or team-added marketplaces. If needed, add the GitHub repository that contains your marketplace.
Select the individual plugins to add to the team. Adding only their marketplace leaves this step unfinished.
Keep three states separate: available, installed and enabled. A marketplace makes a plugin discoverable; installation adds it to a client; enablement makes its components available in sessions. That distinction is useful when a colleague can find a tool but cannot use it.
Check the recipient’s client
Ask a direct member to inspect their plugin list before relying on the setup:
In VS Code, open Customize from the Chat side panel or Agents window, then select Plugins.
In the Copilot app, open Customize, then Installed.
In Copilot CLI, run
copilot plugin list.
Then try the capability you intend to share in a small, low-impact task. A plugin appearing in a list is not proof that an external service is connected or that every packaged component works in that client.
For a missing or unusable tool, check individual plugin selection, repository access, client compatibility and administrator policy separately. The team announcement does not specify a minimum client version or a synchronization interval, and it does not establish delivery to cloud agents or other IDEs.
If colleagues are also adopting the app for Azure repositories, the guide to setting up the Copilot app for Azure DevOps covers the separate account and repository connection. Plugin assignment does not replace that setup.
Decide whether you need defaults or requirements
Use team defaults when the configuration should follow a group of people. For tools tied to a particular project, GitHub documents repository defaults in .github/copilot/settings.json, with local overrides where supported. These are different scopes, not stronger and weaker versions of the same control.
For compulsory settings, enterprise-managed plugin policy can require a plugin or block it. Members cannot reverse those requirements. Separate enterprise-team managed settings also impose policy; they are not the optional organization-team defaults described here.
A team choice cannot override organization or enterprise restrictions. If the goal is to exclude unapproved sources or mandate particular tools, use the guide to restricting Copilot to approved plugin sources. Optional defaults cannot guarantee that every colleague keeps the same tools enabled.
What does a five-person team cost?
As of November 18, GitHub lists Copilot Business at US$19 and Enterprise at US$39 per granted seat per month. Both named plans qualify for team defaults, so this feature alone is not a reason to upgrade from Business to Enterprise.
Illustrative seat-only calculation: five seats held for a full month cost 5 × US$19 = US$95 on Business, or 5 × US$39 = US$195 on Enterprise. This assumes public list prices without proration or negotiated discounts. It excludes taxes, underlying GitHub platform charges, additional AI usage and any separately billed plugin services.
Each Business seat includes 1,900 monthly AI credits; Enterprise includes 3,900. GitHub pools those allowances at the billing-entity level, rather than reserving a separate balance for each teammate. Additional paid usage is enabled by default on both plans, so an administrator must disable AI credits paid usage if spending beyond the included pool is not wanted.
Selecting a plugin does not establish its connected service’s price, licence terms or usage limits. Check those with the chosen provider. A shared default is a configuration choice, not an unlimited-use entitlement.
Automating the setup through the API
The team-customization REST endpoints remain in public preview. Their PUT operation replaces the GitHub-managed configuration rather than applying a partial update. For automation, read the existing document, preserve unrelated settings in the replacement and review the result; that sequence is not a guarantee against concurrent edits.
Assignments use pluginAssignments with the state defaultEnabled; additional marketplaces are separate extraKnownMarketplaces entries. A 409 response means the team keeps its customizations in a repository. Investigate that existing configuration path instead of deleting it or forcing a replacement.
