GitHub adds plugin-only controls for Copilot customizations
Enterprise admins can now block standalone user and project configuration for skills, agents, hooks, MCP servers and executable extensions, while still allowing approved plugins.
GitHub Copilot plugin-only customizations arrive for enterprises
On November 16, 2026, GitHub added a control that lets enterprise administrators require selected GitHub Copilot plugin-only customizations to come from plugins or managed settings rather than standalone user or project configuration. Announced on the GitHub Changelog as an improvement, the change is aimed at organizations that want approved MCP tools and canvases handed out through a shared plugin library without turning those capabilities off altogether.
The setting and what it blocks
The control is a managed setting called strictPluginOnlyCustomization. Switched on, it blocks standalone customizations from user and project sources. Plugins and managed settings that qualify stay allowed, subject to whatever other policies the organization already runs.
Administrators can apply it to all five supported categories at once or pick them one by one: skills, custom agents, hooks, MCP servers and executable Copilot extensions. GitHub's own example is locking down MCP servers and extensions while leaving skills, agents and hooks open. One detail worth reading twice: in this context, extensions means executable canvas providers, not VS Code Marketplace extensions.
Pairing it with marketplace rules
GitHub is explicit that plugin-only does not mean enterprise-managed plugins only, and that the setting is not a marketplace allowlist. To narrow where plugins may come from, administrators pair it with strictKnownMarketplaces. Existing managed settings can also supply marketplace definitions and require or block specific plugins.
The two controls do different jobs. One decides whether standalone configuration is acceptable at all. The other decides which marketplaces count as eligible sources. Running only the first still leaves a fairly wide door open.
Who can use it
GitHub says the control is configurable on GitHub Enterprise Cloud, for members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or one of its organizations. The post points administrators to its documentation on managing plugin marketplaces and plugins with enterprise-managed settings for setup, and the full changelog entry is short enough to read in a minute.
What this likely means for developers
This suggests the practical effect lands on developers who keep personal MCP servers or project-level agent configuration: once a category is locked, that setup likely stops applying unless the same capability is packaged as a plugin or shipped through managed settings. A team that leans on a hand-rolled MCP server for internal tooling will probably need to turn it into an approved plugin rather than pointing each developer at their own config.
It also shifts work onto whoever curates the plugin library. The setting does not judge whether a plugin is any good. Approving sources is still a human decision, and an approved marketplace can contain more than an organization intends to permit.
Limits and open questions
The post leaves several things unstated. It does not say whether the restriction applies retroactively to customizations developers already have in place, whether administrators configure it through a UI or a managed settings file, or what a developer sees when a blocked customization fails to load. It also does not describe what makes a plugin eligible beyond the categories listed, and it mentions GitHub Enterprise Cloud only, so availability elsewhere is unclear.
What it means for building apps with AI
Most people building small apps with AI assistants will never touch these settings, since they belong to enterprise license administration. But the direction is worth noting: customization surfaces are becoming policy surfaces, and the agent configuration a developer assembles personally may not be the one an organization lets run.
If you build with an AI app builder and later move code into a company repository, this is the layer that governs what tooling travels with it. Draftship's paid plans include GitHub push, which is documented in GitHub and Vercel; once code lands in an enterprise org, plugin and marketplace rules like these may shape which Copilot customizations are available around it.
Primary sources
- Control where GitHub Copilot customizations come from · GitHub Changelog, Nov 16, 2026
This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.