Copilot admins can now bar MCP servers and skills that don’t come from plugins
A new managed setting lets enterprise administrators require five kinds of Copilot customization to arrive through plugins or managed settings, not user or project files.

GitHub, owned by Microsoft, has given enterprise administrators a way to require Copilot customizations to come from plugins or managed settings. A new setting, strictPluginOnlyCustomization, blocks standalone configuration from user and project sources.
Five categories, switched on one by one
The restriction covers five kinds of customization: skills, custom agents, hooks, MCP servers and executable Copilot extensions. An administrator can apply it to all five or pick only some. GitHub’s own example restricts MCP servers and extensions while leaving skills, agents and hooks open.

The word “extensions” is narrower than it sounds. According to GitHub, it refers to executable canvas providers, not VS Code Marketplace extensions, so the setting does not govern the editor’s general extension ecosystem.
Plugins and managed settings that meet the administrator’s other policies stay allowed. GitHub says the aim is to distribute approved MCP tools and canvases through a shared plugin library without turning those capabilities off entirely.

A plugin-only rule is not a marketplace allowlist
GitHub is explicit about what the setting does not do. In its words, plugin-only does not mean enterprise-managed plugins only, and it is not a marketplace allowlist. A plugin from any marketplace the policy still permits would qualify.
To narrow that, administrators pair it with a second setting, strictKnownMarketplaces, which restricts the marketplace sources that count as eligible. Existing managed settings can also supply marketplace definitions and require or block specific plugins. Together, the controls work in layers: where a customization may come from, which marketplaces are trusted, and which individual plugins are required or banned.
Who can use it today
The controls are for enterprise administrators on GitHub Enterprise Cloud. They apply to members holding Copilot Business or Copilot Enterprise licenses, whether issued by the enterprise itself or by one of its organizations. GitHub points administrators to its documentation on managing plugin marketplaces and plugins with enterprise-managed settings for setup. Individual Copilot plans are not mentioned.
For teams, the practical change is that a developer can no longer wire up an MCP server or drop a hooks file into a repository and have Copilot run it, if the administrator has restricted that category. Before this, the choice was largely binary for some capabilities: allow them everywhere or disable them.
What to watch as agent surfaces multiply
The setting arrives during a busy week of administrative changes in Copilot. On the same day GitHub retired Claude Opus 4.8, Opus 5 and GPT-5.6 Terra from the model picker, according to our earlier report. Administrators are also managing model-level policies: in GitHub’s weekly release notes, Claude Fable 5.2 requires a data-retention policy that is off by default, and Copilot Business and Enterprise administrators must switch it on.
Read together, these show that enterprise Copilot control is spreading across models, data retention and now the tooling that agents can call. MCP servers and hooks matter most here, since they can reach outside systems or run code, which is why a security team may want them to pass through a reviewed library. GitHub’s changelog does not describe any incident behind the change.
Several things remain unestablished by the announcement. It gives no date for availability beyond the post itself, and it does not say how the setting is reported to developers whose customizations are blocked, or whether audit logs record blocked attempts. It also does not say how enforcement works for Copilot clients that read these settings differently. Adoption signals to look for include GitHub’s documentation updates and any extension of the policy to additional customization types. The company’s statements here are its own description and have not been independently verified.
For now, the feature is a governance tool rather than a security guarantee: it decides where customizations may originate, and it relies on administrators to curate the plugins and marketplaces that remain.
Sign Up for the Daily AI Pulse
One email a day. All the stories that matter.
By signing up, you agree to our Terms of Use and acknowledge the data practices in our Privacy Policy. You may unsubscribe at any time.
Leo MartinsAI Tools, Prompts & Practical AI ExpertLeo Martins is the AI Tools & Practical AI Expert at Aiholics, focused on helping readers use artificial intelligence to improve productivity, creativity and everyday work.
You may also like

Copilot seat management can now run from a GitHub App, not a person’s token

Copilot code review can now be switched on or off by API, from enterprise down to repo

Copilot’s dashboard now counts chat users, and “passive” becomes “chat-first”
