On November 16, 2026, GitHub announced a new enterprise governance control allowing administrators to dictate where GitHub Copilot customizations originate, enabling organizations to distribute approved tools without turning off customization features altogether.
How strictPluginOnlyCustomization Works Across Five Categories
Blocking Standalone User & Project Customizations: The strictPluginOnlyCustomization managed setting blocks standalone customizations defined in user or project sources while allowing eligible plugins and managed settings to remain active subject to other enterprise policies.
Five Configurable Categories (Excluding VS Code Marketplace): Administrators can apply the rule to all or a subset of five categories: skills, custom agents, hooks, MCP servers, and executable Copilot extensions—for instance, restricting MCP servers and extensions while leaving skills, agents, and hooks open. GitHub notes that extensions here include executable canvas providers and do not refer to VS Code Marketplace extensions.
Pairing with strictKnownMarketplaces & Eligibility
Combining Source Control with Marketplace Allowlists: GitHub clarifies that plugin-only enforcement does not mean enterprise-managed plugins only and does not act as a marketplace allowlist by itself. Administrators can pair strictPluginOnlyCustomization with strictKnownMarketplaces (which restricts plugin installation to explicitly listed marketplaces and disables built-in marketplaces per GitHub's managed settings documentation) to distribute approved MCP tools and canvases through a shared plugin library. These controls apply on GitHub Enterprise Cloud for members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or its organizations.
