GitHub Enforces New Global Default Policy for Copilot Features
GitHub has implemented a global default policy for generally available Copilot features, allowing organizations to pre-configure enablement settings for users.
GitHub enforced a global default policy for generally available Copilot features on October 22. This rollout runs gradually through October 26 for Copilot Business and Copilot Enterprise plans.
If you left eligible features unconfigured, they now follow this new default. The policy covers supported client capabilities and settings under "Features & clients" and "MCP servers in Copilot." You can verify your current status in GitHub settings under AI Controls, Copilot, and Default policy for new features.
When the policy takes effect, unconfigured features shift to your chosen global default. Your options are Enabled, Disabled, or Let organizations decide. This happens only once, meaning if you change your default policy later, previously set feature policies remain untouched. You can still set any individual feature explicitly at any time. Existing explicit choices are preserved.
Preview features stay strictly opt-in. If your organization opted into a preview that later became generally available, that choice carries over. Otherwise, the default policy applies once the feature becomes eligible. GitHub filed the update in its changelog under enterprise management and tools.