Daily · · Copilot · 🌶️🌶️Worth a lookMedium: worth a look Why: Settings change by Oct 26
Copilot’s default policy kicks in by Oct 26
Action needed: Copilot features you left unconfigured will follow your global default. GitHub began rolling out enforcement of the global default policy for Copilot Business and Copilot Enterprise on Oct 22, 2026, through Oct 26, so timing can differ by enterprise or organization.
Choices you made yourself stay as they are.
What changed
A Copilot feature you never touched could switch on, or off, in the next few days. GitHub announced the global default policy in September; now it is being enforced.
What changes
Once enforcement reaches you, eligible generally available features and capabilities left Unconfigured are set to your selected global default: Enabled, Disabled or Let organizations decide. It covers eligible settings on “Features & clients” and “MCP servers in Copilot”.
This is a one-time change: later edits to the default policy won’t change feature policies that are already set.
What stays the same
- If you enabled or disabled a feature yourself, the rollout leaves it alone.
- Preview features stay opt-in. If you opted into a preview that later becomes generally available, your choice is kept.
What to do
Check your setting under AI Controls → Copilot → Default policy for new features, and make an explicit choice for any feature you want handled differently from that default. GitHub’s documentation on default availability lists eligibility and exceptions.
Source: GitHub Changelog: global default for Copilot features, Oct 22, 2026