Skip to content
important Productivity

GitHub introduces the strictPluginOnlyCustomization setting to restrict customization sources in GitHub Copilot

clearly official source

The company GitHub has added the managed setting strictPluginOnlyCustomization, with which enterprise administrators can restrict the sources of Copilot customizations to only plugins and managed settings, for skills, agents, hooks, MCP servers, and extensions.

The company GitHub has introduced a new managed setting called strictPluginOnlyCustomization for the GitHub Copilot product. Enterprise-level administrators can use it to require that selected Copilot customizations come only from plugins or managed settings, not from standalone configurations of individual users or projects.

The setting can be applied to all five supported categories of customizations - skills, custom agents, hooks, MCP servers, and executable extensions (this refers to canvas providers, not the VS Code Marketplace) - or only to selected ones. For example, an administrator can restrict the sources of MCP servers and extensions while leaving skills, agents, and hooks open. According to the company GitHub, plugin-only does not automatically mean only enterprise-managed plugins, nor is it a marketplace allowlist; the setting can be combined with the additional parameter strictKnownMarketplaces, which narrows the range of allowed marketplace sources, and with existing managed settings that define marketplace definitions and require or block specific plugins.

The feature is available to administrators on GitHub Enterprise Cloud for members with a Copilot Business or Copilot Enterprise license issued by the enterprise or one of its organizations.

What changed

Why it matters

Companies deploying Copilot across the organization have so far found it difficult to control where add-ons such as MCP servers or custom agents come from - individual developers could add them themselves from any source. The new setting gives administrators a tool to reduce this risk without having to disable the entire given type of customization.

Two audiences, two different impacts

What this means

01

For individuals

Developers at enterprises that enable this setting will no longer be able to freely add custom MCP servers, skills, or agents outside of approved plugins and marketplaces designated by the administrator.

What to do Check with your GitHub Enterprise administrator whether and how company policy restricts the sources of custom Copilot customizations.
More practical updates →
02

For a business

Administrators of GitHub Enterprise Cloud gain a tool for enforcing governance over the sources of Copilot customizations (MCP servers, plugins, agents), which can reduce the risk of deploying unapproved or unvetted extensions.

Risks and compliance
What to decide Consider introducing strictPluginOnlyCustomization in conjunction with strictKnownMarketplaces to restrict the sources of MCP servers and other Copilot customizations to approved plugins.
More business impacts →
security enterprise governance GitHub Copilot GitHub Enterprise managed settings MCP servers

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

1
GitHub Copilot Changelog primary source · first detected Control where GitHub Copilot customizations come from