Microsoft previews Work IQ MCP for agents

Microsoft previewed Work IQ MCP servers to give agents live Microsoft 365 context and governed tool access.

Microsoft has introduced Work IQ MCP as a preview feature for building agents that can use Microsoft 365 context, tools, and governance controls. The setup is aimed at Copilot Studio, Microsoft Foundry, Visual Studio Code, and the Microsoft 365 admin center, with access tied to a Microsoft 365 Copilot license.

What changed

Work IQ is Microsoft’s new intelligence layer for agents, built to ground responses in shared organizational context across files, mail, meetings, chats, and business systems. Microsoft says the system is organized into three layers - Data, Memory, and Inference - so agents can keep context across tasks, apps, and sessions.

The preview also adds a managed MCP tool catalog under Agent 365. Microsoft lists several first-party servers, including Work IQ Copilot, Calendar, Mail, SharePoint, OneDrive, Teams, User, Word, plus Dataverse and Dynamics 365 actions.

• Admins can allow or block MCP servers in the Microsoft 365 admin center.
• Tool calls are traced in Microsoft Defender for audit and troubleshooting.
• Agents can use scoped permissions and policy checks at runtime.
• Existing older Microsoft MCP connections remain supported.

For developers, Microsoft says the integration path runs through the Agent 365 SDK and CLI, Copilot Studio, Foundry, and direct API workflows in Visual Studio Code. The company also says the servers are tested for accuracy, latency, and reliability before broad use.

Why it matters

This is less about a single new connector and more about how Microsoft wants agents to operate inside enterprise controls. By putting MCP servers behind admin policy, permissions, and tracing, Microsoft is making tool use easier to govern in regulated environments.

That matters for teams building internal copilots, because the same agent can now pull work context and take actions without ad hoc integrations for each app. It also gives IT a central switch for access control, which may reduce the friction between developer speed and compliance review.

For the market, the preview shows Microsoft pushing MCP from a developer protocol into an enterprise operating model. The key question is whether customers adopt Work IQ as the default path for Microsoft 365 agents or keep mixing it with custom servers and third-party tooling.

The takeaway: Microsoft is packaging agent context, tool access, and governance into one preview, and that could shape how enterprise teams build on MCP inside Microsoft 365.