Configuring enterprise plugin standards

You can apply settings to control users' available plugin marketplaces and default-installed plugins. These settings apply to users on your enterprise's Copilot plan. For more information, see About enterprise-managed plugin standards.

1. In your enterprise's .github-private repository, navigate to the .github/copilot/ directory. If you don't have a .github-private repository yet, see Preparing to use custom agents in your enterprise.

2. Create or edit the settings.json file at .github/copilot/settings.json.

3. Add your plugin policy configuration to the file. The settings.json file supports the following top-level properties:

   JSON

   {
     "extraKnownMarketplaces": {
       "MARKETPLACE-NAME": {
         "source": {
           "source": "github",
           "repo": "OWNER/REPO"
         }
       }
     },
     "enabledPlugins": {
       "PLUGIN-NAME@MARKETPLACE-NAME": true
     }
   }
   

   • extraKnownMarketplaces: Defines additional plugin marketplaces available to users. Each entry is a named marketplace object containing a source property that specifies the provider ("github") and the repository in OWNER/REPO format.
   • enabledPlugins: Defines plugins that are automatically installed for all enterprise users. Each entry uses the format PLUGIN-NAME@MARKETPLACE-NAME as the key, with a boolean value of true to enable the plugin.

4. Commit and push your changes to the default branch of the .github-private repository.

Once the configuration is committed, users will see the specified marketplaces and pre-installed plugins the next time they authenticate from a supported client.

If a user does not see these settings, ensure they receive access to Copilot through your enterprise or one of its organizations. If a user receives a license from multiple billing entities, ensure they have selected your enterprise in the "Usage billed to" dropdown in their personal Copilot settings.