Article

Restrict GitHub Copilot to approved plugin sources

For teams managing Copilot, separate plugin-source rules from marketplace limits, check eligible plans and avoid disabling tools people need.

Editorial illustration for Restrict GitHub Copilot to approved plugin sources: code brackets represent developer tools. Not documentary evidence.

GitHub’s November 16, 2026 announcement gives enterprise administrators more control over where Copilot tools and other customizations come from. To restrict them to approved sources, combine limits on standalone customizations with a marketplace allowlist and separate plugin requirements. A plugin-only rule does not, by itself, limit plugins to sources your enterprise approves.

The practical choice is which existing tools to keep, which sources to exclude and which clients can enforce that decision. Source approval is separate from permission to run a command or access data.

Who can use these controls, and what do they cost?

GitHub explicitly names administrators on GitHub Enterprise Cloud and members whose Copilot Business or Enterprise licences come from that enterprise or its organizations. That is the scope of the source-control announcement; it is not a promise of equivalent administration for personally purchased plans.

As of November 17, GitHub lists Business at US$19 and Enterprise at US$39 per granted seat per month. For ten seats held for a full month, the illustrative seat-only calculation is 10 × $19 = $190 or 10 × $39 = $390. Extra AI usage, underlying GitHub licences, taxes and separately billed integrations are outside that calculation. Both named plans qualify; this control alone does not justify an Enterprise upgrade.

The plans page also lists a separate Copilot access billing option. The announcement does not expressly address it, so confirm feature-specific eligibility before choosing that option for this rollout.

For a Copilot-only enterprise without organizations, GitHub’s deployment guidance says server-managed delivery requires an organization, a governance repository and one user with a GitHub Enterprise licence. Device-management or file-based delivery offers alternatives without that repository setup.

Which customizations must come through plugins?

The strictPluginOnlyCustomization setting blocks selected standalone user and project customizations. GitHub says eligible plugins and managed settings remain permitted, subject to other policies. Its five supported categories are skills, custom agents, hooks, MCP servers and executable Copilot extensions. MCP connects assistants to external tools; extensions here include executable canvas providers, not extensions from the VS Code Marketplace.

Microsoft’s VS Code 1.146 release notes document two choices for Copilot-managed settings:

  • true restricts all five supported standalone categories.

  • An array selects categories: ["mcp", "extensions"] restricts those two while leaving skills, agents and hooks outside this particular restriction.

Choose the narrower option if the goal is to govern tool connections and executable extensions while preserving standalone skills and agents. Choose all categories only after identifying approved replacements for the personal and project customizations people rely on. These are rollout choices, not a guarantee that a plugin is safe.

Canvas coverage was already documented in VS Code 1.146, released November 11; the November 16 notice is not the first release of every underlying control. Microsoft also warns that the editor’s similarly named boolean ChatStrictPluginOnlyCustomization policy does not govern canvas extensions. Use the Copilot-managed setting for that purpose.

How do you restrict marketplace sources?

Adding a marketplace and excluding other marketplaces are different operations. GitHub’s marketplace guide uses extraKnownMarketplaces to distribute marketplace definitions. This makes a source available; it does not establish an allowlist.

Use strictKnownMarketplaces for the restriction. The settings reference says configuring it also disables built-in marketplaces. An empty array, [], means a complete marketplace lockdown, not “keep the defaults”. Include the sources needed for your approved tools before tightening this setting.

The resulting decision rule is straightforward: a customization needs an allowed route, its marketplace must satisfy source restrictions, and its plugin must not be blocked. A plugin package alone establishes none of those approvals. This is a reading of the documented controls, not a verified security boundary across every client.

Which plugins should be required or blocked?

Use enabledPlugins for individual requirements. GitHub documents identifiers in the form plugin-name@marketplace-name: true requires the plugin to be enabled; false requires it to be disabled. The marketplace name must match its manifest name.

Requiring two plugins does not mean every unlisted plugin is blocked. Keep this decision separate from marketplace eligibility. Enterprise-managed settings require or block plugins; optional project defaults belong in .github/copilot/settings.json and remain subordinate to managed policy.

What should you check before rollout?

Start with an inventory of the standalone customizations and marketplace plugins the team needs. Arrange approved replacements before blocking their current source, then check both policy delivery and access to the plugin files.

Those are different access paths. Server-managed policy can reach enterprise-licensed users who cannot read the governance repository. But private plugin files still require access to their hosting repository. A missing tool may therefore be a repository-access problem, not proof that the policy failed to arrive.

For server-managed delivery, GitHub’s setup guide places copilot/managed-settings.json on the default branch of the enterprise-designated .github-private repository. Merge changes into the existing policy. Review configuration issues under enterprise AI controls → Agents, then confirm the effective settings on clients. GitHub says supported clients normally refresh within about an hour; restarting or signing in again triggers a refresh.

Client coverage remains a qualification. As of November 17, the central managed-settings reference has no entry or client-support row for strictPluginOnlyCustomization. VS Code 1.146 documents it in Copilot harness sessions, but that does not establish a minimum version or equivalent behavior for every Copilot client and remote host. The harness is the software coordinating the model and tools; teams still using Local should also consult the VS Code Local-to-Copilot migration guide.

Before broad deployment, verify on each intended client that an approved tool still loads and a disallowed standalone customization does not. Do not treat a saved policy file as proof of enforcement.

Finally, retain separate rules for what loaded tools may do. GitHub configures local sandboxing separately in the CLI and Copilot app; choosing an approved source does not enable it. Review Copilot tool-approval controls alongside source policy. The rollout is complete only when the intended sources are restricted, needed tools remain usable and their execution permissions match the work.