Lexis+ DMS integration with SharePoint

I'm currently supporting a firm which is piloting Lexis+ (with Protégé) as their first foray in the dedicated legal AI tooling. They are a full blown Microsoft outfit, and we've already built a few Copilot Studio PoCs for various workflows. One of the advertised features is DMS integration, which states it can draft, cite and extract from documents at the firm. Just prior to the AI push, a huge project was undertaken to move many of the documents to SharePoint. I'm very curious about what the requirements are, if there are documents type that supported/not supported, and just how comprehensive it's search is. Working with Copilot Studio it became very obvious that agents essentially ran a traditional SharePoint search behind the scenes, and just slopped what it wanted on top without context. It also has folder size and file size limits which are easily exceeded in a legal database, as well as very poor support for PDFs (advertised as working, but in practice it's very poor), amongst a slew of other limitations that don't become apparently until you start digging. There is zero documentation about how this works, beyond "[We will work with your IT and knowledge teams to ensure a smooth rollout, including the set-up of your preferred funnel settings, filters and teams.](https://www.lexisnexis.com/en-us/products/dms-integration.page)" I'm super skeptical... Does anyone out there have experience? The things I really want to know are: * Does Lexis lean on the SharePoint search results to identify documents for ingestion? * Does it lean on SharePoint to return content, or does it ingest documents itself? * Is it using RAG, semantic search, or something else to extract file contents? * For citation in Protégé, does it require a specific file structure to identify documents? How does it process the contents of those documents? * Is it subject to the same [size/type/recency limits](https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-unstructured-data) as other integrations as SharePoint? * What is it doing to "find the needle in a haystack" with massive document libraries of mixed content types? If anyone has any real-world information on how this works, it would go a long to building confidence in the product, and determining whether it's even worth investigation a DMS integration.