GitHub Copilot 支持企业管理员管控自定义功能来源
Control where GitHub Copilot customizations come from
GitHub Copilot 面向 GitHub Enterprise Cloud 管理员上线自定义来源控制功能,支持强制要求指定自定义项来自插件或托管配置,阻止来自用户及项目单独配置的来源。
原文明确了企业级插件管控策略,管理员无需彻底禁用扩展即可集中规范 MCP 工具与智能体的接入来源。

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.
Choose which customizations require plugins
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.
Combine with your marketplace policies
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.
Enterprise administrators can configure these controls on GitHub Enterprise Cloud for members with Copilot Business or Copilot Enterprise licenses issued by the enterprise or one of its organizations.
See managing plugin marketplaces and plugins with enterprise-managed settings for administrator setup.
The post Control where GitHub Copilot customizations come from appeared first on The GitHub Blog.
来源:GitHub Changelog · github.blog