NetDocuments + Microsoft 365: Reference Architecture for Legal

Posted in Document Management Software | Last updated on October 25, 2026 by Craig Bayer

A partner asks where the final version of the settlement agreement is. One associate says NetDocuments. Another says it’s in the Teams chat. A third has it attached in Outlook.

Sound familiar?

NetDocuments and Microsoft 365 aren’t competing products. They’re two halves of the same setup, and each one has a job. The trouble starts when nobody decides which system owns what — so everything ends up everywhere.

Here’s the reference architecture we use for NetDocuments and Microsoft 365 at law firms: what lives where, and why.

Full disclosure: Optiable is a NetDocuments shop. We don’t sell or implement any other DMS.

Microsoft Runs the Office. NetDocuments Holds the Record.

That’s the whole architecture in one line. People sign in, send email, write, and talk in Microsoft 365. NetDocuments is where the firm’s client work lives — profiled to a client and matter, versioned, secured, and searchable.

Job Microsoft 365 NetDocuments
Sign-in and MFA Microsoft Entra ID Trusts Entra ID through single sign-on
Email delivery Exchange Online —
Email as part of the client file — Filed to the matter with ndMail or the M365 Add-in
Writing and editing Word, Excel, PowerPoint ndOffice saves, versions, and profiles it
Final client documents — Cabinet → Workspace
Chat and meetings Teams Matter files reached from inside Teams
PST, ZIP, and video files SharePoint (firm site) Linked back into the matter
AI Copilot ndMAX, or a direct connection to Claude

Every section below is one row of that table.

1. Identity: Microsoft Entra ID Is the Front Door

Your users already sign in to Microsoft 365 every morning. NetDocuments should use that same sign-in, not a second password.

NetDocuments supports single sign-on with Microsoft Entra ID (formerly Azure AD). Users click Use Organization’s Login, and Microsoft handles the rest — including MFA and whatever Conditional Access rules your IT team has in place.

Here’s why that matters:

  • One password – Users stop forgetting the NetDocuments one
  • One MFA policy – Set it in Entra ID, and it covers NetDocuments too
  • One place to shut the door – When someone leaves, disable them in Entra ID and they’re out of NetDocuments at the same time

Microsoft’s setup guide is here: Microsoft Entra SSO integration with NetDocuments.

2. Email: Exchange Delivers It. NetDocuments Files It.

Exchange Online’s job is getting the email from point A to point B. It is not the client file.

An email about a matter is part of that matter, the same as a letter or a pleading. It gets filed to NetDocuments, profiled to the client and matter, where the whole team can find it — not left sitting in one attorney’s mailbox.

  • Outlook Classic – ndMail, installed with ndOffice
  • New Outlook, Outlook on the web, and Outlook mobile – the NetDocuments M365 Add-in

For how firms should handle filing day-to-day, see Saving Email to a DMS: Best Practices.

3. Documents: Word Edits. NetDocuments Saves.

Users keep working in desktop Word, Excel, and PowerPoint. Nothing about that changes.

ndOffice sits on top of Office and changes where the file goes. ndSave saves to NetDocuments with a client, matter, and Doc Type. ndOpen opens from NetDocuments. While a document is open, ndOffice keeps a working copy in the Echo folder on the user’s computer and checks it back in when they’re done.

The result is one copy of the document, with every version, in the matter where it belongs. Not one in NetDocuments, one on the desktop, and one in someone’s Downloads folder.

4. Teams: Talk There. File Here.

Teams is great for conversation. It’s a lousy place to keep the client file.

When someone drops a file into a Teams channel, it doesn’t go to NetDocuments. It goes to the SharePoint site behind that team. No client and matter, no Doc Type, no NetDocuments security, and it won’t show up when someone searches the matter.

If the final version of a client document lives in a Teams chat, it doesn’t live anywhere.

NetDocuments has a Teams app, so users can access matter files and share them from within Teams. That’s the right pattern: the conversation happens in Teams, and the document stays in NetDocuments.

5. SharePoint: The Overflow Tank, Not the DMS

Your firm already has a SharePoint site. Every Microsoft 365 business plan with SharePoint gives the firm 1 TB, plus 10 GB per licensed user.

For a 40-user firm: 1 TB + (40 × 10 GB) = 1.4 TB. Most firms barely touch it.

That’s where PST files, ZIP files, and videos belong. NetDocuments can’t search inside any of them — only the name — so storing them in NetDocuments buys you nothing but a storage bill. Put them in the firm’s SharePoint site and link them back into the matter so they still show up where everyone expects them. The step-by-step is in Stop Storing PST, ZIP, and Video Files in NetDocuments.

What SharePoint should not be is a second DMS. If you’re weighing that idea, read SharePoint vs NetDocuments for Law Firms first.

6. AI: Decide How It Gets to Your Documents

AI is only as useful as the documents it can reach, and your documents are in NetDocuments. So the question is how the AI gets in.

  • Copilot – Microsoft’s assistant, built into Microsoft 365. I compared it to NetDocuments’ own AI in NetDocuments vs Microsoft 365 Copilot.
  • Claude – The real way to use Claude with NetDocuments is upgrading to AI 300 (ndMAX Enterprise) and connecting NetDocuments directly to Claude. Do it on a Claude Team or Enterprise account — not individual plans like Pro or Max. Here’s how to connect Claude to NetDocuments.

Whichever you pick, the AI comes to NetDocuments. Your documents don’t get copied out to the AI.

The Bottom Line

Microsoft 365 runs the office: sign-in, email, editing, chat, and overflow storage. NetDocuments holds the record: every client document and every filed email, profiled to a matter, versioned, and secured.

Draw that line once, tell your users where it is, and stop finding settlement agreements in Teams chats.

Need Help?

Not sure where the lines should be drawn at your firm — or untangling a setup where they never were? We can map your Microsoft 365 and NetDocuments environment and tell you what should live where, usually in a single call.

Schedule a free consultation at go.oncehub.com/optconsult.


Craig Bayer is the founder and leader of Optiable, an award-winning document management (DMS) consulting firm dedicated to helping law firms seamlessly integrate NetDocuments. Specializing in firms with 10 to 150 users, he has rolled out NetDocuments for over 600 law firms across the United States and Canada since 2010.

CONNECT WITH CRAIG → linkedin.com/in/craigbayer

About the Author

Craig Bayer is the founder and leader of Optiable, an award-winning document management (DMS) consulting firm dedicated to helping law firms seamlessly integrate NetDocuments. Specializing in firms with 10 to 150 users, he has successfully guided over 500 law firms across the United States and Canada through NetDocuments implementations since 2010.

With deep expertise in the legal industry, Craig has a proven track record of optimizing technology to meet the unique needs of law firms. His certifications include industry-leading tools such as Amicus Attorney, Centerbase, Clio, PCLaw, HotDocs, TimeMatters, Soluno, and Worldox, enabling him to deliver comprehensive solutions tailored to each client’s workflow and goals.

Craig Bayer