AI Tool Profile
strictKnownMarketplaces: Copilot Plugin Governance, Limits, and QA
The strictKnownMarketplaces enterprise-managed setting restricts plugin installation in supported GitHub Copilot clients to explicitly configured marketplace source objects; an empty array locks installation down.

Verification & Sources
- Status
- Verified
- Source links
- 5
- Freshness
- Verified July 28, 2026
- Last verified
- July 28, 2026
- Last updated
- July 28, 2026
Key source checks
Suggest a correction
What It Does
The strictKnownMarketplaces enterprise-managed setting restricts plugin installation in supported GitHub Copilot clients to explicitly configured marketplace source objects; an empty array locks installation down.
Full Guide
Kingy verdict: strictKnownMarketplaces is a narrow but valuable enterprise control: it limits plugin installation in supported Copilot clients to explicitly configured marketplaces. It is not package verification, malware scanning or a guarantee that every allowed plugin is safe. Its value depends on precise source definitions, managed-setting delivery and a tested emergency-change process.
What the setting controls
GitHub announced public-preview support for Visual Studio Code and GitHub Copilot CLI on June 25, 2026. Administrators add strictKnownMarketplaces to enterprise-managed settings. Supported clients then restrict plugin installation to marketplaces that match the configured source objects. GitHub’s current reference says an empty array means complete lockdown.
The reference documents source types including GitHub repositories, Git URLs, URLs, npm packages, files, directories, host patterns and path patterns. Broad URL, host or path patterns can weaken the intended boundary. Treat every pattern as code: review it, test positive and negative cases and record who approved it.
Precedence and deployment
GitHub documents managed-setting precedence from MDM-managed settings to server-managed settings, file-based settings and then user-level settings. The CLI reference lists platform-specific managed locations and rejects unsafe file-based configurations in some POSIX cases. A policy written correctly but delivered to the wrong location is not an enforced control.
extraKnownMarketplaces adds sources, while strictKnownMarketplaces limits installation to the known set. enabledPlugins can require or block specific plugin keys. Test these controls together because a marketplace restriction alone does not express which plugin versions or capabilities should be enabled.
Source identity and lifecycle risk
A GitHub repository entry is more specific than a host pattern, but even a specific repository can change owners, default branches and contents. URL and path patterns create additional ambiguity around redirects, encoding and nested paths. Define the narrowest practical source, prefer immutable revisions where the plugin system supports them and monitor changes to every approved marketplace. The review record should connect a business owner, source definition, permitted clients, expected plugins and expiry date so a temporary exception does not become permanent infrastructure.
What it does not prove
An approved marketplace can later change, a repository can transfer ownership, a tag can move and a package can add risky behavior. Source restriction should sit alongside pinned revisions where available, change review, plugin permission analysis, provenance checks, network controls and runtime monitoring. Empty-list lockdown also needs a tested recovery path so administrators do not bypass governance during an incident.
The feature is enterprise management, not a separately priced security product. Access follows the applicable GitHub enterprise and Copilot entitlements. Verify preview availability in the exact client versions and deployment method before treating it as a procurement control.
How Kingy would evaluate it
Build a matrix of approved and unapproved GitHub, Git, URL, npm, file and directory sources. Test exact entries, sibling repositories, redirects, mixed case, path traversal, symlinks, moved tags and host-pattern near misses in both supported clients. Repeat with MDM, server and file settings to confirm precedence and update timing.
Then remove a previously allowed marketplace, deploy an empty list and simulate an urgent exception. Confirm installed-plugin behavior, logs, user messaging and rollback. Kingy reviewed the launch post, managed-settings reference, CLI configuration reference, enterprise plugin standards and pricing documentation; we did not deploy the preview or attempt a bypass.
Primary sources
Tool Links
Launch History
strictKnownMarketplaces for Copilot CLI and VS Code
GitHub launched public-preview strictKnownMarketplaces support in enterprise-managed settings for Copilot CLI and Visual Studio Code, restricting plugin installation to explicitly configured marketplace sources.
strictKnownMarketplaces for Copilot CLI and VS Code provides a useful fail-closed plugin-source boundary, including complete lockdown with an empty list. The public preview does…