GitHub Copilot Enterprise Managed Settings Can Now Set the Default Model
GitHub announced on September 2 that enterprise-managed settings can set the default GitHub Copilot model for new conversations. Per-team overrides are configured via team-mappings.json, generally available for Copilot Business and Enterprise.
GitHub announced on September 2, 2026 that enterprise-managed settings can now set the default GitHub Copilot model1.
- Organizations can set the default model used for new conversations1
- Enterprise teams can be assigned a different default model. Set the
modelkey as overridable and update team configuration files inteam-mappings.json. All other users inherit the enterprise default1 - Generally available with Copilot Business and Copilot Enterprise, covering the GitHub Copilot app, Copilot CLI, and Visual Studio Code1
This puts the question of which model each group uses in the organization’s hands. Copilot ships changes frequently — the August round of VS Code Copilot updates, which added external session handoff among other things, landed only days earlier. For organizations running Copilot across several departments, the choice between standardizing on a single default and varying it by the nature of each codebase is now something that can be expressed in configuration.
Sources
- Enterprise-managed settings support any default model - GitHub Changelog (September 2, 2026)
Was this article helpful?
Thank you!
Received. Thank you!