How to block or disable GitHub Copilot for your organisation
Copilot now writes code, runs agent tasks in your repositories and calls MCP servers. Personal Copilot Free accounts can do much of the same outside your contract. Here is how to switch it off, or keep only the parts you approve.
Next step
AI Agent Blocklist: the other coding assistants, agents and MCP servers your developers reach for when Copilot is locked down
Extension IDs, package names, process names and domains, each with a risk grade, updated every day.
What "Copilot" covers today
Disabling Copilot used to mean turning off code completions. Today the name covers several surfaces, and each has its own switch. List what your developers use before you change anything.
| Surface | What it does | Where you control it |
|---|---|---|
| Copilot in the IDE | Completions, chat and agent mode in VS Code, Visual Studio, JetBrains IDEs, Xcode and Eclipse | Organisation policies, seats, IDE policies |
| Copilot CLI | An agent in the terminal that reads and changes code and runs commands | A Copilot CLI policy in organisation and enterprise settings |
| Copilot in GitHub | Chat on the website and in GitHub Mobile | Policies such as Copilot Chat in GitHub |
| Copilot cloud agent | Takes an issue, works in a cloud sandbox and opens a pull request | Organisation policies, repository settings, rulesets and firewall allowlists |
| MCP servers in Copilot | Extra tools and data sources for chat and agents | The MCP policy and registry settings under AI controls |
| Personal plans | Copilot Free or a paid personal plan, signed in with any GitHub account | Network routing, IDE policies, Visual Studio templates |
Where Copilot slips past your controls
Most surprises come from the gaps between these surfaces rather than from Copilot itself. These are the ones admins hit most often.
Personal accounts
A developer signs in to the IDE with a personal GitHub account and uses Copilot Free. Your policies, seats and data terms do not apply.
Agent mode
Agent mode in the IDE can edit many files and run terminal commands. Auto-approval settings decide whether a person checks each one.
MCP servers
Developers can add MCP servers to their editor. Each one brings tools and data access that nobody reviewed.
Cloud agent
The cloud agent writes to branches in your repositories. Branch protection decides whether its work can land unreviewed.
Exclusions are not walls
GitHub states that content exclusion is not a filesystem security boundary and may miss indirect access by agents.
Other assistants
Switch Copilot off and some developers install another AI extension or command-line agent the same afternoon.
Four levels of control, from light to total
Pick the level that matches your policy. Each level includes the ones above it.
Rein in features
Keep Copilot, but block suggestions matching public code, turn off agent mode or the CLI, and limit MCP servers to a registry.
Company accounts only
Allow your business or enterprise plan and block personal plans on the network and in Visual Studio.
Copilot off for the organisation
Remove seats, set policies to disabled at enterprise level, and block the extensions in your IDE policies.
No AI coding assistants at all
Do level 3 and block the other assistants and agents by extension ID, package, process and domain.
Organisation and enterprise policies, step by step
These steps use the paths in GitHub's documentation for organisation owners. GitHub renames sections from time to time, so check the current settings pages if a label differs.
- Open the Copilot settings. Go to your organisation, then Settings. In the sidebar under Code, planning, and automation, click Copilot.
- Review access. Decide who keeps a seat. Removing a member's seat stops their access through your organisation.
- Set feature policies. Under Policies, enable or disable features such as Copilot in the IDE, the CLI, chat on GitHub, the cloud agent and MCP servers in Copilot.
- Set models. Under Models, keep only the models your data terms cover.
- Block public code matches. Set Suggestions matching public code to Blocked.
- Enterprise owners: set the same policies at enterprise level. Where you choose a fixed value, organisations cannot loosen it; "Let organizations decide" hands the choice down.
Block GitHub Copilot Free and personal plans on your network
GitHub routes each Copilot plan through its own host names. That lets you allow your company plan and block personal plans at the firewall or secure web gateway.
Block
*.individual.githubcopilot.comPersonal plans, including Copilot Free and paid individual plans.
Allow for Business
*.business.githubcopilot.comIf your organisation uses Copilot Business.
Allow for Enterprise
*.enterprise.githubcopilot.comFor Copilot Enterprise or the access billing model. Allow both if you have both plans.
| Client | Minimum version for plan routing |
|---|---|
| Copilot Chat in VS Code | 0.17 or later |
| Copilot in JetBrains IDEs | 1.5.6.5692 or later |
| Visual Studio 2022 | 17.11 or later |
Disable Copilot in VS Code, Visual Studio and IntelliJ
IDE controls catch what account policies miss, especially personal sign-ins. Each IDE family has its own mechanism.
VS Code
- Users: turn on chat.disableAIFeatures to hide built-in AI features and disable the Copilot extensions.
- Fleet: AllowedExtensions policy to block the Copilot extensions, ChatAgentMode to switch off agent mode, ChatToolsAutoApprove and ChatToolsTerminalEnableAutoApprove to keep approvals on.
- Deploy with the VSCode ADMX on Windows, the sample profile on macOS, or /etc/vscode/policy.json on Linux.
Visual Studio
- Install the Visual Studio administrative templates.
- Open Computer Configuration > Administrative Templates > Visual Studio > Copilot Settings.
- 17.10 and later: disable Copilot for individual accounts or entirely. 17.13 and later: disable Copilot Free. 17.14.16 and later: Disable Agent Mode.
- Deploy with Intune or Group Policy, then restart Visual Studio.
JetBrains IDEs
- Users: Settings, then Plugins, find GitHub Copilot, then Disable or Uninstall.
- Fleet: remove seats, block personal plans on the network, and manage allowed plugins with your IDE management tooling.
- Older plugin versions do not support plan routing, so keep plugins current.
GitHub Copilot MCP server security and the registry allowlist
MCP servers extend Copilot with tools that can read data and take actions. GitHub gives admins a policy to turn them off and a registry allowlist to limit them.
In GitHub settings
- The MCP servers in Copilot policy switches MCP support on or off. Enterprise owners find it under AI controls, then MCP.
- Set an MCP registry URL for your approved servers.
- In Restrict MCP access to registry servers, choose Registry only. Only servers from the registry may run.
- Registry only cannot be saved without a valid registry URL. The feature is in public preview.
In the IDE
- VS Code enforcement of registry policies reached the stable release in public preview in November 2025.
- Visual Studio 2026 blocks connections to servers that are not on the allowlist and shows an error.
- VS Code also has device policies: ChatMCP, ChatAllowedMcpServers, ChatDeniedMcpServers and ChatAllowManagedMcpServersOnly.
- Check each IDE's current support before you rely on it.
Why GitHub Copilot blocks public code, and when you should
The public code filter is a licensing control, not a security one, but admins set it in the same place.
How it works
- With the policy set to Blocked, Copilot checks each suggestion, with about 150 characters of surrounding code, against public code on GitHub.
- Matches and near matches are hidden.
- With Allowed, users can see details of matching code and links to the source repositories.
- Seats assigned through your organisation inherit your setting.
Our advice
- Set it to Blocked at the highest level you control.
- Lock it at enterprise level so organisations cannot loosen it.
- Users also ask about Copilot's content filters for offensive language. Those shape what Copilot says, not what it can access, so they are not part of your security controls.
GitHub Copilot coding agent security
The cloud agent works in GitHub's infrastructure, so the controls live in your repositories and organisation, not on laptops.
| Risk | Control documented by GitHub | What to set |
|---|---|---|
| Agent reaches the internet freely | Cloud sandboxes honour repository and organisation firewall allowlists | Keep the allowlist short |
| Agent work lands without review | Rulesets and branch protection can stop it creating or updating pull requests | Required reviews on protected branches |
| Agent used on sensitive repositories | Repository owners and admins can disable Copilot for particular repositories | Off for repositories with regulated data |
| Agent writes insecure code | GitHub notes that output can contain vulnerabilities | Code scanning and human review on every pull request |
How to stop a GitHub Copilot subscription, and what that does not stop
Ending a subscription and ending use are different things. Free plans cost nothing, so they never show up in your bills.
| Situation | How to stop it | What still works afterwards |
|---|---|---|
| Seats paid by your organisation | Remove seats in the organisation's Copilot settings, or turn Copilot off at enterprise level | Personal plans the same people sign in with |
| A personal paid plan | The account owner cancels it in their GitHub billing settings; check GitHub's current billing pages | Copilot Free on the same account |
| Copilot Free | No subscription to cancel; block the personal plan hosts and use IDE policies | Unmanaged devices and networks you do not control |
| Other AI assistants | Block them by extension ID, package, process and domain | Nothing on managed devices, once the rules are in place |
Check that Copilot is really off
After the change, test from a developer's point of view. These checks take ten minutes on one managed laptop.
- Sign in with a personal account in VS Code and confirm Copilot cannot reach its personal plan hosts.
- Open Visual Studio and confirm the Copilot Settings policies show as applied after a restart.
- Try to install another AI extension and confirm the AllowedExtensions policy blocks it.
- Add an MCP server that is not in your registry and confirm it is refused in a supported IDE.
- Check network logs for remaining traffic to AI coding domains from developer subnets.
How the AI Agent Blocklist fits around Copilot
Many companies keep Copilot under their own plan and block everything else. Our files cover the "everything else" so a locked-down Copilot does not push developers to an unmanaged tool.
Other assistants in VS Code
- anthropic.claude-code Claude Code
- openai.chatgpt Codex
- saoudrizwan.claude-dev Cline
- kilocode.Kilo-Code Kilo Code
Four examples to set to false in AllowedExtensions. The file holds every coding agent extension we track.
What else the download covers
- Command-line agents by package and process name
- AI code editors by bundle ID and package ID
- MCP server packages and domains
- Coding agent domains for firewall and DNS
Keep Copilot on your terms and the rest off
The AI Agent Blocklist covers coding agents, AI editors, MCP servers, AI browsers and agent extensions, with a risk grade on every entry.
From $99 a month for one organisation. Download access is set up within one business day of your order.
- VS Code, Open VSX and JetBrains extension IDs of coding agents
- Package and process names for endpoint rules
- Domains in plain, hosts, PAC and firewall list formats
- CSV and JSON with all columns, updated every day
Ask us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
Questions about disabling Copilot
Can you disable GitHub Copilot for an organisation?
How do I block GitHub Copilot Free on the company network?
How do I disable GitHub Copilot in Visual Studio 2022?
How do I disable GitHub Copilot in VS Code?
How do I disable GitHub Copilot in IntelliJ?
Why does GitHub Copilot block suggestions matching public code?
Can I restrict which MCP servers GitHub Copilot uses?
Is Copilot content exclusion a security control?
GitHub, GitHub Copilot and GitHub Mobile are trademarks of GitHub, Inc. Visual Studio, VS Code, Intune and Windows are trademarks of Microsoft Corporation. IntelliJ and JetBrains are trademarks of JetBrains s.r.o.
Xcode is a trademark of Apple Inc. Eclipse is a trademark of the Eclipse Foundation. Claude Code is a trademark of Anthropic, PBC. Codex is a trademark of OpenAI. Cline, Kilo Code and Zscaler are trademarks of their respective owners.
macOS is a trademark of Apple Inc. Cursor is a trademark of Anysphere, Inc. Open VSX is a trademark of the Eclipse Foundation. Linux is a registered trademark of Linus Torvalds.
Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.