Playbooks · Teams
Require Copilot customizations to come from plugins
Written November 17, 2026
The strictPluginOnlyCustomization managed setting blocks standalone Copilot skills, agents, hooks, MCP servers and extensions. Set it per category.
An enterprise admin who wants Copilot customizations to come from an approved plugin library, rather than from files any user or project can drop in, gets a managed setting for that job in the GitHub Changelog post of November 16, 2026. The setting does not turn any capability off. Skills, custom agents, hooks, MCP servers and extensions all stay available. What changes is where they are allowed to come from: a plugin or a managed setting, instead of a standalone file in a user folder or a project. For an admin trying to share one approved set of tools across an enterprise, that distinction is the whole point.
One setting, five categories
The changelog post names the setting strictPluginOnlyCustomization. It blocks standalone customizations from user and project sources. Eligible plugins and managed settings remain allowed, subject to the admin's other policies, so turning the setting on does not freeze configuration in place. Admins can still push their own choices through managed settings, and a customization that arrives inside an eligible plugin still loads.
The restriction can cover all five categories at once, or individual ones:
- skills
- custom agents
- hooks
- MCP servers
- executable Copilot extensions
One point in the post is easy to misread. Extensions here include executable canvas providers. They are not VS Code Marketplace extensions, so a policy written for one kind does not describe the other.
The narrow version is the useful one
The example in the post restricts two categories and leaves three open: MCP servers and extensions must come from plugins, while skills, agents, and hooks stay as they are. That shape fits the common admin problem. MCP servers and executable extensions run code and reach outside tools, so they are the pieces an admin most wants to approve once and distribute. Skills and prompt-like files carry less risk, and forcing them through plugins on day one would break working setups for little gain.
Combined with marketplace restrictions, the post says, approved MCP tools and canvases can be distributed through a shared plugin library without disabling those capabilities entirely. The team keeps using MCP tools. It just gets them from the library the admin chose, in the version the admin approved.
Plugin-only is not an allowlist
Two limits in the post deserve a plain reading. Plugin-only does not mean enterprise-managed plugins only. A plugin from another source can still be eligible. And the setting is not a marketplace allowlist: on its own it says nothing about which marketplaces count.
An admin who also wants to control the sources pairs the setting with strictKnownMarketplaces, which restricts eligible marketplace sources. Existing managed settings can supply marketplace definitions and require or block specific plugins. So the two settings do different jobs. One decides the form a customization must arrive in. The other decides which shelves it can come from. An admin who sets only the first and expects the second has a gap, and the gap will not show until someone installs a plugin from a marketplace nobody looked at.
Who can set it, and what it does not cover
The controls are configurable on GitHub Enterprise Cloud for members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or one of its organizations, as the post puts it. That scope matters in an enterprise with mixed licensing: the setting governs the members whose licenses come from that enterprise.
This is a different control from model policy. Model policy decides which models people can pick. This setting decides where customizations can come from. The model side is covered in Copilot's model-policy API is GA at four levels.
A short way to roll it out
- Start with the two executable categories. Restrict MCP servers and extensions first, following the post's own example, and leave skills, agents, and hooks open until the plugin library carries what people need.
- Stock the library before you restrict. Approved MCP tools and canvases need to exist as plugins before standalone copies stop loading, or the first effect is breakage rather than control.
- Pair the settings if sources matter. Add
strictKnownMarketplaceswhen the marketplaces themselves need limits; the plugin-only setting alone does not supply them. - Keep managed settings for the enterprise's own choices. Managed settings remain allowed under the restriction, so central configuration does not need to travel as a plugin.
Related playbooks
- Copilot Agent Merge: watch a PR and fix its blockers
- The Copilot app now takes GHES accounts
- Copilot Automations learn from real outcomes
- Copilot CLI signs in with Microsoft Entra
Sources
- Control where GitHub Copilot customizations come from — GitHub Changelog — the strictPluginOnlyCustomization setting, the five categories, the per-category example, and the pairing with strictKnownMarketplaces.
Back to: Teams playbooks hub · Also: Copilot's model-policy API is GA at four levels