|
| 1 | +--- |
| 2 | +title: About enterprise-managed plugin standards |
| 3 | +shortTitle: Enterprise plugin standards |
| 4 | +allowTitleToDifferFromFilename: true |
| 5 | +intro: Enterprise administrators can centrally define plugin policies for users, ensuring consistent plugin availability. |
| 6 | +versions: |
| 7 | + feature: copilot |
| 8 | +contentType: concepts |
| 9 | +category: |
| 10 | + - Learn about Copilot |
| 11 | + - Learn about Copilot CLI |
| 12 | +docsTeamMetrics: |
| 13 | + - copilot-cli |
| 14 | +redirect_from: |
| 15 | + - /copilot/concepts/agents/copilot-cli/about-enterprise-plugin-standards |
| 16 | +--- |
| 17 | + |
| 18 | +> [!NOTE] This feature is in {% data variables.release-phases.public_preview %} and subject to change. |
| 19 | +
|
| 20 | +Enterprise-managed plugin standards allow administrators to **define and enforce policies for plugin availability**. By configuring a `settings.json` file in the enterprise's `.github-private` repository, administrators can specify which plugin marketplaces are available to users and which plugins are installed automatically. |
| 21 | + |
| 22 | +## Where plugin standards apply |
| 23 | + |
| 24 | +Plugin standards apply to all users on the enterprise's {% data variables.product.prodname_copilot_short %} plan, across the following clients: |
| 25 | + |
| 26 | +* **{% data variables.copilot.copilot_cli_short %}**: see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-cli-plugins) |
| 27 | +* **{% data variables.product.prodname_vscode_shortname %}** (version 1.122 and later): see [Agent plugins in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/agent-customization/agent-plugins) in the {% data variables.product.prodname_vscode_shortname %} documentation |
| 28 | + |
| 29 | +Users must upgrade to a supported client version for these standards to be applied. |
| 30 | + |
| 31 | +## How plugin standards work |
| 32 | + |
| 33 | +Enterprise plugin standards use a configuration file stored in your enterprise's `.github-private` repository. The configuration is defined in a `settings.json` file at the following path: `.github/copilot/settings.json`. |
| 34 | + |
| 35 | +For plugin standards, the file can define: |
| 36 | + |
| 37 | +* **Known marketplaces**. Plugin marketplaces that are available to users for browsing and installing plugins. |
| 38 | +* **Default-enabled plugins**. Specific plugins that are automatically installed when users authenticate. |
| 39 | + |
| 40 | +When a user authenticates to {% data variables.product.prodname_copilot_short %} in a supported client, the client queries an API endpoint that reads the `settings.json` from the enterprise's `.github-private` repository. The policies defined in the file are then applied to the user's session. |
| 41 | + |
| 42 | +## Why use enterprise-managed plugin standards |
| 43 | + |
| 44 | +Enterprise-managed plugin standards help administrators address several common challenges: |
| 45 | + |
| 46 | +* **Consistency across clients**. Ensure that all developers have access to the same plugins and marketplaces. |
| 47 | +* **Centralized governance**. Manage plugin availability from a single configuration file, rather than relying on individual developers to install the correct plugins. |
| 48 | +* **Version-controlled policies**. Because the configuration lives in a Git repository, all changes to plugin standards are tracked, auditable, and reviewable through pull requests. |
| 49 | +* **Reduced onboarding friction**. New developers automatically receive the enterprise's standard plugins when they authenticate, without any manual setup. |
| 50 | + |
| 51 | +## Next step |
| 52 | + |
| 53 | +To configure enterprise plugin standards, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-plugin-standards). |
0 commit comments