GitHub Copilot default policy starts applying to unconfigured features through October 26

GitHub is rolling out enforcement of its global default policy for eligible Copilot features through October 26. The change applies to Copilot Business and Copilot Enterprise: generally available features and supported client capabilities that remain unconfigured will take the organization’s or enterprise’s selected default. GitHub announced the enforcement window on October 22, following its September announcement of the policy. [The official changelog describes the rollout](https://github.blog/changelog/2026‑10‑22‑global‑default‑for‑copilot‑features‑generally‑available). The practical distinction is between leaving a setting unconfigured and making an explicit choice. A feature without an individual decision can inherit the global default when enforcement reaches that enterprise or organization. A feature an administrator has already enabled or disabled keeps that setting. GitHub says rollout timing varies, so the announcement alone does not establish that a particular tenant has already changed.

Administrators can find the global setting at `AI Controls → Copilot → Default policy for new features`. The possible defaults are `Enabled`, `Disabled` and `Let organizations decide`. GitHub says the policy covers eligible settings under `Features & clients` and `MCP servers in Copilot`; its [default‑availability documentation](https://docs.github.com/copilot/concepts/enterprise/default‑availability) is the reference for detailed eligibility and exceptions. [The release identifies these controls](https://github.blog/changelog/2026‑10‑22‑global‑default‑for‑copilot‑features‑generally‑available). A useful review therefore has two parts: inspect the selected default, then identify eligible individual settings still marked `Unconfigured`. For example, a default of `Enabled` and a default of `Disabled` lead to different outcomes for an eligible unconfigured capability. Neither overrides a feature that already has an explicit enabled or disabled choice. Administrators can still make those individual choices at any time.

The rollout is a one‑time application of the default to the eligible unconfigured settings. GitHub explicitly says that later changes to the default policy will not change feature policies that are already set. [That behavior is documented in the October 22 notice](https://github.blog/changelog/2026‑10‑22‑global‑default‑for‑copilot‑features‑generally‑available). That limits what a later global edit can accomplish. An administrator reviewing access after the rollout should inspect the individual policy values rather than assume that changing the global default will reverse earlier settings. The default remains a way to handle eligibility and unconfigured capabilities; it is not a substitute for checking the effective choices on features the organization already configured. OpenTools has not tested enforcement in a customer tenant.

Preview features remain opt‑in. If an organization opted into a preview and it subsequently becomes generally available, GitHub says that choice is preserved. Otherwise, the default applies when the feature becomes eligible. The release therefore does not support a claim that every Copilot preview is being switched on, or that every feature becomes available to every organization at the same moment. [GitHub sets out the preview exception here](https://github.blog/changelog/2026‑10‑22‑global‑default‑for‑copilot‑features‑generally‑available). The immediate reader task is to review eligible unconfigured capabilities during the announced rollout, particularly where a global default can affect client or MCP settings. That differs from the [Copilot model‑policy API covered earlier by OpenTools](https://opentools.ai/news/github‑copilot‑model‑policy‑api‑enterprise‑controls), which concerns managing model choices through an API. This release concerns how default feature policy is applied; it does not announce a new model‑policy endpoint or demonstrate how an organization’s existing controls behave in practice.