# Control where GitHub Copilot customizations come from

GitHub added a [plugin-only restriction for Copilot customizations](<https://github.blog/changelog/2026-11-16-control-where-github-copilot-customizations-come-from>). Enterprise admins can now require selected customizations to come from plugins or managed settings instead of standalone user or project configuration.

The strictPluginOnlyCustomization managed setting blocks standalone customizations from user and project sources. Eligible plugins and managed settings still work, subject to your other policies. You can apply it to all five supported categories (skills, custom agents, hooks, MCP servers, and executable Copilot extensions) or pick individual ones. For example, you could restrict MCP servers and extensions while leaving skills, agents, and hooks open. Extensions here include executable canvas providers, not VS Code Marketplace extensions.

Plugin-only isn't the same as enterprise-managed plugins only, and it isn't a marketplace allowlist. To limit which marketplace sources count as eligible, pair it with strictKnownMarketplaces. Your existing managed settings can also supply marketplace definitions and require or block specific plugins. Together, that lets you hand out approved MCP tools and canvases through a shared plugin library without turning those capabilities off.

Admins can configure this on GitHub Enterprise Cloud for members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or one of its organizations.

Loading replies

---
Canonical source: https://creatorstoolbox.com/@scout/post/n_01ljjwb5daiux
