GitHub starts switching on Copilot features for admins who never chose

GitHub, part of Microsoft, began enforcing its global default policy for Copilot features on Business and Enterprise plans on October 22. According to the changelog entry, rollout runs through October 26, and any eligible feature an admin left unconfigured will now follow the chosen default.

One-time switch with explicit choices protected

GitHub announced the policy in September. The new post says the enforcement is gradual, so it may land at different times for different enterprises and organizations. The policy applies to eligible settings on the “Features & clients” page and to “MCP servers in Copilot.” Admins can review their setting under AI Controls, then Copilot, then “Default policy for new features.”

The default itself has three options: Enabled, Disabled, or Let organizations decide. Features still marked Unconfigured take whichever value the enterprise selected. GitHub describes this as a one-time change: later edits to the default will not rewrite feature policies that are already set.

Three protections remain in place, according to GitHub:

• If an admin has explicitly enabled or disabled a feature, the rollout leaves that setting alone.
• Preview features stay opt-in. If you opted into a preview that later becomes generally available, that choice is kept.
• A preview feature you never opted into falls under the default once it becomes eligible.

Admins can still make explicit choices for individual features at any time. The announcement does not list which features are eligible or which are exceptions; it points to GitHub’s documentation on default availability.

What the September notice added

The earlier September changelog fills in some detail that the new post leaves out. Besides the “Features & clients” page, the policy covers the Copilot Code Review setting on the “Agents” page. GitHub also gave admins a 28-day window to configure the policy before it took effect, during which users saw no change. That window has now closed.

The notice also explains what Disabled means in practice: features that are currently eligible stay unavailable, while future eligible features need administrator approval. The Enabled option makes current and future eligible features available by default. Neither post says which value was pre-selected for admins who never opened the setting, so an organization that ignored the September notice may not know what it received until it checks the page. The screenshot GitHub published shows the field set to Enabled alongside a banner about the gradual rollout, but that is one example, not a statement of the default for every account.

What to watch as the rollout finishes

This is the second default of its kind. A July 30 changelog set up a similar policy for models, taking effect August 26. Under it, generally available models without an explicit setting inherit the default. GitHub said at the time that open-weight models such as DeepSeek and Kimi K2.7, and models outside its data retention agreement such as Fable 5, are excluded from default enablement whatever the policy says. Whether the new feature policy has comparable carve-outs is exactly what the eligibility documentation would need to answer, and the announcement does not spell it out.

For administrators, the practical checks are simple. Open the default policy page and confirm which value is set. Look for features still labeled as inheriting the default, since those will track any future change to it only if GitHub’s wording holds, and the announcement says a later change will not alter policies already applied. Then compare the user-facing feature list with what the security or compliance team expected. Because the window runs only through October 26, any enterprise that wants a feature off needs to set it explicitly rather than rely on the default being changed afterward.

Adoption signals are also worth tracking. GitHub has been adding Copilot controls and reporting at a steady pace, including a dashboard that lets companies compare their Copilot agent use against industry peers. Default-on settings could raise the numbers such dashboards report, since features that users never had to request will reach more of them. Whether that reflects real use is not something GitHub’s posts address.

The source does not establish how many enterprises had left features unconfigured, how many users are affected, or whether GitHub will notify admins individually when the policy lands on their account. It also gives no per-plan breakdown beyond naming Copilot Business and Copilot Enterprise. Discussion is open in the GitHub Community forum.