Risk · 10
A catalogue of plugins is not a check
Microsoft announced a plugin registry that brings Microsoft, partner and custom plugins into one catalogue. The partner announcement expected general availability by the end of September 2026. It did not say, on 28 September, that availability had already been confirmed. A catalogue is a list. A list is not a test of whether the action is fit to run.
What central approval does
Central approval and discoverability can stop every team from wiring the same connection in a different corner. That is useful for a company that has just started, because the alternative is a drawer of one-off connectors nobody can name.
Write access still needs an owner
The September notes are consistent on this point across Managed Runtime, Work IQ and plugins: name an owner for the app, the agent identity, the plugin and the connected system before anyone grants a write. Discoverability without that owner is how a convenient plugin becomes an unowned integration.
Fiction keeps the issue open
FrontierOrg, a fictional method, files risk and data issues with stable identifiers instead of rewriting yesterday's entry to look cleaner. A plugin that has not been reviewed stays an open issue. Do not borrow the fictional company. Borrow the refusal to close an issue because a catalogue exists.
Monday
Ask for the list of plugins someone has already connected to a Copilot agent or app. If there is no list, that absence is the finding. Do not approve a new write connection this week.
Who signs for a plugin that can change a customer record, and where is that signature kept?
Sources: Microsoft partner blog, September 2026, The new Copilot is here (opens in a new tab).
Where this note mentions FrontierOrg, that is a fictional method for rehearsing a decision. It is not a company, not a client, and not a case study.