GitHub Copilot can now lock customisations to approved plugins
A new enterprise setting blocks standalone Skills, custom agents, hooks, MCP servers and extensions, so Copilot customisations must come through a managed plugin instead.
GitHub added a new managed setting for Copilot on 16 November that lets enterprise admins restrict where agent customisations can come from. The setting, strictPluginOnlyCustomization, blocks standalone Skills, custom agents, hooks, MCP servers and executable Copilot extensions defined at the user or project level, so each of those must come through an approved plugin instead.
Admins can apply the restriction across all five categories or pick individual ones, and it is available on GitHub Enterprise Cloud for Copilot Business and Copilot Enterprise licence holders. GitHub is careful to say plugin-only does not mean enterprise-managed-only, and it is not a marketplace allowlist by itself: pairing it with the existing strictKnownMarketplaces setting is what actually limits which marketplaces those plugins can come from.
Why it matters: this closes a gap that recent incidents have made obvious. A user-defined Skill, hook or MCP server runs with real access the moment it loads, and this blog has already covered several cases of exactly that being abused, from poisoned AGENTS.md files to a backdoored Claude Code extension. An org that turns this setting on stops an individual developer from wiring in an unreviewed MCP server or hook, however well-meaning, and forces that customisation through something the organisation actually vetted.
The caveat: it only ships for Enterprise Cloud with a Business or Enterprise licence, so smaller teams and individual Copilot users have no equivalent control.