Ran into this recently with a client and wanted to share a short technical note so that you can avoid the headache. Many clients use shared subfolders in Teams/SharePoint to stage internal collections from document systems, 3rd parties or other non-M365 sources. Direct load to RelativityOne, Reveal or other cloud platform requires integration and security configuration. So many practitioners are still stuck downloading to local storage and then upload/process. While Microsoft formally increased the maximum SPOD download to 250 GB last July, users (like myself) have encountered issues with much smaller downloads (~20GB) crashing out. There is also a 400 character path limit that is easy to hit with complex folder structures. The most important note is that my client got NO errors on the zip truncation and the file processed on their eDiscovery platform even though it was corrupt. So incomplete downloads can slide through your workflow without good QC.
Microsoft recommends using the local synchronization option for a more transactional process, but since you cannot get file or size counts from a document library, how do you know it is complete?
My preferred approach is to use eDiscovery tools for eDiscovery requests. That is not always possible or practical in heavily secured client environments. I solved this using Purview eDiscovery to search/export based on the DocumentLink: property in a KeyQL search after a LOT of testing. While the documentation makes it look simple the syntax does not exactly match up in the tenants I have tested. I recommend targeting just the specific SP/Teams Group site for search performance.
Original test folder “SPDOCLINKtest” URL in my test web SharePoint:
https://edjgroupinc.sharepoint.com/sites/testTeamsPremium-SharedChannelTest/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2FtestTeamsPremium%2DSharedChannelTest%2FShared%20Documents%2FSPDOCLINKtest
Original test folder “SPDOCLINKtest” link copied via UI:
https://edjgroupinc.sharepoint.com/:f:/s/testTeamsPremium-SharedChannelTest/EinJvQDTqTxFvJSd9b_KGl0BoYONHHIFGFj0jdMxZaAv_A?e=9zOni4
Sharing link (existing access only):
https://edjgroupinc.sharepoint.com/:f:/r/sites/testTeamsPremium-SharedChannelTest/Shared%20Documents/SPDOCLINKtest?csf=1&web=1&e=pel0D5
Successful Reformat for KeyQL formatted target:
DocumentLink:“https://edjgroupinc.sharepoint.com/sites/testTeamsPremium-SharedChannelTest/Shared Documents/spdoclinktest*”
You may notice many subtle differences and the restoration of spaces and backslashes. In the end, the DocumentLink property in KeyQL did work to get known file count test folders. The recommended Path: property did NOT work in my tests, but I am sure it works for someone out there. I sincerely hope that this quick tech note saves someone the time and frustration I burned on my Sunday off. Purview seems to be a constantly moving target that outpaces documentation and published community testing. I do not envy the PM teams being pressured to innovate and answering to legal users demanding consistency. I invite you all to share your own Microsoft 365 and Purview gotchas under your own name or I am happy to give you anonymity to support the community.
Greg Buckles wants your feedback, questions or project inquiries at Greg@eDJGroupInc.com. Book a free 15 minute ‘Good Karma’ call if he has availability. He solves problems and creates eDiscovery solutions for enterprise and law firm clients.
Greg’s blog perspectives are personal opinions and should not be interpreted as a professional judgment or advice. Greg is no longer an investigative journalist and all perspectives are based on best public information. Blog content is neither approved nor reviewed by any providers prior to being published. Do you want to share your own perspective? Greg is looking for practical, professional informative perspectives free of marketing fluff, hidden agendas or personal/product bias. Outside blogs will clearly indicate the author, company and any relevant affiliations.
Greg’s latest nature, art and diving photographs on Instagram. (the latest turtle video is cool!)