# GitHub — Control where GitHub Copilot customizations come from

- Company: GitHub (github.com)
- Announced: 2026-11-16T19:48:33+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://github.blog/changelog/2026-11-16-control-where-github-copilot-customizations-come-from
- Record: https://forck.live/items/37014-control-where-github-copilot-customizations-come-from
- Subject: Copilot

GitHub is letting enterprise administrators require that selected Copilot customizations come from plugins or managed settings instead of standalone user or project configuration. The strictPluginOnlyCustomization managed setting blocks standalone customizations from user and project sources, while eligible plugins and managed settings stay allowed subject to other policies. Administrators can apply the restriction to all five supported categories or pick individual ones: skills, custom agents, hooks, MCP servers, and executable Copilot extensions. GitHub notes that plugin-only does not mean enterprise-managed plugins only, and it is not a marketplace allowlist; it can be paired with strictKnownMarketplaces to restrict eligible marketplace sources. 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.

## Evidence

Verbatim from https://github.blog/changelog/2026-11-16-control-where-github-copilot-customizations-come-from:

> As an enterprise administrator, you can now require selected GitHub Copilot customizations to come from plugins or managed settings, rather than standalone user or project configuration. Combined with marketplace restrictions, this lets you distribute approved MCP tools and canvases through a shared plugin library without disabling those capabilities entirely.
> 
> The strictPluginOnlyCustomization managed setting blocks standalone customizations from user and project sources. Eligible plugins and managed settings remain allowed, subject to your other policies.
> 
> You can apply the restriction to all five supported categories or select individual ones: skills, custom agents, hooks, MCP servers, and executable Copilot extensions. For example, restrict MCP servers and extensions while leaving skills, agents, and hooks open. Extensions here include executable canvas providers, not VS Code Marketplace extensions.
> 
> Plugin-only does not mean enterprise-managed plugins only, and it isn’t a marketplace allowlist. Pair it with strictKnownMarketplaces to restrict eligible marketplace sources. Your existing managed settings can supply marketplace definitions and require or block specific plugins.

---

Record: https://forck.live/items/37014-control-where-github-copilot-customizations-come-from
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
