iManage Connector for Microsoft Copilot Chat: What’s Changed?

The AI integration landscape around iManage continues to move quickly.

Following our recent OIA Advisory on iManage, MCP and the evolving AI ecosystem, iManage has provided further clarification around its integration with Microsoft Copilot Chat and Copilot Cowork.

The latest update simplifies what had appeared to be two separate connector experiences into a more consolidated approach.

What has changed?

Previously, there appeared to be separate paths for the Federated Connector and the iManage Copilot integration.

iManage has now clarified that the Federated Connector has been consolidated into a single iManage connector, managed through the iManage Cowork plug-in.

Importantly, this doesn't mean customers need to actively use Copilot Cowork.

Instead, the Cowork plug-in is intended to serve as the central connector for iManage across both Microsoft Copilot Chat and Copilot Cowork.

What does this mean for iManage customers?

The update makes the direction of the integration clearer, but it also highlights just how quickly the Microsoft and iManage AI ecosystems are evolving.

For organisations exploring iManage with Microsoft Copilot, the key takeaway is to stay informed and remain flexible.

These technologies and integration models are still developing. Rather than becoming too committed to one particular implementation model, organisations should continue focusing on the fundamentals: governed access to knowledge, information architecture, AI readiness and identifying practical use cases.

The bigger picture

This update doesn't change the broader message from our previous advisory.

MCP (Model Context Protocol) remains an important part of the evolving iManage AI ecosystem, while the ways users actually access that governed knowledge through Copilot, Cowork, agents and other AI experiences continue to develop.

For iManage customers, it's another reminder that the AI landscape isn't standing still.