Microsoft 365 Copilot ExpandedContextIQ: Web Prompt Picker Preview Planned for October 2026

The item is listed as in development. Preview is scheduled for October 2026 and general availability for November 2026. Nothing has shipped yet, and Microsoft says everything on the roadmap is an estimate and subject to change.

The roadmap entry at a glance​

A few boundaries are worth noting:

• Web only. The listing names no desktop app, mobile app or Windows client version.
• Worldwide commercial cloud only. GCC, GCC High, DoD and other sovereign clouds are not listed. Customers in those clouds should not expect this rollout on the same schedule.
• Two release stages. Preview comes first and general availability follows about a month later, if the dates hold.

Section summary: This is a planned change to the Copilot prompt-writing experience on the web in the worldwide commercial cloud. It is not available yet.

What "ExpandedContextIQ" actually promises​

The description is one sentence long: users will be able to discover and select more agents, skills and content sources while composing prompts. In practice, you would pick the right helper or data source at the moment you write the request, instead of hoping Copilot picks correctly or leaving the prompt to set things up somewhere else.

The listing leaves a lot out. It does not say:

• which agents, skills or content sources will appear in the picker
• how the picker will be triggered or laid out
• whether it will vary by license, tenant configuration or admin policy
• whether selecting a source affects grounding priority, scope or cost

There are no screenshots, setup steps or eligibility details. Anyone claiming to know exactly what the picker looks like is guessing.

Why "skills" and "sources" mean something specific in Work IQ​

The terms in the roadmap line already have defined meanings in Microsoft's Work IQ documentation.

Skills. In a March post on the Microsoft Community Hub, Microsoft said Work IQ includes agentic skills that provide specialized instructions to Copilot & agents. The company described adding skills to Work IQ that enable Copilot to deliver experiences that are highly tailored for specific tasks like "schedule a meeting", "find and retrieve data from an external source", or "access meeting details and transcripts". The same post summed up how skills and tools relate: "If skills describe what to do, tools do it."

Content sources. Microsoft's Work IQ overview on Microsoft Learn says that in addition to productivity data from Microsoft 365 applications, Work IQ also includes business and workflow data from Dynamics 365 and Power Platform. A July explainer from Emergent Software said Microsoft's current Work IQ sources documentation identifies mail, calendars, Teams, OneDrive, SharePoint, user profiles, people information, Microsoft 365 Copilot Search, and SharePoint Lists as available Work IQ source categories.

External systems. In a Microsoft Mechanics episode from May, Microsoft showed how organizations can extend the same knowledge layer to ServiceNow, CRMs, and other non-Microsoft systems with API and MCP Server connectors in the Microsoft 365 admin center.

None of these sources confirm what the new picker will offer. They do show what already exists in the Work IQ platform and could be surfaced. The roadmap entry does not say which of these will appear or whether any third-party connector will be selectable.

Section summary: Skills, sources and agents are existing Work IQ concepts. The roadmap item is about making them easier to find and select when writing a prompt, not about adding new data sources.

What this is not: the Work IQ APIs​

Don't confuse this with the Work IQ APIs. In June, Microsoft announced those APIs with general availability on June 16, 2026. It described four domains, Chat, Context, Tools and Workspaces, with usage-based pricing in Copilot Credits. Microsoft's Learn documentation says that for the Context domain, Work IQ assembles and grounds context internally across organizational and business data to provide agent-ready inputs, so agents don't need to stitch together raw signals or manage retrieval pipelines.

That is a developer-facing API. ExpandedContextIQ, as described, is a change for users in the Copilot web interface. Nothing in the roadmap entry says it adds API endpoints, changes the Work IQ API contract or uses the credit-based billing model. Microsoft's overview also separates licensed users' access in Microsoft 365 Copilot experiences from usage billing for custom and third-party agents. The roadmap item says nothing about licensing at all.

The governance question admins will ask first​

Will a picker full of agents and sources let users reach data they couldn't reach before? Nothing in the roadmap entry says so, and Microsoft's documentation points the other way.

Microsoft describes Work IQ requests as user-scoped: each one runs in a specific user's context and only reaches what that user can already see or do. Its Rego-based policy engine evaluates factors like resource paths, request methods, user identity, and data content to control exactly what actions are allowed. Microsoft also says every tool invocation is logged and evaluated.

That describes Work IQ's existing controls. The roadmap item does not repeat them or promise anything specific about the new picker. A picker is a discovery interface, not a permissions grant, but admins should confirm that in the preview rather than assume it.

A practical prep list for IT​

Based on the documented Work IQ model, these are reasonable steps before October. They are my recommendations, not Microsoft guidance:

1. Review your agent inventory. If users will be able to browse agents from the prompt box, any agent you have deployed or allowed may become more visible. Clean up stale or experimental ones.
2. Audit connectors. Check which Microsoft 365 Copilot connectors and MCP connections are enabled in the admin center. More visible sources means more use of whatever you have connected.
3. Check oversharing hygiene. User-scoped access protects you only as well as your SharePoint and OneDrive permissions do. Easier source selection won't create oversharing, but it may expose existing oversharing.
4. Watch Message Center. Roadmap items usually move to Message Center posts closer to rollout, often with admin-control details. Wait for that before writing user guidance.
5. Plan preview testing. If your tenant gets early features, have a few people test which sources and agents appear for users with different permission levels.

Analysis: small UI, big behavioral shift​

A prompt-box picker looks minor, but it changes how people use Copilot. For most of its life, Microsoft 365 Copilot has asked users to trust the orchestrator: type a request, and Copilot decides what to search and which capability to use. That keeps things simple, but users can't see what's happening. When Copilot grounds an answer in the wrong document, users often don't know why.

Explicit selection is the opposite approach. It gives experienced users control, and it could reduce hallucination-style mistakes caused by retrieving the wrong source. The risk is choice overload. If a large enterprise has dozens of agents and connectors, a picker could turn into a cluttered menu that users ignore. Discovery only helps if the list is curated, and that is partly your job as an admin, not only Microsoft's.

Microsoft's own marketing pulls the other way. Its Work IQ materials promise grounding without long prompts, manual up..., meaning Copilot finds context for you. ExpandedContextIQ suggests Microsoft now sees value in letting users steer as well. That's a sensible hedge: automatic context for most users, explicit choices for those who want them.

The effect on answer quality or productivity can't be judged until the preview arrives.

Bottom line​

• What: Roadmap item 570854 expands Context IQ so Microsoft 365 Copilot users on the web can discover and select more agents, skills and content sources while writing prompts.
• When: Preview is targeted for October 2026 and general availability for November 2026. Both are estimates, and the feature is still in development.
• Where: Web only, in the Worldwide (Standard Multi-Tenant) cloud.
• What's unknown: Which sources and agents appear, the interface design, licensing and admin controls.
• What to do now: Tidy up agents and connectors, check permissions, and look for the Message Center post before telling users anything.