New video: امریکہ کے قومی ترانے میں ٹیپو سلطان کے راکٹ؟ →
Muddaser

Microsoft Copilot Plugin Catalog: Find, Approve & Install Plugins

The Microsoft Copilot Plugin Catalog is now live at microsoft.com/en-us/copilot/features/plugins/explore. Use it to discover Copilot plugins, but remember: finding a plugin in the public catalog does not mean your organization has approved it. An administrator may still need to allow, assign or install it before you can use it.[1][3]

Quick checklist: what to do now

  • Browse first: open the public Copilot Plugin Catalog and identify the capability you need.
  • Check what is inside: a plugin may contain a reusable skill, a tool or connector, an agent, or a combination of these.[1][3]
  • Review access: if Copilot says the plugin is blocked, use Request access rather than trying to bypass your organization’s policy.[4]
  • Start with a small user group: administrators can assign a plugin to all users or only selected users and groups.[4]
  • Test the actual workflow: verify its output, data access and any actions it can take before a wider rollout.
  • Keep high-risk actions restricted: tools that write, delete or process payments deserve stricter controls than read-only tools.[4]

What is a Microsoft Copilot plugin?

A Microsoft 365 Copilot plugin is an installable package that adds capabilities to Copilot and related Microsoft AI experiences. Microsoft’s current model groups three kinds of capability inside plugins:[1][3]

  1. Skills — reusable instructions that teach Copilot how to complete a task consistently.
  2. Tools — connections that retrieve information or perform actions through defined inputs, outputs and permissions; connectors are included in this category.
  3. Agents — specialized assistants that reason toward a goal and can coordinate skills and tools.

A plugin does not need all three. A packaged skill by itself can be a plugin, while a more advanced package may combine an agent, internal knowledge, connectors and an MCP server.[3]

This terminology matters because “plugin” no longer means only a small add-on that calls one external API. It can represent a complete work package: instructions, data access and an agent that uses both.

Plugin Catalog vs plugin registry vs Tools Registry

These names sound interchangeable, but they serve different purposes.

  • Copilot Plugin Catalog: the public discovery page where people can browse available plugins.
  • Plugin registry: a publishing and distribution destination for plugins shared with a selected audience.
  • Tools Registry: the Microsoft 365 admin center view used for visibility and governance of plugins, skills, MCP servers and connectors.
  • Agent Registry: the admin view for agent-specific controls.
  • Microsoft Marketplace: a route publishers can use to reach customers across organizations.[3]

The key rule is simple: publicly listed does not mean tenant-approved. Microsoft explicitly separates public discovery, publishing and organization-level administration.[3]

How end users can find and request a plugin

1. Open the public catalog

Go to the Microsoft Copilot Plugin Catalog. Microsoft launched the public catalog alongside Ignite 2026 as a starting point for exploring the broader plugin ecosystem.[1]

2. Match the plugin to a real job

Do not install a plugin only because its demo looks impressive. Write down the job you need it to perform, such as:

  • preparing a sales meeting brief;
  • finding an approved internal policy;
  • drafting a support escalation summary;
  • checking a contract against a playbook;
  • updating a CRM record after human review.

Then inspect whether the plugin uses skills, tools, agents or external services. The more systems it can access and the more actions it can take, the more carefully it should be reviewed.

3. Check availability inside Copilot

Microsoft is bringing plugins into Copilot navigation as part of the experience that combines Chat and Cowork. The catalog helps with discovery, while actual availability still depends on your tenant, licensing, rollout stage and admin policy.[1][2][3]

If the plugin is restricted, it can remain visible with a message saying it is blocked by organizational policy. Eligible users can select Request access, which sends a request to the Microsoft 365 admin center for approval or rejection.[4]

4. Test with non-sensitive work first

Use a low-risk example before connecting confidential documents or letting a plugin perform actions. Confirm:

  • the plugin selects the right sources;
  • its result can be traced back to those sources;
  • permissions match the intended user group;
  • it asks for review before consequential actions;
  • failure states are clear rather than silently producing incomplete work.

Admin checklist: approve and install safely

Control which publisher categories are allowed

In the Microsoft 365 admin center, go to Agents → Settings → Agent and plugin access. Administrators can control discovery and installation by publisher category: Microsoft, the organization itself, or certified external publishers.[4]

A cautious rollout can begin with Microsoft and organization-owned plugins, then add selected external publishers after security and procurement review.

Assign a plugin to a pilot group

For an individual plugin, go to Agents → Tools → Plugins, open the plugin, then choose availability for:

  • all users;
  • no users; or
  • specific users and groups.[4]

Use a pilot group that represents the real workflow. A plugin tested only by IT may behave differently when used with live finance, sales or service processes.

Review access requests

Requests appear under Agents → Tools → Requests. Review the user, requested plugin, publisher, permissions and business reason before approving or rejecting access.[4]

Upload an internal plugin or skill

Microsoft’s documented path for internal packages is Agents → Tools → Registry → Upload. The package must already have a valid manifest. During installation, the admin reviews included components and scopes access to all users or specific users and groups.[4]

Know what blocking affects

Blocking a plugin prevents users from accessing that package and agents that depend on it, but associated MCP servers or connectors may remain available to other plugins. Blocking an MCP server can also disable dependent plugins, so administrators should check dependencies before making a broad change.[4]

For supported MCP servers, Microsoft is also rolling out tool-level controls. This lets an organization keep lower-risk read operations available while disabling higher-risk tools such as write, delete or payment actions.[4]

A practical five-minute risk review

Before approving a plugin, record answers to these questions:

  1. Who published it? Is it Microsoft, your organization or a certified external publisher?
  2. What data can it read? Check mail, files, chats, CRM records and external services separately.
  3. What can it change? Distinguish search and summarization from create, update, delete, send and payment actions.
  4. Where does processing happen? Identify external APIs or remote MCP servers.
  5. Who receives access? Prefer a named pilot group over an all-user rollout.
  6. Is a human approval step present? Require review for messages, record changes, purchases and other consequential actions.
  7. Can you disable it quickly? Confirm the plugin and its dependent tools appear in the appropriate registry.
  8. How will you test it? Include expected, ambiguous, unsupported and failure scenarios.

Where the new catalog fits in Microsoft’s Copilot changes

At Ignite 2026, Microsoft announced that Copilot Home and Office in Copilot were generally available, while Code was due to become generally available in the following weeks and Autopilot was beginning a Frontier rollout. Microsoft also announced new role-focused plugins and skills for sales, service, finance and legal work.[2]

The catalog is the discovery layer for this expanding ecosystem. Microsoft’s unified registry provides centralized management and control, while the individual plugin still needs to pass the organization’s own access and governance process.[2][3]

That separation is useful. Employees can discover what exists without administrators automatically approving every listed integration.

Common problems

“I can see the plugin but cannot install it”

Your organization may block its publisher category or restrict the plugin to another user group. Use Request access if that option appears, and give a specific business reason.[4]

“The Plugin Catalog page works, but the plugin is missing in Copilot”

The public catalog and your tenant’s available plugins are not the same list. Availability can depend on tenant policy, product support, rollout stage and required setup.[1][3]

“Should we enable every certified external plugin?”

No. Certification is not a substitute for checking permissions, data handling, business need and action risk. Allow only the publishers and plugins your organization can support and govern.

“Is an agent the same as a plugin?”

Not exactly. A plugin is the installable package. An agent can be one component inside that package, alongside skills and tools.[3]

FAQ

Is the Microsoft Copilot Plugin Catalog public?

Yes. Microsoft describes it as a public registry for discovering available plugins, and the catalog is accessible on Microsoft’s website.[1][3]

Does a catalog listing mean a plugin is approved for my company?

No. Public discovery and tenant approval are separate. Your administrator may need to allow the publisher category, install the plugin or assign it to your user or group.[3][4]

Can administrators block third-party Copilot plugins?

Yes. In Agents → Settings → Agent and plugin access, administrators can clear the category for certified external publishers. Individual plugins can also be restricted or blocked.[4]

Can a Copilot plugin include an MCP server?

Yes. A plugin may include or connect to tools through supported MCP configurations. Administrators should review the server, declared tools, permissions and dependent plugins before approval.[3][4]

What is the safest rollout approach?

Begin with a defined use case, a small user group, non-sensitive test data and human review for consequential actions. Expand only after checking permissions, output quality, dependencies and failure behavior.

Bottom line

The Copilot Plugin Catalog makes discovery easier, but governance still happens inside the organization. Browse publicly, evaluate the plugin’s skills and tools, request access through the supported workflow, and pilot before expanding. The strongest plugin is not the one with the most capabilities; it is the one that solves a defined job with the minimum data access and action permissions required.

Sources

[1] https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/plugins-at-microsoft-ignite-2026/4569951 — Plugins at Microsoft Ignite 2026
[2] https://www.microsoft.com/en-us/copilot/blog/2026/11/17/copilot-at-microsoft-ignite-expanding-whats-possible-with-intelligence-built-for-work — Copilot at Microsoft Ignite 2026
[3] https://learn.microsoft.com/en-us/plugins/overview — What Is a Microsoft 365 Copilot Plugin?
[4] https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-plugins-skills-mcp-servers?view=o365-worldwide — Manage plugins, skills, and MCP servers

Leave a Comment