Copilot starts applying defaults to unconfigured team features

A blank setting can stop being a neutral choice. GitHub has started applying the selected global default to eligible Copilot features that a team has left unconfigured. The October 22 announcement describes a gradual rollout through October 26 for Copilot Business and Enterprise. Rollout notice.

For a small agency, the practical question is whether an unconfigured capability should follow the organisation’s general policy or receive an explicit decision. GitHub says existing enable and disable choices are preserved. Preview features remain opt-in.

Review the blank entries, then record the exceptions

The release points administrators to AI Controls → Copilot → Default policy for new features, with eligible settings on Features & clients and MCP servers in Copilot. The selected default can enable, disable or delegate decisions to organisations, subject to the applicable policy scope.

Consider an illustrative team that explicitly disabled one sensitive integration but left a different, eligible feature unconfigured. The explicit choice stays in place; the unconfigured entry follows the selected default as enforcement reaches that account. Record which exceptions are deliberate, and inspect actual settings before telling the team what is available. This is a proposed review, not an audit of a real organisation.

GitHub describes the backfill as a one-time change: changing the default later does not rewrite feature policies that are already set. That makes an explicit record more useful than relying on memory of the original default.

Features and models have separate defaults

The default-availability documentation distinguishes feature and model policies and lists eligibility exceptions. It still contains wording that the feature policy is not yet active, alongside its October 22 start date. The newer dated announcement supplies the rollout window; it does not establish that every account has already changed.

Administrators should review unconfigured entries during that window and recheck actual state by its end. Individual creators on personal plans do not need to perform this enterprise review. For a separate view of model access and inheritance, read our Copilot model-policy API coverage.