BlogGuide
Microsoft 365 Copilot can't connect to iManage
Keep Copilot and add Caddi: Caddi finds the repetitive filing and profiling in iManage, automates the high-volume steps through the API, hands the judgment calls to Copilot as an agent, and monitors both.
IManage is the document- and email-management system (DMS) most law firms run on.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
By Jason Alafgani
01Reaching it
Copilot stops at the edge of Microsoft 365.
It reaches your mailbox, files, Teams and SharePoint through the Microsoft Graph. iManage sits outside that boundary, so Copilot can't open a record there, let alone write one.
No native connector to iManage. Data goes in and out by hand, pasted.
Connects to iManage through its API, with scoped access the firm controls and every run logged.
02Running it
Helping a person is not the same as doing the work.
Copilot drafts and summarises in the app you're in. Legal staff file, profile, name, and retrieve documents and email in iManage all day, with strict workspace, security, and naming conventions. That is a workflow across three to six tools, and it has to run with nobody at the keyboard.
Assists one person in one app, while they drive.
Runs the high-volume work across iManage, Microsoft Outlook and Aderant as code, the same way every run. Work that needs judgment goes to Copilot as an agent.
03Governing it
Nobody can see what ran, or where.
Copy-paste and ad-hoc scripts break when a screen, a token or a login changes, and nothing tells the firm what ran, what failed, or what is still done by hand before the filing and profiling stops.
Credentials and scripts outside firm controls, fixed by whoever built them.
Caddi Govern monitors every Caddi run, and the work Caddi hands to Copilot reports each decision and API call back to it, in one firm-wide view: what is automated, where it runs, and what is still manual. Caddi is SOC 2 attested.
Caddi
See how Caddi AI Agents can run the high-volume work inside iManage and hand the judgment calls to Copilot
Frequently asked questions
Can Microsoft 365 Copilot connect to iManage?
Not in a governed, production-ready way. Copilot works within Microsoft 365 and reaches data through the Microsoft Graph; iManage is outside that boundary, so there's no native connector. You don't have to replace Copilot to fix it: Caddi connects to iManage directly, runs the high-volume work there, and hands judgment-heavy work to Copilot as an agent.
Do I have to choose between Copilot and Caddi?
No. Caddi Discover finds and ranks the repetitive work across iManage and your other systems, with evidence. Each finding is automated in Caddi or exported to Copilot as an agent, whichever is the better tool: Caddi for high-volume, high-accuracy work that has to run the same way every time, Copilot for individual, judgment-heavy work. Caddi Govern monitors every Caddi run and the work exported to Copilot, which reports each decision and API call back, in one firm-wide view.
How does Caddi connect to iManage?
Through a real iManage connection. Caddi reads and writes iManage as part of an automated workflow, with scoped, permissioned access and a run-by-run audit trail (Caddi is SOC 2 attested).
Do I need a developer to set this up?
No. You show Caddi the workflow over a screen share and Caddi builds and maintains the automation for you, including the iManage connection. There's no integration code for your team to write or keep running.
Is my client and matter data safe?
Yes. Caddi uses scoped, permissioned access and runs production work as deterministic code with a full audit trail. AI is used only at setup to understand the workflow, not to make decisions on every run, and Caddi is SOC 2 attested.