Lifestyle

GitHub Copilot adds strictPluginOnlyCustomization: enterprise admins can limit 5 types of customization to plugins or managed settings, for Copilot Business and Enterprise

GitHub announced that enterprise admins can now require Copilot skills, custom agents, hooks, MCP servers and executable extensions to come only from plugins or managed settings. The control applies to members with Copilot Business or Enterprise licenses on GitHub Enterprise Cloud.

News date: About 4 min read

Share on LINE
Contents
  1. 1. What does this setting change?
  2. 2. Which categories can be restricted?
  3. 3. Do you need to pair it with a marketplace policy?
  4. 4. FAQ

In a changelog post dated November 16, 2026, GitHub announced an "Improvement": enterprise admins can now require certain Copilot customizations to come from plugins or managed settings, rather than being configured individually at the personal or project level. The announcement does not mention a preview or waitlist. It applies to members with Copilot Business and Copilot Enterprise licenses on GitHub Enterprise Cloud. For enterprises that need to standardize where their AI tooling comes from, admins can control the origin of features such as MCP servers (services that let Copilot connect to external tools) without disabling them entirely.

What does this setting change?

"Managed settings" are settings that admins distribute centrally and members cannot change themselves. "Plugins" are packages that bundle several Copilot customizations for distribution. According to GitHub, the strictPluginOnlyCustomization managed setting blocks standalone customizations from user and project sources. Eligible plugins and managed settings are still allowed, but remain subject to other policies. GitHub says that, combined with marketplace restrictions, admins can distribute approved MCP tools and canvases through a shared plugin library instead of disabling those capabilities altogether.

Which categories can be restricted?

GitHub says the restriction can be applied to all five supported categories or to just some of them. The five categories are skills, custom agents, hooks (actions triggered automatically at specific moments), MCP servers, and executable Copilot extensions. As an example, GitHub says you can restrict only MCP servers and extensions while leaving skills, agents and hooks open. Extensions here include executable canvas providers; they are not VS Code Marketplace extensions.

Settings and scope, compiled from the GitHub Changelog
ItemGitHub's description
strictPluginOnlyCustomizationBlocks standalone customizations from user and project sources; plugins and managed settings are still allowed
strictKnownMarketplacesUsed together with it to restrict eligible marketplace sources
Restrictable categoriesSkills, custom agents, hooks, MCP servers, executable Copilot extensions (5 in total)
ScopeGitHub Enterprise Cloud; members with a Copilot Business or Copilot Enterprise license
Not includedVS Code Marketplace extensions; plugin-only does not mean enterprise-managed plugins only

Do you need to pair it with a marketplace policy?

GitHub explains that plugin-only does not mean only enterprise-managed plugins are allowed, and it is not a marketplace allowlist (a list that permits only specified sources). To restrict which marketplace sources can be used, pair it with strictKnownMarketplaces. Admins' existing managed settings can supply marketplace definitions and can also require or block specific plugins.

FAQ

Does this setting disable MCP?

According to GitHub, no. It blocks standalone configuration from user and project sources. Content provided through plugins or managed settings still works, and admins can distribute approved MCP tools through a shared plugin library.

Do I have to restrict all five categories?

No. GitHub says you can apply it to all of them or choose individual categories, for example restricting only MCP servers and extensions.

Does it affect VS Code Marketplace extensions?

GitHub explains that "extensions" here means executable Copilot extensions, including executable canvas providers, not VS Code Marketplace extensions.

Who can configure it?

GitHub says enterprise admins can configure it on GitHub Enterprise Cloud. It applies to members who hold a Copilot Business or Copilot Enterprise license assigned by the enterprise or its organizations.

Where can I find the setup steps?

GitHub directs admins to its documentation on managing plugin marketplaces and plugins with enterprise managed settings. The announcement itself does not give specific configuration commands.

Browse the latest news in this topic

Found this guide helpful? Share it with someone who needs it

Share on LINE

Sources

Compiled from the references and verification dates listed above; fares, schedules, product features, and terms can change, so please confirm the latest details on the relevant official website before travelling, booking, or purchasing.

Lifestyle