Sulat.com / Writing on AIWednesday, November 18, 2026
Agent Engineering/18 November 2026

Work IQ gives agents one MCP server for Microsoft 365, and Ignite adds org context

Microsoft's Jeff Teper flagged people and org context in Work IQ for Ignite. Work IQ's MCP server, built around a handful of generic tools, is generally available, but every performance figure published so far is Microsoft's own.

3D Microsoft logo tiles feeding cables from mail, calendar, chat and files into one glowing connector

At a glance

  • Jeff Teper's "Big addition to Work IQ" post links an announcement on people and org context in Copilot and Cowork, covering headcount and skills answers, and the announcement doesn't mention MCP.
  • Microsoft says the Work IQ MCP server, generally available since 16 June, exposes Microsoft 365 through one endpoint and a handful of generic tools instead of one server per workload.
  • Every performance figure so far, including a SharePoint pass rate rising from 70.1% to 84.6%, comes from Microsoft's own testing, and none of the three named customer quotes says it uses the MCP server.
  • Writes are blocked by default and the tenant policy is a single on or off switch; the retrieve tool, SharePoint tools and Copilot Studio integration are still in preview.

Microsoft executive vice president Jeff Teper said “Big addition to Work IQ for #MSIgnite” in a post on X that links Microsoft’s announcement of people and org context in Work IQ. The announcement covers Copilot and Cowork answers about headcount, reporting lines and skills. It doesn’t mention MCP, the Model Context Protocol that lets an AI agent call tools in other apps. Work IQ has an MCP server too, and Microsoft made it generally available on 16 June.

Stephanie Mylenski wrote the announcement, published on 16 November (US time). Ignite runs from 17 to 20 November in San Francisco. This piece covers both halves: what the people and org context adds, and what the Work IQ MCP server does for companies that want one route for agents into Microsoft 365, with the evidence Microsoft has published for it.

What Teper’s post adds

Microsoft describes Work IQ as the intelligence layer behind Microsoft 365 Copilot and agents. People and org context brings together three things: org and people data, customer-defined context such as which employees count toward headcount, and analytical reasoning over both. Microsoft’s example questions include the headcount in a leader’s org, the manager-to-individual-contributor ratio compared with company guidelines, and who has machine learning experience.

The data comes from the Microsoft 365 Organizational Data Service, which ingests HR system data automatically, and from Copilot connectors for external HR and recruiting tools. The Workforce Insights Agent lets admins and HR specialists add attribute descriptions and organisational context, then check how the changes affect answers. A Workforce Intelligence plugin for Cowork adds three launch skills: an organisational snapshot, a people skills landscape and a shareable organisational dashboard. Microsoft says the feature is “not for monitoring employee performance”.

CapabilityStatus
People and org data, standard and custom attributesGA
Analytical reasoning (counts, ratios, averages)GA
Organisational skills insightsGA
Organisational contextFrontier
Context and attribute configuration in the Workforce Insights AgentFrontier
Domain-grounded skills in the Cowork pluginFrontier
Rollout runs through December. Source: Microsoft Tech Community, 16 November.

The announcement describes these features inside Copilot and Cowork. It doesn’t say whether the org data reaches outside agents through the Work IQ MCP server. Microsoft lists restricted-data handling, guided workflows for leaders and response tuning as areas it’s exploring next.

What the Work IQ MCP server does

According to Microsoft Learn, the Work IQ MCP server lets agents read, create, update and delete Microsoft 365 entities, call Microsoft 365 Copilot, pull grounding content and look up API schemas, all through one MCP endpoint. Sign-in goes through Microsoft Entra. Microsoft’s SharePoint team gives the address as workiq.svc.cloud.microsoft/mcp, and the Work IQ plugin for GitHub Copilot CLI points at the same server.

Microsoft’s design rule is “Fewer tools, more paths”. A small set of verbs acts on resource paths, so a new workload adds paths and the tool list stays the same size. Microsoft’s June launch post says the server collapses hundreds of operations into 10 generic tools.

CallWhat it does
fetch /me/messagesReads the user’s email
create_entity /me/eventsCreates a calendar event
do_action /me/sendMailSends an email
call_function /search/queryRuns a semantic search
askPuts a natural-language question to Microsoft 365 Copilot
retrieveReturns grounding text with citations and source metadata
Examples from Microsoft Learn’s Work IQ MCP overview.

The Learn tool reference names 12 tools: seven entity tools (fetch, fetch_blob, create_entity, update_entity, delete_entity, do_action, call_function), three Copilot tools (ask, retrieve, list_agents) and two schema tools (get_schema, search_paths). The launch post and the Agent 365 documentation say 10. The Learn overview says the tools fall into four categories and lists three.

Diagram: agents connect to one Work IQ MCP server, which checks policy and reaches mail, Teams, files and people
Agents connect to one server, and Microsoft’s checks run on every call.

Why Microsoft calls it unified

Microsoft’s Agent 365 documentation sets Work IQ MCP, a single endpoint with generic tools, against the older Microsoft-hosted servers for Copilot, Calendar, Mail, SharePoint, OneDrive, Teams, User and Word. It calls those “a legacy experience retained for testing and backward compatibility” and tells admins not to pick them in place of Work IQ. Custom and third-party MCP servers register through a bring-your-own process so admins can review them in one place.

Microsoft’s own IT team makes the same case for its developers. In a June post, Microsoft Digital wrote: “Rather than asking our developers to configure dozens of individual connectors for mail, calendars, files, and meetings, Work IQ offers them a single-entry point for enterprise context.” It adds that admins decide which Work IQ MCP servers are enabled in the tenant and who may use them.

The preview of SharePoint tools, announced on 3 November, shows how the design scales. The catalogue holds more than 60 SharePoint operations, but they appear as /sharepoint/ paths behind the same verbs instead of 60 extra tools. An agent calls search_paths to find an operation, get_schema to read its arguments and do_action to run it, and Work IQ routes the request to SharePoint in one hop without a second model in the middle, Microsoft says.

Three steps: search_paths finds a SharePoint path, get_schema checks it, do_action runs it
The agent looks up a SharePoint action when it needs one instead of carrying 60 tools.

Two more additions ride on the same server. Microsoft’s Dynamics 365 team says business skills, which package instructions and context for a business task, can be defined once and reused by every agent connected to Work IQ MCP, including Copilot Studio agents. A Message Center notice from 5 November adds a read-only /memory/me/coreMemories path that gives agents a user’s custom instructions, saved memories and chat-history insights, rolling out through December.

“Unified” covers Microsoft 365 and Microsoft’s business apps. Servers from other companies sit beside Work IQ in the Agent 365 registry rather than behind it.

The evidence so far

Microsoft’s SharePoint team says adding SharePoint tools raised Work IQ’s task pass rate from 70.1% to 84.6% while using 16% fewer tokens, in its internal evals. Against direct Graph access, it reports a success-rate lift of up to 77% depending on the task. The June launch post claims 80% fewer tokens than traditional APIs in coding harnesses and twice the speed, both from Microsoft’s internal testing. Every performance figure published so far comes from Microsoft.

Four stat cards: 70.1% to 84.6% pass rate, 16% fewer tokens, up to 77% over Graph, 80% fewer tokens
Every performance figure published so far comes from Microsoft’s own tests.

The launch post names three customers. SLB’s Shashi Menon said SLB uses Work IQ inside its Tela assistant so subsurface workflows can draw on “meeting insights, documents, and communications, with governed access”. HP’s Anneliese Olson described scanning a document at an HP printer and having Copilot summarise, translate or redact it. Miro’s Jeff Chow said customers bring “real-time Microsoft 365 Copilot context directly onto the visual collaborative Miro canvas”. The post’s partner graphic also shows Darwinbox and Kore.ai.

None of the three quotes carries a figure, and none says which Work IQ interface the integration uses. Microsoft offers MCP, REST and agent-to-agent protocols. No customer in these posts says it runs on the MCP server specifically.

Guardrails and limits

Four layers sit between an agent and the data: Entra sign-in, OAuth permissions, the signed-in user’s own Microsoft 365 permissions and a tenant policy written in Rego, the Open Policy Agent language. Microsoft says every tool invocation is logged. The SharePoint preview adds two scopes, WorkIQ.Read for searching and reading and WorkIQ.Act for creating, updating or moving content. An agent that holds only the older WorkIQAgent.Ask permission doesn’t see SharePoint paths.

Four stacked checks: Entra sign-in, OAuth scopes, user permissions, tenant policy; every tool call logged
An agent clears four checks before it can change anything, and writes are blocked until an admin allows them.

Writes are off by default. The policy blocks create, update, delete and action requests, including sending email, until an admin enables them. In the initial release the policy is a tenant-wide on or off switch in the Microsoft 365 admin center, and per-user, per-app or per-agent templates aren’t part of it.

The tool reference sets hard edges. Collection reads default to 25 items with a cap of 100, and the $skip parameter is blocked. Chat messages come back 10 at a time. Raw file downloads default to 4 MB. get_schema and search_paths cover Microsoft Graph v1.0 only. Microsoft says it’s working with the MCP community on a standards-based way to move large files.

Several pieces aren’t generally available yet. The retrieve tool and the SharePoint tools are in public preview, and so is Work IQ in Copilot Studio. Billing is usage-based in Copilot Credits, independent of Microsoft 365 Copilot licensing, with a fixed component for Tools and a variable one for Chat and Context. Admins set spending limits in the admin center, and Microsoft’s posts link to a licensing page for rates.

Three columns: generally available, preview, and Frontier or later, listing Work IQ features
The MCP server is generally available; several of the newest pieces are still preview or Frontier.

What’s next

Microsoft’s SharePoint team said it will share the roadmap for more SharePoint tools, richer skills and the large-file work at Ignite. The Work IQ sessions listed in the announcement fall on these New Zealand times: THR853, on people and org context, at 11:35 am on Wednesday 18 November; BRK210, “Engineering the Frontier Firm: How Work IQ Powers Copilot”, at 10:45 am on Thursday 19 November; and TT1659, “Work IQ in Copilot: Turning Work Context into Outcomes”, at 11:25 am on Friday 20 November.


Discover more from Sulat AI & Tech News

Subscribe to get the latest posts sent to your email.