What Microsoft announced
Ignite returns November 17–20, 2026, at Moscone Center in San Francisco and online. The post says Microsoft will launch a new, publicly available Plugin Catalog on microsoft.com on November 17. It is meant for exploring the broader Microsoft plugin ecosystem and available offerings. The post gives its address as aka.ms/CopilotPluginCatalog.
As of November 13 none of this has happened. The catalog contents, features and exact inventory are unverified. Treat the November 17 launch as a promise, not a fact.
The second change is in the Copilot app itself. As the new Copilot Home brings Chat and Cowork together, users will begin seeing plugins in navigation. Familiar agents stay easy to find. Microsoft describes this as a navigation update. For IT, it says the management experience stays the same, with no back-end changes required. That claim covers the navigation change only. It is not a statement that all plugin governance is frozen.
What counts as a plugin
Microsoft's framing is that a plugin can combine any of three things:
- Skills: reusable instructions that teach Copilot to perform a task consistently.
- Tools: ways to retrieve information or take action through defined inputs, outputs and permissions. Connectors fall under this heading.
- Agents: components that reason and act toward a goal, orchestrating skills and tools.
This is Microsoft's own vocabulary. The post says plugins are becoming common across the industry, but the definitions are not a universal standard. Microsoft's September 30 registry post groups the pieces slightly differently, as skills, connectors and agents.
Catalog versus registry
The new public catalog and the plugin registry are easy to confuse.
- The registry was announced on September 30. It is a shared catalog for discovering, publishing and governing organization-approved and custom-built plugins across Copilot experiences and Microsoft 365 apps. Admins manage it through the Microsoft 365 admin center.
- The public catalog is a microsoft.com destination for browsing what exists.
Nothing in the November 12 post says the public catalog installs plugins, changes tenant policy or bypasses admin approval. Don't assume it does. Microsoft's Cowork documentation says users may need their organization to approve some plugins before they appear in the list. Easier discovery does not mean automatic availability.
Registry background
Several details come from the September announcement and later reporting. They are not new November statements.
- The September 30 post says the registry covers Home (Chat and Cowork), Code, Autopilot, Word, Excel, PowerPoint and SharePoint. The Agents-related buttons are to be replaced by a Plugins button by late November 2026, with no action required from admins.
- The Message Center item gave a two-part schedule. The registry rollout began in late September and was expected to finish by late October. UI changes begin in late October and are expected to complete by late November. The "plugins in navigation" change is therefore part of an already scheduled UI rollout. Your tenant's timing may differ.
- Microsoft said at the time that more than 100 plugins were available, a figure from September. Treat it as a dated September count. Some connectors were still rolling out then.
- Microsoft's published admin guidance says that in the Microsoft 365 admin center, admins review plugins under Agents > Tools. From there they can enable, disable, block or assign them to users or groups.
- A Microsoft release-notes roundup reports that partner plugins and a Dynamics 365 ERP apps plugin are beginning to roll out through the registry. It also lists Capital Markets and Finance plugins in Cowork as generally available.
What the Cowork documentation says about users and admins
Microsoft Learn's Cowork pages show how plugins behave today. They do not prove the new navigation.
For users:
- Plugins can be browsed from the Customize option behind the plus button in Cowork. Each listing shows the name, publisher, description and the skills or connectors it provides.
- Acquired plugins can be toggled on or off in the Sources & Skills panel.
- Connectors that need authentication require each user to sign in or consent once. An admin cannot do this on a user's behalf.
For admins:
- Plugins can be deployed to everyone or to specific users and groups.
- Users need Microsoft 365 Copilot licenses.
- Microsoft says there is currently no single tenant setting that disables plugin sharing for every user. Org-wide publication requires admin approval, but a user can still share an uploaded plugin with specific people. Admins can block a plugin afterward.
- Plugin activity appears in Microsoft Purview audit logs under Copilot activities.
- Purview Information Barriers are not currently supported for plugin or skill management and sharing.
The sharing limits matter for governance. A public catalog and a friendlier Plugins menu will raise user curiosity. Admins who have not decided their policy on user-uploaded plugins should settle it before the questions start.
The Ignite plugin schedule
All times are Pacific. Sessions are forthcoming, and Microsoft says most will be recorded for on-demand viewing.
| Date | Time | ID | Session |
|---|---|---|---|
| Nov 17 | 2:00–3:15 PM | LAB652 | Delegate complex work: Hands-on with Copilot Cowork |
| Nov 17 | 6:15–7:30 PM | LAB654 | Copilot Connectors: Connect once. Use enterprise knowledge everywhere. |
| Nov 18 | 2:50–3:15 PM | THR851 | Skills in Microsoft Copilot (theatre) |
| Nov 19 | 9:00–9:45 AM | BRK222 | What's new in Microsoft Copilot for functional roles |
| Nov 19 | 10:15–11:00 AM | BRK220 | Connect Once: Unlock enterprise knowledge with Copilot Connectors |
| Nov 19 | 11:25–11:40 AM | LTG1181 | Skills for agents: reusable expertise that scales |
| Nov 19 | 4:00–4:45 PM | BRK221 | Govern Once, Use Everywhere: Scale Copilot with One Plugin Registry |
| Nov 19 | 4:15–4:30 PM | LTG1220 | WIQD in 15 minutes: Build, validate, and publish plugins |
| Nov 20 | 9:00–9:45 AM | BRK223 | Getting work done with Copilot as a small business |
| Nov 20 | 11:30 AM–12:15 PM | BRK237 | Plugins for Copilot: build once, govern once, use everywhere |
Note that BRK221 and LTG1220 overlap on November 19, so in-person attendees will have to pick one.
Which session suits whom
- Admins and governance leads: BRK221 covers publishing, approval, discovery and governance. BRK237 follows the lifecycle from build through deployment, evaluation and maintenance.
- Developers: LAB654 has attendees build a custom connector, configure authentication, define actions and publish it. LTG1220 demonstrates Work IQ Developer Tools (WIQD) taking a plugin from scaffolding to organizational sharing. Microsoft's September post described WIQD as covering build, preview, validate, package and publish through the registry.
- Power users and department leads: THR851 and LTG1181 focus on skills. BRK222 targets legal, finance and HR workflows.
- Small businesses: BRK223 promises plugin packages that bundle prebuilt skills, scenarios and business-system connections.
In-person attendees can also visit the Microsoft IQ Expert Meetup at the Expert Meet Up Station, listed as Microsoft IQ EMU (#2).
Analysis: what to watch
This section is analysis based on the announcements, not reporting.
- The vocabulary shift is deliberate. In September, Microsoft said "Plugins" is replacing "Agents" in the top-level Copilot UI, though agents remain part of the extensibility story. Expect help desk questions from users who go looking for the Agents page.
- Consistency is the real pitch. The slogans on the session titles, "govern once" and "build once", describe a single packaging and approval path across Copilot surfaces. Whether the experience matches the slogans will show up in the demos. Microsoft also said Copilot Studio, GitHub Copilot and Foundry are future registry targets, not current ones.
- Discovery before governance can create friction. A public catalog may show plugins your tenant has not approved. That gap is a policy and communication task for IT.
- Marketing caveat. Everything in the Ignite post is Microsoft describing its own products ahead of its own event. Independent verification of the catalog's breadth and the plugins' quality will have to wait until the catalog is live.
Pre-Ignite checklist for admins
- Check the Message Center for the plugin registry item and note when the UI change reaches your tenant.
- Review Agents > Tools in the Microsoft 365 admin center to see what is deployed, blocked or available.
- Decide your stance on user-uploaded plugins and org-wide publication requests.
- Confirm who holds the Copilot administrator role, since plugin management requires it or tenant admin rights.
- Tell users that the Plugins entry replaces the Agents entry and that some plugins will still need approval.
- After November 17, open the public catalog and compare its listings with your tenant's approved set.
Bottom line
The news is modest but concrete. Plugins will show up in Copilot Home navigation, a public Plugin Catalog is scheduled for November 17, and Ignite will carry about a dozen plugin sessions. It is a preview, and the substance arrives next week. Admins should use the gap to get their approval and sharing policies in order.