NetDocuments and Microsoft 365: what works, what doesn't

NetDocuments is a cloud-native document management system for matter documents; Microsoft 365 storage handles everything else in the firm (precedents, templates, marketing, internal comms, HR, project workspaces). Most firms end up running both, and they coexist cleanly in well-configured deployments. The trouble starts when the OneDrive sync client is quietly configured (usually by default) to sync the same folders NetDocuments' local components use for checked-out documents and email filing. This piece walks through the specific pitfalls, the fix patterns that keep the two systems out of each other's way, and how Cloud Drive Mapper gives fee-earners the mapped-drive experience they know from a DMS, applied to Microsoft 365 storage.

What breaks when NetDocuments and the OneDrive sync client collide?

NetDocuments is more cloud-native than a traditional on-premises DMS, so its collision surface with OneDrive is smaller than iManage's. But it exists, and five specific patterns show up regularly.

ndOffice's local cache gets swept into OneDrive sync

NetDocuments' ndOffice add-in caches checked-out documents locally during editing so Word, Excel and PowerPoint can operate on them at native speed. If that cache folder lives inside a OneDrive-synced Documents folder (common after Known Folder Move enrolment), OneDrive tries to sync every checked-out matter document as it happens. "Conflict copy" files appear for matter documents that should only exist inside NetDocuments.

ndMail Outlook filing produces duplicates or hangs

ndMail files emails from Outlook into NetDocuments matter workspaces. It uses temp files in the user profile during that process. If Outlook's temp folder or the working file location is OneDrive-synced, filing operations can hang, fail silently, or file the same message multiple times as OneDrive interferes with the intermediate files.

ndSync offline copies double up with OneDrive

ndSync gives fee-earners offline access to selected matter documents. If OneDrive is simultaneously syncing the same content (rare but happens when firms have not cleanly separated the DMS side from the general storage side), you get two competing offline stores, each trying to reconcile changes back to different back-ends. The fee-earner's laptop becomes a source of confusion instead of a source of productivity.

Templates and precedents fail to load under Files On-Demand

Fee-earners regularly open template documents or precedent files from shared SharePoint libraries while NetDocuments is mid-checkout. If those files live on OneDrive with Files On-Demand and have not been hydrated recently, the open request can time out or fail before the sync client pulls the file down. Users experience this as unreliability that is hard to attribute to any one system.

SharePoint isn't accessible in a way fee-earners recognise

The SharePoint browser experience and the OneDrive desktop client are not the drive-letter, folder-hierarchy view fee-earners have used inside NetDocuments for years. Even when the M365 side of the firm's storage is configured correctly, users find it awkward and default back to emailing documents to themselves or storing them in NetDocuments where they do not belong. Adoption of the SharePoint tier suffers, and NetDocuments accumulates content that should have lived elsewhere.

Why NetDocuments and the OneDrive sync client don't naturally coexist

Both systems are trying to be authoritative about the same class of thing: a document, its versions, its lock state, its cache. Neither was designed with the other in mind. NetDocuments has stronger cloud-native discipline than a legacy on-prem DMS, which reduces the collision surface, but the collision surface is not zero. Where they overlap, each thinks it owns the file lifecycle and they trip each other up.

Add the drive-letter mismatch on top: NetDocuments presents documents through its own DMS UX (browser or ndOffice-in-Word) that fee-earners are trained on; OneDrive presents documents through Explorer folders and browser tabs. Two UX patterns for what looks like the same task is friction, and firms end up with fee-earners who quietly ignore whichever system they did not master first.

For the broader take on why sync clients struggle with applications that assume they own the filesystem, see Desktop applications and real file paths. The same underlying pattern affects the wider category of DMS, ECM and matter-management tools that maintain their own local components. Our iManage and Microsoft 365 piece covers the same terrain for firms running on iManage.

What are the fix options?

Three approaches. The first two are boundary-setting; the third is the drive-mapping approach this page is about.

Carefully configure OneDrive to skip NetDocuments folders

Set OneDrive selective sync (and Known Folder Move exclusions) to leave ndOffice's local cache, ndMail's temp locations and ndSync's offline folders alone. Effective when done meticulously, and fragile because a new user setup, a profile migration or a Windows update can reintroduce the overlap silently. Works best in tightly-managed environments where IT retains firm control of user profile configuration.

Move non-DMS content to SharePoint but skip the OneDrive desktop client

Store non-matter content in SharePoint libraries. Have fee-earners access those libraries through the browser or through Teams. Avoids the sync-client conflicts entirely. The trade-off is UX: the browser view does not match the mapped-drive muscle memory fee-earners have from NetDocuments, and adoption of the SharePoint tier typically lags.

Use a drive-mapping approach (Cloud Drive Mapper)

Present SharePoint document libraries as real Windows drive letters. Fee-earners get the mapped-drive view they know from a DMS, applied to the firm's non-matter Microsoft 365 content. No sync client is involved, so nothing overlaps with ndOffice, ndMail or ndSync.

How Cloud Drive Mapper fits with NetDocuments

CDM is not a DMS. It does not replace NetDocuments' matter structures, ethical walls, DMS-grade full-text search or the workflow and security controls the platform is built around. Where CDM fits is on the non-DMS side of the firm's storage.

Coexistence: SharePoint as a mapped drive alongside NetDocuments

Most firms run CDM alongside NetDocuments. NetDocuments owns matter content and everything that goes with it; CDM gives fee-earners a drive-letter view of SharePoint document libraries for everything else. The two systems never touch the same files, and there is no OneDrive sync client to interfere with either.

Because CDM does not use a local cache the way OneDrive does, ndOffice's checkout cache, ndMail's Outlook temp locations and ndSync's offline stores are unaffected by CDM being installed on the endpoint. Everything OneDrive struggles with in a NetDocuments deployment is a non-issue.

Client-facing SharePoint workspaces alongside matter DMS

Some firms operate client-facing SharePoint workspaces for prospect materials, transactional deal rooms, or shared project spaces that do not warrant a full DMS matter record. CDM presents those workspaces as mapped drives for the firm's own users, while clients reach the same content through SharePoint guest access in the browser or Teams (CDM is only for users in your own Microsoft 365 tenant). The DMS keeps handling matter documents; SharePoint handles the shared-workspace layer; CDM makes the SharePoint side feel like a DMS to users.

Hybrid: NetDocuments plus M365 plus CDM

The common current pattern in NetDocuments firms. NetDocuments Cloud handles the matter DMS; SharePoint handles precedents, templates, marketing, internal comms; CDM presents SharePoint as mapped drives. Fee-earners have two workflows (NetDocuments for matters, mapped drive for everything else), each clean and unambiguous.

NetDocuments-specific configuration notes

Nothing exotic is required. Install CDM as normal and map SharePoint document libraries to the drive letters the firm uses (typically M:, N:, or similar). Fee-earners do not need to change how they work with NetDocuments itself; the mapped drive appears in Explorer and File Open/Save dialogs alongside their NetDocuments Web tab or ndOffice-in-Word workflow.

If your firm is moving away from OneDrive Known Folder Move, unenrol users cleanly before deploying CDM. If KFM is being retained for personal OneDrive space, ensure ndOffice cache, ndMail temp locations and ndSync offline folders are excluded from KFM's Desktop, Documents and Pictures redirection.

CDM supports NetDocuments-adjacent workflows in the following deployment models:

• Windows desktops (direct)
• Citrix Virtual Apps and Desktops
• Citrix DaaS
• Azure Virtual Desktop (AVD)
• Windows 365 Cloud PC
• Omnissa Horizon (formerly VMware Horizon)

Cloud Drive Mapper is used across law firms and legal departments to give fee-earners the mapped-drive experience they know from a DMS, applied to Microsoft 365 storage.

Frequently asked questions

Does Cloud Drive Mapper replace NetDocuments?

No. CDM is drive-mapping middleware for Microsoft 365 storage, not a document management system. It does not provide matter-based folder structures, ethical walls, DMS-grade full-text search across the matter corpus, version history, or the workflow and security controls NetDocuments is built around. CDM sits alongside NetDocuments on the non-DMS side of the firm's storage.

Does Cloud Drive Mapper work alongside NetDocuments Cloud?

Yes. NetDocuments Cloud handles matter content and everything the firm has structured inside it; CDM handles everything else the firm stores in Microsoft 365 (precedents, templates, marketing, internal comms, HR, ops). The two systems operate on separate content and do not interfere with each other. Most CDM-in-legal deployments run alongside a DMS in some form.

Will CDM interfere with ndOffice, ndMail or ndSync?

No. CDM does not maintain a local sync cache and does not touch NetDocuments' local components. ndOffice's checked-out document cache, ndMail's Outlook filing operations, and ndSync's offline copies of matter documents are all unaffected by CDM being installed on the endpoint. The two systems operate in different scopes: NetDocuments handles matter content locally where needed; CDM streams Microsoft 365 content on demand.

Can CDM present matter documents from SharePoint as a mapped drive?

Yes, when those matter documents live in SharePoint. Some firms use NetDocuments for their core matter DMS and SharePoint for adjacent client work that does not warrant a full DMS record (client-shared folders, prospect materials, project workspaces). CDM presents those SharePoint sites as Windows drive letters. NetDocuments' own matter documents are best accessed through NetDocuments; CDM is not designed to sit between them.

Does CDM work with the NetDocuments Web experience?

Yes. CDM does not touch NetDocuments' browser experience. The NetDocuments Web app runs in the browser as it always has; CDM provides mapped drive letters for Microsoft 365 storage on the same Windows session. Fee-earners can move between the NetDocuments browser tab and their SharePoint mapped drives freely, and neither impacts the other.

Which locking model does CDM use for SharePoint documents?

SharePoint's native check-out. When a fee-earner opens a document from a CDM-mapped drive, CDM triggers a SharePoint check-out automatically. A second user opening the same document sees it as checked out and receives a read-only copy. This mirrors the exclusive-lock model NetDocuments users are already familiar with from their DMS.

Related solutions

• iManage and Microsoft 365: what works, what doesn't (the same pattern for the other major legal DMS)
• Desktop applications and real file paths (the underlying problem class)
• OneDrive for Business in Citrix (many firms run DMS + M365 over Citrix)
• Replacing your file server with SharePoint
• Overcoming the OneDrive 300,000 file sync limit (matter archives frequently hit this)
• Cloud Drive Mapper for legal and professional services

← Back to all solutions