GitHub Copilot enterprise admins can require customizations to come from plugins
GitHub says enterprise administrators can now require selected Copilot customizations to come from plugins or managed settings instead of standalone user or project configuration. The new strictPluginOnlyCustomization managed setting blocks standalone customizations from user and project sources, while eligible plugins and managed settings stay allowed under the other policies.
Categories. The restriction can cover all five supported categories or only some of them: skills, custom agents, hooks, MCP servers, and executable Copilot extensions (this includes executable canvas providers, not VS Code Marketplace extensions). GitHub's example restricts MCP servers and extensions while leaving skills, agents and hooks open.
With marketplace policies. GitHub says plugin-only does not mean enterprise-managed plugins only, and it is not a marketplace allowlist. Pairing it with strictKnownMarketplaces restricts the marketplace sources that count as eligible, and existing managed settings can supply marketplace definitions and require or block specific plugins. The aim, GitHub says, is to distribute approved MCP tools and canvases through a shared plugin library without turning those capabilities off.
The controls are available on GitHub Enterprise Cloud for members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or one of its organizations.
Sources
Get news like this as a push.
AI Tracker alerts you when something changes for the tools you use.