What shipped? GitHub Copilot for JetBrains now supports enterprise managed settings — plugin governance, MCP server access controls, managed OpenTelemetry, and organization-controlled permission modes.
What changed? Administrators can centrally control four areas that previously required per-developer configuration:
- Plugin governance — enforce specific plugins as enabled or disabled, approve additional marketplace sources, or restrict installation to approved sources only.
- MCP server allowlist — use
allowedMcpServersanddeniedMcpServersto prevent connections to servers outside the enterprise's approved list. - Managed OpenTelemetry — configure collector endpoint, protocol, service name, and content-capture policy centrally. Managed values override developer settings.
- Permission modes — disable Bypass Approvals and Autopilot modes at the org level so developers can't opt out of approval flows.
Why does a builder care? If your org uses Copilot in JetBrains IDEs, these controls mean security policy is enforced at the admin level instead of relying on every developer to configure things correctly. The MCP server allowlist is particularly relevant as custom MCP servers become more common — one misconfigured server is a supply-chain vector, and this closes that door at the fleet level.