All signals
AI Tools|22 Jul 2026

Microsoft 365 quietly opened its Model Context Protocol agents to Word, Excel, PowerPoint, Outlook, and Catalyst on 15 July, letting any MCP-built agent run inside the apps staff already use daily.

Microsoft 365 quietly opened its Model Context Protocol agents to Word, Excel, PowerPoint, Outlook, and Catalyst on 15 July, letting any MCP-built agent run inside the apps staff already use daily.

Why It Matters

Until now, an MCP agent your team built or bought lived in its own tool or the Copilot Studio test pane, one more window to switch to. From 15 July it can answer and act from inside the Copilot pane in Word, Excel, PowerPoint, Outlook, or Catalyst, so a custom agent that reads your CRM or pulls stock levels shows up exactly where the work already happens. For an SMB that has been hesitant about agent sprawl, this narrows the gap between building an agent and staff actually using it.

What To Do About It

If you or your MSP have already built or piloted an MCP agent, test it inside Word or Outlook this week, the integration may already be live on your tenant. If you have not built one yet, this is the moment to scope a single high-value use case, such as an Outlook agent that drafts replies from your knowledge base, rather than a broad agent platform.

model context protocolmcp agentsmicrosoft 365 copilotoffice appsagent adoption

Weekly intelligence, Friday mornings.

The week's top AI signals decoded for business leaders. No fluff.

Related Signals