GitHub Copilot Enterprise: Team-Specific Managed Settings

Enterprise administrators can now customize managed settings by targeting enterprise teams with itemized configuration files, allowing for scaled governance and team flexibility without central bottlenecks. This enables teams to adapt Copilot to their workflows while staying within defined boundaries.

Administrators can use the `"overridable": {}` syntax in `copilot/managed-settings.json` to allow teams to specialize configuration on a per-team basis, falling back to enterprise defaults if not explicitly set by the team.

New settings like `enabledPlugins` and `extraKnownMarketplaces` allow individual teams to layer on additional plugins and marketplaces beyond the enterprise baseline, fostering team-specific customization.

The `team-mappings.json` file allows mapping individual settings files to one or more team slugs, enabling the application of specific policies across multiple teams or specialized job roles.

When a user belongs to multiple teams, team-level settings are combined using the least restrictive value for each key, then applied beneath the enterprise file, ensuring user preferences are respected within defined limits.

Managed settings are currently enforced in VS Code, Copilot CLI, Copilot App, and Copilot cloud agent for users with Copilot Business or Enterprise licenses. Support is planned to extend across all Copilot clients via the Copilot SDK.