GitHub begins enforcing Copilot's global defaults for unconfigured features

The rollout applies selected enterprise defaults to eligible generally available capabilities while preserving explicit choices and preview opt-ins.

GitHub has started enforcing the global default policy for eligible Copilot features and supported client capabilities on Business and Enterprise plans. The company announced the start of the rollout on 22 October, with enforcement continuing through 26 October across organisations and enterprises.

The policy gives administrators a way to decide what happens when a generally available capability has no individual setting. Instead of treating each newly eligible feature as an isolated configuration task, an enterprise can select a common default and make exceptions where needed.

What happens to unconfigured settings

Eligible features left unconfigured are set according to the chosen default: enabled, disabled or delegated to organisations. The affected areas include “Features & clients” and “MCP servers in Copilot.”

GitHub describes this as a one-time change for the eligible settings. Once a feature has a policy value, changing the global default later does not rewrite that value. Administrators remain able to make explicit choices for individual features at any time.

That behaviour makes the default a starting rule rather than a continuous override. A company can establish a general approach while preserving a deliberate decision about a particular capability. An organisation that has disabled a feature does not lose that choice merely because the enterprise later changes its overall preference.

Existing decisions and previews

The rollout preserves explicit enabled or disabled settings. Preview features remain opt-in. If an organisation opted into a preview before it became generally available, that choice is retained; otherwise, the default applies when the capability becomes eligible.

For administrators, the distinction between a preview and a generally available feature becomes part of the rollout process. The first can require an active experiment decision, while the second can follow the enterprise's standard policy. A team's configuration record therefore needs to capture both the feature's stage and the policy value it receives.

GitHub places the control under AI Controls, then Copilot, then “Default policy for new features.” Because enforcement is gradual, the effective date can differ between organisations during the announced rollout window.

Managing a changing toolset

AI development environments now contain more than a single assistant. New clients, connectors and server integrations can change which tools are available to an agent. A default policy provides a common administrative baseline as that toolset expands.

The operational work is to connect the baseline with the organisation's actual adoption process. A central team may choose broad availability for established capabilities, delegate decisions to business units, or keep new eligible features disabled until a review is complete. The product supports those different approaches through the same policy surface.

The one-time nature of the change also means administrators should examine the resulting feature values rather than assume that the current global default describes every historical setting. A capability may have an explicit decision made before the rollout or a value assigned when it first became eligible.

This release makes that inheritance model more consequential: unconfigured features now receive a concrete policy value. The practical outcome is a more predictable starting point for Copilot administration, with individual feature decisions still available where the organisation needs them.

Sources

- [Global default for Copilot features generally available](https://github.blog/changelog/2026-10-22-global-default-for-copilot-features-generally-available/) — GitHub