In September, we announced a global default policy for generally available GitHub Copilot features and supported client capabilities on Copilot Business and Copilot Enterprise plans. Starting today, we’re gradually rolling out enforcement of the policy through October 26, so it may take effect at different times for different enterprises and organizations. Eligible features left unconfigured will be set according to the global policy. Administrators can still make explicit choices for individual features at any time.

The policy applies to eligible settings on “Features & clients” and “MCP servers in Copilot”. You can review your setting under AI Controls → Copilot → Default policy for new features. For eligibility and exceptions, see the documentation on default availability.

What’s changing

Once the policy takes effect for your enterprise or organization:

Eligible generally available features and capabilities left Unconfigured will be set according to the selected global default of Enabled, Disabled, or Let organizations decide. This is a one-time change. Subsequent changes to the default policy won’t change feature policies that are already set.
Explicit choices are preserved. If you’ve enabled or disabled an individual feature, the rollout won’t change that setting.
Preview features remain opt-in. If you opted into a preview that later becomes generally available, your choice will be preserved. Otherwise, the default policy will apply when it becomes eligible.

Join the discussion within GitHub Community.

The post Global default for Copilot features generally available appeared first on The GitHub Blog.