Microsoft 365 Copilot Connector Prompt Discovery Launches on Web: What Admins Should Know

What Microsoft actually announced​

The roadmap entry is short. A mirror of the record on D365Hub gives the description as "Improve discovery of Champion connector prompts – inline suggestive pre & post prompts, prompt library." The same mirror lists the release phase as General Availability, a release date of December CY2025, the Web platform, the Worldwide (Standard Multi-Tenant) cloud instance, a created date of 2025-09-12, and roadmap ID 502542.

The latest roadmap feed shows the item as Launched. That is the best evidence we have on its current status. One caution: a December 2025 date in a roadmap entry was a planning estimate, not a confirmed ship date. Microsoft's roadmap page says its dates are estimates and subject to change. It also says entries can be removed once a feature reaches general availability, which may explain why the item's details no longer show on the live roadmap page. The November 2026 timestamp on the feed item shows when the record was last pushed. It is not the original announcement date, which archives give as September 12, 2025.

At a glance:

Why connector prompts need help being found​

The problem this fixes is real. Copilot connectors (formerly Graph connectors) bring third-party business data into Microsoft 365 so Copilot can ground its answers in it. Users can already reach that content today. Microsoft's support documentation on referencing content in Copilot Chat says users can ground prompts in their organization's connector data through the references menu: type /, then look under the All and Other tabs for any connectors enabled in Copilot. Microsoft names Confluence, Jira and ServiceNow as examples of supported connectors.

That works if you know about it. Most users don't. A slash menu with tabs is easy to miss, and someone who has never thought to ask Copilot about ServiceNow tickets won't go looking for it. An admin can spend weeks getting a connector deployed and indexed, and the result can still go mostly unused. Suggested prompts shown inline, plus a library to browse, put examples in front of users so they don't have to know the feature exists first.

What isn't specified​

The roadmap description leaves a lot open. The following details are not established:

• What "Champion" means. The entry doesn't say whether it's a formal Microsoft label or program, a set of chosen connectors, or prompts picked by Microsoft or connector publishers.
• Where the suggestions appear. "Pre & post prompts" suggests suggestions before you send a prompt and after Copilot replies. The entry doesn't confirm exactly where on screen they show up.
• Who fills the library. It doesn't say whether admins or connector developers can add, edit or curate entries.
• Which connectors are included, or whether suggestions are personalized.
• Licensing and client coverage. The record lists Web and the Worldwide commercial cloud only. It says nothing about desktop or mobile Copilot, GCC and sovereign clouds, or license tiers.

This is also about discovery, not access. Nothing in the entry says connectors switch on automatically, that permissions change, or that users get new access to connector data. The support documentation describes referencing connectors that are already enabled in Copilot, and existing access controls still apply.

How it relates to Copilot's other prompt features​

Copilot already has a few places to find prompts, which makes it harder to say where this library sits. A third-party field guide from A Guide to Cloud describes a Copilot Prompt Gallery inside the Microsoft 365 Copilot app with hundreds of pre-written, role-aware prompts curated by Microsoft, which users can browse by task, by job type, or by Copilot agent. A community prompt repository on GitHub also reports that Microsoft 365 Copilot now lets IT admins publish a curated prompt library to the whole tenant, surfaced to users in Copilot Chat, Teams, and Edge.

The roadmap entry doesn't say whether the connector prompt library is part of the Prompt Gallery, works alongside organizational prompts, or is a separate feature. Our best guess is that connector prompts appear in the existing Gallery, but that is an inference, not a confirmed fact.

What admins and users can do now​

For IT admins:

1. Check which connectors are enabled for Copilot. Suggestions can only help with data Copilot can already reach.
2. Test it in the web client. The record lists Web only, so start your testing at Copilot Chat in the browser. Don't expect it in every client.
3. Teach the slash menu anyway. Typing / and checking the All and Other tabs is the documented way to reference connector content. Your training shouldn't depend on suggestions appearing for everyone.
4. Write a few prompts of your own. If your tenant uses organizational prompts, connector-specific examples ("Summarize open P1 incidents in ServiceNow assigned to my team") show users what to try.

For users: a suggested prompt gets you started, but it doesn't guarantee a correct answer. Microsoft's own prompting guidance recommends giving a clear goal, then adding context, a source and your expectations when you want more control over the result. The same guidance says Copilot responses can contain errors, so check them, and running the same prompt twice may give different results. That matters most when the source is an incident queue or a Jira backlog someone will act on.

Bottom line​

This is a small, sensible change to make connector data easier to find, not a new capability. Many organizations have already paid to get connector data into Copilot, and this feature tries to get users to actually ask about it. Admins should treat the "Launched" status as permission to check it in their own web tenant, and not promise users a specific interface until they've seen it.