Live
Cloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AICloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AI
GitHub

Enforcing Plugin‑Only Copilot Customizations in GitHub Enterprise

AI SummaryPowered by AI

GitHub Enterprise Cloud now offers a strictPluginOnlyCustomization managed setting that forces selected Copilot customizations to be supplied only via approved plugins or managed settings, blocking user‑ or project‑level definitions. This gives AI, platform, DevOps, and security teams tighter control over extension sources, simplifying compliance and reducing the risk of unvetted code running in Copilot workflows.

GitHub Enterprise Cloud has introduced a new managed setting, strictPluginOnlyCustomization, that lets administrators require certain Copilot customizations to originate exclusively from approved plugins or enterprise‑managed settings. By blocking standalone user or project configurations, the change directly affects how AI engineers, platform engineers, SREs, and security staff source and govern Copilot extensions.

Copilot Plugin Enforcement

The setting can be applied globally or to any of the five supported customization categories: skills, custom agents, hooks, MCP servers, and executable Copilot extensions. When enabled, any attempt to define a customization from a user’s personal configuration or a project’s repository is rejected, unless the definition is delivered through a plugin that the enterprise has approved via managed settings. The policy does not automatically restrict marketplace sources; administrators must combine it with strictKnownMarketplaces or other marketplace controls to limit which external plugins are acceptable.

Operational Impact

Teams will need to audit existing Copilot customizations to determine which fall under the new restriction. Approved plugins must be catalogued in the enterprise‑managed settings, and CI/CD pipelines may require updates to ensure that only those plugins are referenced during builds or deployments. Because the policy can be scoped per‑category, organizations can adopt a phased approach—e.g., enforce plugin‑only for MCP servers and executable extensions while leaving skills and hooks open for rapid experimentation.

Configuration is performed through the GitHub Enterprise Cloud admin console and applies to members holding Copilot Business or Copilot Enterprise licenses. Existing managed settings that already define marketplace allowances can be extended to include the new plugin‑only requirement, avoiding a complete rewrite of policy definitions.

Security and Compliance Considerations

Requiring plugins or managed settings creates a clearer provenance chain for code that runs inside Copilot. This can simplify audits, as each approved plugin can be reviewed once and then trusted across the organization. However, the setting alone does not constitute a marketplace allowlist; pairing it with strictKnownMarketplaces is necessary to prevent unvetted marketplace plugins from slipping through. Security engineers should verify that the approved plugin list is kept up to date and that any new plugin undergoes the organization’s standard review process before being added to the managed settings.

Related CloudNinjas coverage: AI engineering.

What This Means For Practitioners

  • Review current Copilot customizations and map them to the five categories.
  • Identify which categories merit plugin‑only enforcement based on risk and compliance needs.
  • Populate managed settings with approved plugins and, if needed, define strict marketplace policies.
  • Update CI/CD scripts to reference only approved plugins and validate that builds fail when disallowed customizations are detected.
  • Establish a periodic review process to keep the approved plugin list aligned with security and operational requirements.
Originally published atGitHub Changelog