Text of code.visualstudio.com › docs › enterprise › manage-ai-settings as Styx crawled it on Oct 10, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Manage AI settings in enterprise environments

AI agents: See llms.txt for documentation discovery and navigation. Documentation articles are also available as Markdown by appending .md to the article URL. 🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. Manage AI settings in enterprise environments View as Markdown Ask in VS Code Ask in VS Code Insiders Organizations can govern AI features in VS Code through three management solutions: Copilot enterprise-managed settings, VS Code device policies, and GitHub organization or enterprise settings.

These solutions control different layers of the AI experience. An organization might use all three, but should configure an overlapping control in only one system. Note If you're a developer and an agent, model, or tool is unavailable, first check the AI troubleshooting guidance . For an organization-managed restriction, ask your administrator which capabilities are approved. Understand the three management solutions Before you choose a solution, understand where each one is configured and what it controls.

Copilot enterprise-managed settings Use enterprise-managed settings for Copilot guardrails that should apply across supported clients, such as VS Code and Copilot CLI. Administrators define these settings with the GitHub-supported server-managed, MDM-managed, or file-based delivery methods. Even when you use an MDM solution, enterprise-managed settings use the Copilot configuration format and delivery path, not the VS Code device-policy namespace.

For server-managed deployments, administrators can override supported settings for specific enterprise teams. GitHub applies the matching values based on each person's enterprise team membership. See Override enterprise-managed settings for teams . Refer to the enterprise-managed settings setup guide and settings reference for supported keys, client coverage, configuration schemas, and precedence. VS Code device policies Use device policies for editor-specific controls on managed VS Code installations.

Administrators deploy these policies through platform management tools, such as Group Policy, Microsoft Intune, or macOS configuration profiles. The policies apply to the managed device and override the corresponding user settings in VS Code. Refer to the VS Code enterprise policy reference for policy names, accepted values, supported platforms, and minimum versions. GitHub organization and enterprise settings Use GitHub organization and enterprise settings for account-level and service-side controls, such as Copilot access, model availability, content exclusions, and organization-provided customizations.

Administrators configure these controls on GitHub. They follow the signed-in GitHub account and its organization or enterprise membership rather than the VS Code device-policy channel. Refer to Manage Copilot for your enterprise for configuration and reference information about these controls. Choose a management solution The solutions are not mutually exclusive. Choose the solution for each control based on the scope you need.

Requirement Management solution Configuration location Scope Apply consistent Copilot guardrails across supported clients. Copilot enterprise-managed settings GitHub-supported server, MDM, or file delivery Supported Copilot clients and keys Control a VS Code-specific editor feature on managed devices. VS Code device policies Operating system or device management Managed VS Code installations Control Copilot access or GitHub-hosted organization and enterprise behavior.

GitHub organization or enterprise settings GitHub organization or enterprise administration Signed-in accounts and GitHub-hosted services Some controls are available through more than one solution. Review the order of precedence before you combine them. Before a broad rollout, test the proposed configuration with a representative project, device, and account. Confirm that developers can complete approved tasks while the intended restrictions remain in place.

Understand precedence Across managed-settings delivery methods When the same managed setting is available from multiple sources, VS Code applies them in this order: MDM-managed settings. Server-managed settings. File-based settings. User settings. For most keys, the value from the highest-precedence source wins. Some keys, including permissions.deny , permissions.ask , and permissions.allow , combine restrictions from multiple sources in the most restrictive direction.

See Precedence of deployment methods for the complete and current rules. With VS Code device policies Some enterprise-managed settings map to a VS Code device policy. When an administrator configures both systems: If the systems configure different controls, both controls apply. If both systems configure the same control, the enterprise-managed setting takes precedence. The values are not merged. If enterprise-managed settings do not provide that control, the VS Code device policy remains in effect.

Configure an overlapping control through one management solution when possible. Run Developer: Policy Diagnostics to inspect the effective value and its source. Use Copilot enterprise-managed settings Configure and administer enterprise-managed settings by following the GitHub documentation: Get started with enterprise-managed settings explains delivery, configuration files, team overrides, validation, and troubleshooting.

Enterprise-managed settings reference lists supported keys, values, combination behavior, and client coverage. Not every enterprise-managed setting applies to every client. Before you configure a setting for VS Code, check the Supported clients column in the enterprise-managed settings reference . Verify applied managed settings Run Developer: Policy Diagnostics in VS Code to inspect effective policy values and their sources.

For more information, see Verify policy enforcement . If the diagnostics show a server-managed source with an unexpected value, check copilot/managed-settings.json , copilot/team-mappings.json , the mapped file under copilot/teams/ , and the user's enterprise team memberships. GitHub resolves team overrides before it delivers the server-managed settings to VS Code. For GitHub-side validation errors or delivery troubleshooting, follow Validate server-managed settings .

Meet minimum version requirements The managed-settings service can require a minimum VS Code version before AI features are available. When the installed version does not meet the requirement: Chat shows the required and installed versions and provides the appropriate update action. The editor window shows a banner even when Chat is closed. Other editor features remain available. The Agents window shows a blocking notice with an Open Editor Window action.

If built-in updates are disabled by policy, the notice directs the developer to contact an administrator. AI features become available after the installed version meets the requirement. Apply managed telemetry in VS Code Managed OpenTelemetry configuration applies to the Copilot Chat extension and Agent Host. The extension might offer Reload Window after a configuration change. VS Code restarts Agent Host automatically after it resolves a managed telemetry change.

Identity capture is off by default and independent of content capture. Review both controls before deployment, and remove conflicting OpenTelemetry environment variables from managed devices. For the configuration schema and supported clients, see telemetry in the enterprise-managed settings reference . Use VS Code device policies The following sections describe VS Code device policies. Deploy them by following Enterprise policies , and use the policy reference for accepted values and minimum versions.

Jump to: Control access and feature availability Configure models and data handling Govern agents and tools Configure security and observability Control access and feature availability Restrict AI features to

The rest of this page is on the live site.