AI news for business · checked November 17, 2026

Since 16 November 2026, enterprise admins can require that skills, agents, hooks, MCP servers and extensions in GitHub Copilot come only from plugins or managed settings.

Anyone rolling out Copilot across an organization often faces the same problem: individuals or projects add their own MCP servers, skills or hooks, and nobody knows exactly which tools are in use. On 16 November 2026 GitHub announced a new control in its changelog. Enterprise admins can now require selected Copilot customizations to come only from plugins or managed settings. The facts come from the changelog entry and the GitHub documentation it links to; the checklist is our assessment.

LOL.MARKETING / CONNECTING INTELLIGENCE

The essential answer

The new managed setting is called strictPluginOnlyCustomization. It blocks standalone customizations from user and project sources; eligible plugins and managed settings remain allowed, subject to your other policies. Admins can apply the restriction to all five supported categories or pick individual ones: skills, custom agents, hooks, MCP servers and executable Copilot extensions. According to GitHub, “plugin-only” does not mean “enterprise-managed plugins only” and is not a marketplace allowlist. For that, you pair the setting with strictKnownMarketplaces. It can be configured on GitHub Enterprise Cloud for members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or one of its organizations.

01 / FIT

A good fit when

  • Enterprise owners and platform teams on GitHub Enterprise Cloud who want to distribute approved MCP tools, skills and agents centrally through a plugin library and end sprawl from individual configurations.

02 / LIMITS

Not the first choice when

  • Teams without GitHub Enterprise Cloud or on individual Copilot plans; according to the changelog the control applies only to members with Business or Enterprise licenses issued by the enterprise.

What GitHub introduced on 16 November 2026

GitHub labels the entry from 16 November 2026 as an improvement. At its core is a choice for enterprise admins: selected Copilot customizations can now be required to come only from plugins or managed settings, rather than from standalone user or project configuration. Combined with marketplace restrictions, organizations can distribute approved MCP tools and canvases through a shared plugin library without disabling those capabilities entirely.

That is the difference from a plain block that GitHub itself emphasizes: the capabilities stay usable, but the route into the environment runs through plugins that can be distributed, required or blocked centrally. For organizations that switched MCP servers off entirely to stay in control, this can be a way back to governed use; that is our assessment.

Which customizations are covered

The managed setting strictPluginOnlyCustomization blocks standalone customizations from user and project sources. It can be applied to all five supported categories or to individual ones: skills, custom agents, hooks, MCP servers and executable Copilot extensions. GitHub’s example is to restrict MCP servers and extensions while leaving skills, agents and hooks open.

The changelog adds an important clarification: extensions here include executable canvas providers, not VS Code Marketplace extensions. Restricting the “extensions” category therefore does not automatically control which editor extensions may be installed. That remains a separate matter of device and editor management.

Why “plugin-only” alone is not enough

GitHub states explicitly that plugin-only does not mean enterprise-managed plugins only, and it is not a marketplace allowlist. Without a further rule, plugins could therefore still come from other eligible marketplaces. To narrow the sources, you pair the setting with strictKnownMarketplaces. Existing managed settings can also supply marketplace definitions and require or block specific plugins.

The linked documentation describes the managed-settings.json file for this. extraKnownMarketplaces makes additional marketplaces available, such as a repository in your own organization; members need read access to that repository. strictKnownMarketplaces restricts installation to the listed sources and, according to the documentation, also disables the built-in marketplaces. enabledPlugins lets you require (true) or block (false) individual plugins. According to GitHub, managed settings always take precedence over repository defaults and member preferences.

Who can use the control

According to the changelog, enterprise admins configure this control on GitHub Enterprise Cloud. It applies to members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or one of its organizations. The documentation on marketplaces and plugins names enterprise owners as the role that can use it. For teams with different needs it points to team-mappings.json to require or block additional plugins for enterprise teams.

For monitoring, the documentation points to the usage metrics API. The totals_by_plugin array counts skill invocations associated with a plugin, not all plugin activity and not the number of people who installed it. Each of these arrays contains at most the five most active entries. GitHub itself warns against reading exact adoption from these counts.

Our checklist before switching it on

Before enabling strictPluginOnlyCustomization, you should know which skills, agents, hooks and MCP servers already run in projects and for individual people. Otherwise the restriction breaks workflows nobody documented. A step-by-step approach makes sense: first the categories with the highest risk, typically MCP servers and executable extensions, then the rest.

In parallel you need the plugin library that approved tools move into, and a clear rule on who reviews new plugins. If you really want to limit the sources, also set strictKnownMarketplaces and check that all required marketplaces are still reachable afterwards. This is our assessment, not a GitHub requirement.

For your organization’s AI policy the setting is a building block, not a replacement: it governs where customizations come from, not what an approved plugin may do. That review remains the job of the team that maintains the library.

Keep it verifiable

Primary sources

The next sensible step

Do you know which MCP servers your teams use in Copilot?

Eight steps from a general interest in AI to a clearer decision for your business.

Start AI System Check
FreeProvider-neutralNo credentials