threatdeck
Live 13:45 UTC ·

GitHub Copilot managed settings

Enterprise managed settings for Copilot CLI, VS Code, the GitHub Copilot app, JetBrains and Copilot in the cloud. Pick a preset, adjust, copy. Every key links to GitHub's reference; nothing undocumented is generated.

Most organisations: secrets blocked, bypass mode off, sandbox on, short retention.
Secrets and credential files
doc
doc
doc
doc
doc
Shell commands
doc
doc
doc
doc
doc
Permission mode
doc
doc
doc
doc
Sandbox
doc
doc
doc
doc
doc
doc
doc
doc
MCP servers
doc

What each enabled control does

    For a pinned MCP allowlist with ThreatDeck advisory checks, use the MCP allowlist generator.

    Where to put the file

    • Server-managed (default for most enterprises): commit it as copilot/managed-settings.json in your enterprise's .github-private repository; clients pick it up within about an hour. Applies to users who get Copilot from your enterprise.
    • File-based: macOS /Library/Application Support/GitHubCopilot/managed-settings.json, Linux /etc/github-copilot/managed-settings.json, Windows %ProgramFiles%\GitHubCopilot\managed-settings.json. For Copilot CLI on macOS and Linux the file must be a regular root-owned file, not group- or world-writable, not a symlink.
    • MDM: the same keys as string values under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\GitHubCopilot (Windows) or forced preferences for com.github.copilot (macOS). Nested keys use dot-separated names; booleans, arrays and objects are stored as JSON text.
    • Precedence: MDM, then server-managed, then file-based, then user settings; sandbox and the permission rules combine in the most restrictive direction.

    Choosing how to deploy enterprise-managed settings · Getting started

    What this does not protect

    • Managed settings apply to local clients that support each key (Copilot CLI, VS Code, the Copilot app, JetBrains) and to Copilot in the cloud only for server-managed delivery; check the client support table before relying on a key. source
    • MCP allowlists do not apply to MCP servers defined in repository custom agent profiles; restrict the domains they need with the cloud agent firewall. source
    • Content exclusion (keeping files out of suggestions and chat) is configured in repository and organisation settings on GitHub, and GitHub states it is not a filesystem security boundary. source
    • In Copilot CLI, if server-managed settings cannot be fetched and nothing is cached, that policy is unavailable for the session: deliver must-have restrictions by MDM or file. source
    • On Windows the sandbox relies on programs honouring proxy settings, so network host rules are weaker there than on macOS and Linux. source

    Source (checked 2026-11-10): Enterprise managed settings reference.

    Following

    Follow the vendors, products, AI tools, techniques and actors you care about. Matching stories, CVEs and exploited bugs are marked, a Following tab appears in the feed, and returning visits show what changed. Saved only in this browser.

    Presets

    Get updates

    A personal RSS feed of new stories on everything you follow. Paste it into any feed reader, Slack or Teams RSS app.