GitHub is rolling out enforcement of its default model policy for generally available Copilot models on Business and Enterprise plans, effective gradually through September 1. Previously unconfigured and new GA models now inherit the org's global policy setting via a live 'Delegate to default policy' state, while explicit admin choices are preserved. Open-weight models (e.g., DeepSeek, Kimi K2) and models outside GitHub's data retention agreement (e.g., Fable 5) remain disabled by default regardless of policy. GitHub is also considering removing the delegate state in favor of requiring explicit choices for every model.
Questions this post answers
What happens to unconfigured GitHub Copilot models when the global model policy is enforced?
Unconfigured and new generally available Copilot models switch to a 'Delegate to default policy' state, meaning they automatically follow the organization's or enterprise's default enablement policy. If that policy is enabled, which is the default, those models become available to users. Explicit admin choices to enable or disable specific models are always preserved and unaffected. Admins tracking Copilot rollout changes like this can follow GitHub updates on daily.dev.
Which GitHub Copilot models are excluded from the default model policy enablement?
Open-weight models such as DeepSeek and Kimi K2, and models not covered by GitHub's data retention agreement such as Fable 5, are excluded from default enablement regardless of an organization's policy setting. These models remain disabled by default and require explicit admin action to enable. daily.dev helps developers stay current on which Copilot models require manual enablement.