GitHub Lets Enterprise Admins Force Copilot Customisations Through Plugins, and Streams Agent Activity to Microsoft Agent 365
GitHub added a plugin-only setting for Copilot skills, agents, hooks, MCP servers and extensions, audit streaming into Microsoft Agent 365, Entra sign-in for Copilot CLI and team defaults. Secret scanning is available but off. What to decide first.

GitHub added three administrator controls for Copilot between Monday 16 and Wednesday 18 November, and added a fourth capability, secret scanning, that stays off until someone turns it on. Enterprise administrators can now require that Copilot’s skills, custom agents, hooks, MCP servers and executable extensions come only from plugins or managed settings. They can stream Copilot agent activity, including prompts and responses, into Microsoft Agent 365. And organisation teams can set approved plugins as team defaults. None of these is switched on for you. If your organisation runs Copilot Business or Copilot Enterprise, the one to decide on first is the plugin-only setting, because without it any developer can wire a new MCP server into Copilot from their own configuration file.
All of the details below come from four GitHub changelog posts, read on Sunday 22 November. GitHub is the only source for what these features do, so where we describe a setting we say GitHub’s changelog says so, and where we offer a view we label it as ours.
#Plugin-only customisation: the control that closes a door
The post of 16 November describes a managed setting called strictPluginOnlyCustomization. When it is on, GitHub says, standalone customisations from user and project sources are blocked, while eligible plugins and managed settings stay allowed, subject to your other policies. You can apply it to all five categories GitHub names or choose some of them. GitHub’s own example restricts MCP servers and extensions while leaving skills, agents and hooks open.
Two points in the post are easy to misread. First, GitHub says plugin-only does not mean enterprise-managed plugins only, and that it is not a marketplace allowlist. If you want to limit where plugins may come from, you pair it with a second setting, strictKnownMarketplaces. Second, GitHub says the extensions it means here include executable canvas providers, not VS Code Marketplace extensions, so this does not govern your editor extensions.
It applies to enterprise administrators on GitHub Enterprise Cloud, for members whose Copilot Business or Copilot Enterprise licences are issued by the enterprise or one of its organisations, according to GitHub.
Our view: this is the most useful of the four, and the reason is MCP servers. An MCP server, short for Model Context Protocol server, is a connector that lets an AI agent call a tool or read a data source. Each one a developer adds is a new route between your code, your credentials and someone else’s service. Today the only thing between a developer and a new connector is their own judgment. Plugin-only turns that into a review step. We would switch it on for MCP servers and executable extensions first, which is the part of GitHub’s example that carries the most risk, and leave skills and hooks open until you know how your teams use them.
#Agent 365 gets the audit trail
On Tuesday 17 November GitHub said enterprises can stream Copilot agent activity into Microsoft Agent 365, which it describes as Microsoft’s agent control plane. According to GitHub, administrators can see activity across cloud agents on GitHub.com, Copilot CLI, Visual Studio Code, Visual Studio and partner IDEs such as JetBrains and Eclipse. They can review user sessions, including prompts, responses and tool calls, and see usage trends in Agent 365, and they get additional risk information in Microsoft Purview and Defender. It is available to GitHub Enterprise Cloud customers with Enterprise Managed Users, and GitHub points to its documentation on streaming the enterprise audit log for setup.
What GitHub does not say is who inside your organisation should be able to read those prompts. A developer’s prompt can contain code, customer data pasted for debugging, or a credential. Sending those into another system makes that system a store of sensitive material, and in the UK it is the kind of monitoring that your data protection lead and your staff privacy notice should cover before it goes live. We are not giving legal advice, and GitHub’s post does not discuss it. Our reading is that this is a good feature with a decision attached, and the decision is about access to the stream, not about whether to have it.
#Signing in with Entra, and which bill you pay
Also on 17 November, GitHub announced Microsoft Entra sign-in for Copilot CLI in public preview, on Windows and macOS, with Linux to follow. It works two ways, and GitHub is careful to separate them.
- Enterprise Managed Users: for enterprises using OIDC, GitHub says Copilot CLI supports silent single sign-on with your Entra identity. You need a Copilot Business or Copilot Enterprise licence, and your organisation must enable the Copilot CLI policy. Inference and usage are governed by the organisation’s GitHub Copilot plan. GitHub says the experience is limited to Copilot CLI and VS Code.
- Microsoft 365 Copilot licence: if your organisation is in Frontier and has a Microsoft 365 Copilot licence with usage-based billing, Entra sign-in lets a user reach models available through Microsoft Copilot from the terminal, without a GitHub account. In that case, GitHub says, the CLI uses Microsoft 365 inference, and model access and usage limits are managed through Microsoft 365 Copilot settings, not GitHub.
The second route is the one to watch. The same command-line tool can now draw on two different bills and two different sets of controls depending on how a person signs in. GitHub requires Copilot CLI version 1.0.113 or later. If you manage Copilot CLI centrally, check which version your developers run before assuming they can use either route.
#Team defaults, and where the guardrails stop
On Wednesday 18 November GitHub made team customisations generally available for organisation teams on Copilot Business and Copilot Enterprise. Team maintainers and organisation owners can choose approved agent plugins as team defaults from the Customize Copilot tab of the team page on github.com, drawing on the built-in marketplaces, enterprise marketplaces or ones the team adds. According to GitHub, the plugins are enabled by default for a team’s direct members in VS Code, the GitHub Copilot app and Copilot CLI, members of child teams do not inherit them, and members can turn a team plugin off where policy permits. Enterprise and organisation policies take precedence over team choices.
Read that with the first section. A team maintainer can add a marketplace, and a marketplace is a source of plugins. If no marketplace restriction is set, our reading is that a team could add a marketplace of its own choosing and enable plugins from it, within whatever your policies block. Our view is that the plugin-only setting and the marketplace restriction need to be decided together, or the first gives less protection than it appears to.
#Secret scanning: available, and off
The last item is not an admin control in the usual sense, but it changes what Copilot can catch. GitHub says Copilot’s security review specialist now runs GitHub secret scanning, in public preview, in Copilot CLI and Copilot app sessions, through Copilot SDK integrations and in Copilot code review. It says the scanning detects more than 500 secret types, built with more than 150 industry partners, and adds a fine-tuned model that reads the surrounding code for credentials without a recognisable format. It checks your changes, not repository history.
GitHub says secret scanning is off by default, and that until you opt in, security review uses its existing detection only. Opting in is a different action in each place: /settings aiSecretDetection on in an interactive Copilot CLI session, Settings then Experimental in the Copilot app, and Settings, Copilot, Code review, then Secret scanning under Security for a repository’s code review. VS Code is not included in this release, and for SDK integrations a model-provider API key alone is not enough. GitHub says no extra plan is needed, but scans use AI credits under the Secret Protection AI Credit SKU, which means they appear on a bill.
#What we would do this week
- Find out what is allowed today. Ask a developer to add an MCP server to their own project configuration and see whether Copilot accepts it. If it does, your organisation is permissive by default.
- Decide on plugin-only and marketplaces together. Start with MCP servers and executable extensions, and list the marketplaces you are happy with before you restrict them.
- Do not turn on Agent 365 streaming until you know who reads it. Agree who may view prompts and responses, how long they are kept and what staff are told.
- Check your Copilot CLI version against 1.0.113 and decide which sign-in route, if either, you want to allow.
- Pilot secret scanning in one repository and watch the AI credit use before you enable it widely.
#If you are a small team
These features sit at different levels. GitHub’s posts say plugin-only customisation applies on GitHub Enterprise Cloud and Agent 365 streaming needs Enterprise Cloud with Enterprise Managed Users, so a firm with a handful of developers on an ordinary organisation plan may not have them. Team customisations are for Copilot Business and Copilot Enterprise, and the secret scanning opt-in is at repository level. The practical step for a small firm is the last item above, and the person who owns the GitHub account should check which plan it is on before anything else.
#What we do not know
GitHub’s posts do not say whether plugin-only customisation will become a default, what Agent 365 streaming costs, how long the Entra sign-in preview will last, or how many organisations have turned any of this on. They do not describe what a blocked customisation looks like to a developer. We have not tested any of these features, and everything we say about what they do is as GitHub describes them. We expect GitHub to keep adding controls at this pace, which is our reading rather than a statement from GitHub; we would be proved wrong if the next few weeks of changelog posts brought none.
For the related question of which models your developers can pick, and which are being retired, see our piece on ten Copilot models retiring by 18 December.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01GitHub changelog, 16 November 2026: Control where GitHub Copilot customizations come fromgithub.blog
- 02GitHub changelog, 17 November 2026: Monitor GitHub Copilot activity through Microsoft Agent 365github.blog
- 03GitHub changelog, 17 November 2026: GitHub Copilot CLI adds Microsoft Entra sign-in as a previewgithub.blog
- 04GitHub changelog, 18 November 2026: Customize GitHub Copilot for your teamgithub.blog
- 05GitHub changelog, 17 November 2026: Secret scanning on demand for developers and agentsgithub.blog
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
More news
All newsWas this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.




Comments
Add a thoughtful note on GitHub Lets Enterprise Admins Force Copilot Customisations Through Plugins, and Streams Agent Activity to Microsoft Agent 365. Comments are checked for spam and held for moderation before appearing.