A woman reviews a cybersecurity dashboard showing protected systems, approved integrations, and an AI coding assistant.
GitHub Copilot enterprise administrators can now control where selected customizations originate without switching off those capabilities altogether. The new strictPluginOnlyCustomization managed setting blocks standalone user- and project-sourced customizations in selected categories, while leaving eligible plugins and managed settings available, subject to other policies. GitHub announced the change on November 16.

A woman reviews a cybersecurity dashboard showing protected systems, approved integrations, and an AI coding assistant. What the new restriction covers​

Administrators can apply the policy across five categories or choose individual ones:

  • Skills
  • Custom agents
  • Hooks
  • MCP servers
  • Executable Copilot extensions

GitHub’s example restricts MCP servers and executable extensions while leaving the other three categories open under this rule. Crucially, “extensions” includes executable canvas providers—not VS Code Marketplace extensions. This is not a new enterprise switch for policing every editor add-on.

The controls cover GitHub Enterprise Cloud members whose Copilot Business or Copilot Enterprise licenses come from the enterprise or one of its organizations.

Plugin-only is not the same as approved-only​

Requiring a plugin does not automatically require an enterprise-managed plugin. GitHub explicitly distinguishes the new restriction from a marketplace allowlist and says to combine it with strictKnownMarketplaces to constrain marketplace sources. Packaging is one policy question; provenance is another.

GitHub’s administration documentation explains the surrounding controls:

SettingDocumented purpose
extraKnownMarketplacesMakes additional marketplaces available to enterprise members.
strictKnownMarketplacesRestricts marketplace installation to listed sources and disables built-in marketplaces.
enabledPluginsRequires particular plugins to be enabled or disabled.

These settings are administered through managed-settings.json, and managed settings take precedence over repository defaults and member preferences. GitHub identifies enterprise owners as the administrators for this workflow.

Two deployment details worth checking​

An approved marketplace still needs to be reachable. GitHub requires members to have read access to its repository, and the marketplace identifier in the configuration must match the name inside marketplace.json. For private marketplaces, GitHub advises hosting them in an organization their users belong to.

Specific plugin rules use PLUGIN-NAME@MARKETPLACE-NAME identifiers: true requires enablement; false requires disablement. GitHub recommends stable, kebab-case marketplace names because those names become part of plugin identifiers. Treat naming and repository permissions as deployment prerequisites, not housekeeping to finish afterward.

Keep the rollout claims precise​

The announcement does not specify minimum client versions or provide the new setting’s complete configuration syntax. It therefore does not establish identical enforcement behavior across every Copilot client.

The practical takeaway is a layered policy: control customization sources, constrain marketplaces, then require or block individual plugins. Together, those documented controls offer a more selective approach than simply disabling the underlying capabilities.

 

References

  1. Control where GitHub Copilot customizations come from GitHub Changelog 2026-11-16T19:48:33+00:00
  2. Managing plugin marketplaces and plugins with enterprise-managed settings - GitHub Docs docs.github.com