GitHub Moves New Copilot Models to Default-On for Business and Enterprise
A new global policy will make eligible generally available models available automatically from August 26 unless administrators opt out.
GitHub announced on July 29 that generally available models will become enabled by default for Copilot Business and Copilot Enterprise. The new organization and enterprise policy is visible now, but it will not change user access until August 26. GitHub is giving administrators an opt-out rather than requiring them to approve every newly released model one by one.
What changed
For the next 28 days, administrators can configure the new default-availability policy without affecting which models their users can select. When the policy takes effect on August 26, models that an administrator has not explicitly configured will move from an unconfigured state to an inherits-default state.
If the global policy remains enabled, those inherited models will become available to users. If an organization disables the policy, inherited models will remain unavailable. GitHub says the inherited state is dynamic, so changing the global setting later will update every model that still follows the default.
What administrators keep
The change does not overwrite deliberate per-model decisions. A model that an administrator has explicitly enabled or disabled will keep that setting. That distinction matters for organizations that have already reviewed particular providers or model families and do not want a broad policy switch to reverse those choices.
GitHub also carved out two categories from automatic enablement. Open-weight models, including DeepSeek and Kimi K2.7 in the GitHub examples, remain excluded. Models that are not covered by the GitHub data-retention agreement, with Fable 5 given as an example, are also excluded regardless of the global policy.
Why it matters
The policy changes the default governance burden for larger GitHub Copilot customers. Instead of treating every generally available model as a separate approval event, organizations that accept the GitHub default can let new eligible models flow into the model picker automatically. Organizations with stricter review requirements must make an active policy choice before August 26 to preserve manual approval.
The announcement does not identify which future models will first enter through the new default. It defines the control path and its exceptions, rather than promising a particular model release. Administrators should therefore review both the global setting and any explicit per-model decisions before the effective date.
Status
Confirmed. GitHub announced the policy in its official changelog. Internal confidence is medium because the operational details come from one first-party source and have not been independently corroborated.
Sources
Update note: Last reviewed 2026-07-29. We will revise this post if GitHub changes the effective date, exclusions, or administrator controls.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.