NetDocuments Microsoft 365 Integration: New Add-In, Word Co-Authoring and Copilot Access

This piece relies on LawSites' summary of the interview, not a transcript. Hauck's own words and nuances are attributed to that summary. Vendor claims are labeled as vendor claims.

What LawSites reports from the interview​

NetDocuments is rolling out a completely redesigned user experience, a new Microsoft 365 integration and real-time co-authoring. Hauck explains why customers can switch freely between the old and new experiences with no forced migration. He also explains how the new M365 add-in replaces legacy desktop integrations, so lawyers can work across Windows, Mac and mobile devices.

The summary also says he covers:

• General availability of tabular review.
• Document generation and redlining in the NetDocuments assistant.
• Interactive HTML reports.
• A beta MCP connector with Legora, joining existing connectors to Claude, ChatGPT, Copilot and others.

The full roster of connectors and their beta status rest on LawSites' account. NetDocuments' own materials confirm a Copilot connection and a Legora demonstration. They don't confirm every detail in that list.

The classic and new interfaces run side by side​

The "no forced migration" point has a paper trail. When NetDocuments announced the redesign in May, LawSites reported that the new platform launches alongside the existing interface, not as a replacement. The report added that both run on the same data and governance model. That arrangement lets IT run a pilot without committing the whole firm.

The Inspire agenda also lists a session on how the two experiences will evolve side by side. It frames the goal as making the transition feel deliberate rather than disruptive.

NetDocuments' Inspire recap says the new experience is meant to be consistent across the web, its Microsoft 365 add-ins and the mobile app. It mentions a reimagined home page, favorites, recents, a left menu and dark mode. It does not give a rollout schedule or confirm general availability for each item.

The Microsoft 365 add-in: the part admins should read twice​

The LawNext summary says the new add-in replaces legacy desktop integrations. Separate reporting, from a WindowsForum.com news thread covering the Inspire announcements, is more specific. It says the add-in has no desktop component and replaces ndOffice and ndClick on both Windows and Mac. It also reportedly keeps co-authored documents inside NetDocuments. That thread is secondary reporting, so verify it against NetDocuments' own deployment documentation.

If you manage an environment with the older integrations, the practical checklist looks like this:

• Decide who owns add-in deployment in your Microsoft 365 tenant. The thread refers to Integrated Apps.
• Pilot before decommissioning. The same thread advises keeping ndOffice in place until a pilot confirms the add-in does what users need.
• Test co-authoring with documents shared with clients or outside counsel.
• Confirm behavior on Windows, Mac and mobile separately. The source material doesn't establish a detailed compatibility matrix, licensing terms or regional limits.

NetDocuments' Microsoft integration page uses future-tense wording for some co-authoring plans. It says the company will be expanding co-authoring to include real-time desktop co-authoring in Word, Excel and PowerPoint. That page doesn't establish which features every customer has today. In May, LawSites described a narrower scenario: documents stored in NetDocuments can be opened directly in Word for real-time co-authoring. It also described an AI editing tool inside Word that draws on matter context.

The Legal Context Graph, and the cost claim​

The graph is described as proprietary knowledge infrastructure that continuously maps relationships among every matter, document, communication and person in a firm's repository. In May, NetDocuments described indexing at three levels: the document, the matter and the global firm level. The company says it preserves existing permissions and ethical walls.

The number that will draw attention is cost. NetDocuments says it kept the model, AI tool and questions constant and changed only the structured context. In its Inspire recap, it says that on a top-tier model the cost per correct answer fell by half with no loss in quality. It estimates savings of nearly $1 million a year for an organization of 2,000 professionals. A separate NetDocuments post on the Copilot connection gives a more specific figure: the cost per correct answer dropped 48% while answer quality held steady.

Treat these as vendor-reported results. The materials reviewed don't give the full methodology, sample size, model identity, token pricing or independent replication. The "$1 million" figure is an estimate for one organization size. It isn't a measured outcome.

Legal IT Insider offered a measured view at launch. It called the "first-ever" framing the kind of claim vendor launches tend to make. It noted that Hauck acknowledged the company had been enriching documents for some time and had now expanded that work with graph capabilities.

Availability is another caution. The May launch was a private preview for select customers on the enterprise AI tier. NetDocuments' October recap still describes the graph as making an impact at customer sites in private preview. Don't assume broad availability.

MCP, Copilot and governance​

On September 30, NetDocuments announced it connects to Microsoft Copilot through the Model Context Protocol (MCP). The company says MCP gives supported tools a consistent way to work with organizational knowledge and existing access controls. At announcement it was available to ndMAX Enterprise customers.

The company's governance claims are specific:

• Every interaction runs under the user's own NetDocuments credentials.
• Ethical walls, matter-level restrictions and access controls apply.
• Data loss prevention, retention policies and audit trails carry through.
• Admins can switch the connection on or off with a single toggle.
• Documents stay in NetDocuments.

The Inspire recap adds that AI-exclusion policies apply and that each request leaves an audit trail. It also reports Legora demonstrating a new MCP connection, with NetDocuments permissions deciding what each lawyer can see.

These are company descriptions. Different connectors may not share identical controls, so IT should check product-specific documentation. Test with a restricted matter and a user who shouldn't see it. Then confirm in the audit logs that the request was recorded and the content was withheld.

The WindowsForum.com thread reports that NetDocuments' Scott Kelly said an external agent's authorship is recorded in document history. It also reports that partner tools cannot write into the graph itself. That is secondhand, so confirm it before relying on it.

Why keep building an interface if MCP lets users work elsewhere?​

LawSites says Hauck addresses this question directly, along with how smaller and midsized firms can benefit without dedicated knowledge management staff. The summary doesn't give his answers, so I won't invent them. There are two plausible readings, both from general industry logic and neither attributed to Hauck:

• A governed interface is where AI-generated work gets reviewed and recorded.
• MCP is a hedge against the lawyer who prefers Copilot, ChatGPT or Legora as their front door.

Takeaways for IT​

• Pilot, don't flip. The classic interface remains available, so the redesign can be tested with a small group.
• Audit the add-in plan. If the add-in replaces ndOffice and ndClick, map who has what installed today and who owns tenant deployment.
• Verify the benchmark. The 48% and "half" figures are the vendor's. Ask for methodology before building a business case.
• Test governance. Permissions, ethical walls and audit trails are claimed to carry through MCP. Prove it in your tenant.
• Check licensing. The Copilot connection was announced for ndMAX Enterprise customers, and the graph preview was tied to the enterprise AI tier.

In short, this interview is a product-strategy conversation. The details that matter to Microsoft 365 admins are the add-in replacement, co-authoring in Word and the Copilot MCP connection. All of them should be validated against NetDocuments' current documentation before rollout.