GitHub is gradually implementing a global model policy for GitHub Copilot models. This policy applies to Copilot Business and Copilot Enterprise plans. The rollout of enforcement began on August 26 and will continue through September 1, affecting different enterprises at varying times.
Key Points
- A default model policy was announced in July for generally available GitHub Copilot models.
- Enforcement of this policy began on August 26 and will conclude by September 1.
- Unconfigured and new generally available models will inherit the global policy state.
- Administrators retain the ability to make specific decisions for individual models.
- Open-weight models and models requiring data retention are disabled by default.
- GitHub is evaluating a change to require explicit decisions for all policy states, potentially removing the "Delegate to default policy" option.
- Explicitly enabled or disabled models will retain their settings and are not altered by the new policy.
Context
According to GitHub, the global model policy aims to provide a structured approach to managing Copilot models within enterprise environments. The policy introduces four states for models in settings: "Enabled," "Disabled," "Delegate to enterprise teams/apps or organizations," and "Delegate to default policy." Models not previously configured will transition to "Delegate to default policy," aligning with the organization's default enablement setting.
Why It Matters
This policy change affects how administrators manage GitHub Copilot models within their organizations, requiring attention to default settings and explicit configuration choices. The gradual rollout means that the policy's effects will manifest at different times for various enterprises, necessitating awareness of the implementation timeline.
What To Do
- Note the September 1 enforcement completion date for the global model policy.
- Review the default model availability documentation for details on model states.
- Check current Copilot model configurations to understand how the new policy will affect them.
- Participate in the GitHub Community discussion regarding potential future policy changes, such as the removal of the "Delegate to default policy" state.
