GitHub rolls out Copilot global-default policy enforcement through October 26
GitHub began enforcing its global default policy for eligible generally available Copilot features on October 22. The company says the rollout continues through October 26, so the change can reach enterprises and organizations at different times. It applies to Copilot Business and Copilot Enterprise plans.
The policy covers eligible settings on the Features & clients and MCP servers in Copilot pages. Administrators can review the selected default under AI Controls, Copilot, and Default policy for new features. The announcement does not say every Copilot setting is eligible.
When enforcement reaches an enterprise or organization, eligible features left Unconfigured receive the selected global default. GitHub lists Enabled, Disabled and Let organizations decide as the available policy choices. This is a one-time change for those unconfigured settings.
Explicit feature choices are preserved. If an administrator has already enabled or disabled an individual feature, the rollout does not change that setting. Changing the global default later also does not rewrite feature policies that have already been set.
Preview features remain opt-in. A prior decision to opt into a preview is preserved when that feature becomes generally available. Otherwise, the global default applies when the feature becomes eligible. That distinction prevents the rollout from being read as blanket automatic access to every preview.
For teams reviewing Copilot access, the practical check is their selected global policy and any explicit feature-level decisions. Administrators can still make individual choices at any time. The announcement describes policy enforcement, not a change to subscription prices or proof that a particular organization has already completed the rollout.