International
The Morning Dev

Only the news worth knowing

‹
 

Release

Control where GitHub Copilot customizations come from

GitHub Changelog · By Allison ·

The Brief

  • GitHub now lets enterprise administrators require selected Copilot customizations to come from plugins or managed settings.
  • Standalone user or project configuration can be bypassed for those customizations.
  • The control works together with marketplace restrictions to distribute approved MCP tools.

Why it matters

Enterprise teams can restrict which Copilot customizations developers run, reducing the risk of unapproved tools being used in their codebases.

Who’s affected

  • Enterprise GitHub Copilot administrators

What to do

  1. Review which Copilot customizations are in use and decide which should be required to come from plugins or managed settings.
  2. Combine the new source requirement with marketplace restrictions to distribute approved MCP tools.

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…

Timeline

  1. GitHub announced the ability to control where Copilot customizations come from

  2. Archive: 2026 - GitHub Changelog

    Control where GitHub Copilot customizations come from

How do you feel about this?

0 Comments