# Control where GitHub Copilot customizations come from

Source: [Archive: 2026 - GitHub Changelog](https://github.blog/changelog/2026-11-16-control-where-github-copilot-customizations-come-from) · 2026-11-16 · Cloud & DevOps
Page: https://themorning.dev/story/control-where-github-copilot-customizations-come-from-4b8c3044ce82856f
Kind: release · Impact: medium

## In 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.

## What to do

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

## Timeline

- 2026-11-16: GitHub announced the ability to control where Copilot customizations come from

## Coverage

- [Control where GitHub Copilot customizations come from](https://github.blog/changelog/2026-11-16-control-where-github-copilot-customizations-come-from) — Archive: 2026 - GitHub Changelog, 2026-11-16

Tags: github, copilot, enterprise, administration, mcp, security-policy

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
