On November 16, 2026, GitHub started letting GitHub Enterprise Cloud administrators require that certain Copilot customizations arrive through plugins or through settings managed by the enterprise. Standalone customizations, defined in a user's own configuration or in a project, stop loading in the categories the administrator restricts.
What the setting blocks
The key is called strictPluginOnlyCustomization and lives in the enterprise's managed settings. According to the announcement, it "blocks standalone customizations from user and project sources." Eligible plugins and managed settings remain allowed, as long as they comply with the account's other policies.
The restriction covers five categories, together or one at a time: skills, custom agents, hooks, MCP servers and executable Copilot extensions. Here, "extensions" means executable canvas providers, not VS Code Marketplace extensions. GitHub's own example restricts only MCP servers and extensions and leaves skills, agents and hooks open.
Requiring plugins also does not mean accepting only plugins published by the enterprise. The announcement says the setting is not a marketplace allowlist; to limit where plugins can come from, it has to be combined with strictKnownMarketplaces.
Who is affected
The control exists only on GitHub Enterprise Cloud and reaches members with a Copilot Business or Copilot Enterprise license issued by the enterprise or one of its organizations. Someone paying for Copilot Pro personally, even on a work computer, is outside the scope described.
The change matters to companies whose teams already configure MCP servers, hooks or skills on their own. In my reading, project configuration is the most sensitive category: a repository can ship the definition of an MCP server or a hook, and whoever clones the code ends up running that tool with the permissions of their own environment. GitHub presents the feature as a way to distribute approved MCP tools through a shared plugin library without disabling those capabilities: MCP and hooks stay in use, as long as they go through a channel the company reviews.
What to do, and by when
There is no deadline. The announcement describes a setting the administrator applies and does not mention automatic activation. Nothing changes for anyone who leaves the managed settings alone.
For those who want to use the control, the safe order is to first list what teams already use in user and repository configuration, package what is approved as a plugin and publish it in a marketplace the company controls. Then restrict marketplaces with strictKnownMarketplaces, and only after that turn on strictPluginOnlyCustomization, starting with the riskiest categories. Turning the restriction on before the plugin exists makes the tools teams rely on today stop loading.
This is the kind of control I discussed in Enterprise AI starts with controls around the model: deciding who distributes the tools an agent can call is a security decision, made outside the model.
What the announcement does not say
The post does not say which Copilot clients enforce the restriction (VS Code, CLI, cloud agent or the app), or from which version. It also does not say what developers see when a customization is blocked, whether the block shows up in the audit log, or whether something equivalent is coming to GitHub Enterprise Server. Before turning the key on across the company, test with a small group and confirm these points in the managed settings documentation.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.