Enterprise-managed settings support any default model

What happened

GitHub has released a update to its enterprise administrative controls that allows organization administrators to set a preferred GitHub Copilot model as the default option for all new chat conversations. This configuration is managed directly through the enterprise-managed settings console, centralizing the model selection process. By establishing a primary model at the enterprise level, organizations can ensure that their development teams automatically start their interactions with the specific model that has been approved or selected for their workflow.

Back to changelog You can now set your preferred GitHub Copilot model as the default for new conversations through enterprise-managed settings. You can also customize the default by enterprise team, assigning a different default model based on team membership.

How it works

Set the model key as overridable and update team configuration files in team-mappings.json so that enterprise teams can choose their own preferred default model. Model defaults in managed settings are generally available with Copilot Business and Copilot Enterprise in the GitHub Copilot app, Copilot CLI, and Visual Studio Code.

Why it matters

Learn more in our docs about enterprise managed settings, or join the discussion in the GitHub Community. See the full write-up from GitHub Changelog via the source link for quotes and complete context.

Who is affected

Read the original coverage at GitHub Changelog via the source link above for the complete details and primary quotes.

What to watch next

Cross-check release notes and official docs before changing production systems based on early reporting.