Adding Legacy Data to Microsoft

Adding Legacy Data to Microsoft Purview Adds Hidden Risk: eDiscovery Trends

Did you know that adding legacy data to Microsoft Purview adds hidden risk? Shelley Bougnague of Cloudficient discusses that here!

As discussed in her post titled (wait for it!) The Hidden Risk of Adding Legacy Data to Microsoft Purview (available here), Shelley discusses how, in practice, Purview was not designed to absorb decades of historical email, chat, and collaboration data without consequence. More importantly, it was never intended to retroactively govern data created under entirely different rules, policies, and business norms.

Here are a couple of key takeaways to note about Purview:

Advertisement
Veracity Forensics
  • Microsoft Purview is designed to govern active Microsoft 365 data, not decades of historical email, chat, and collaboration content.
  • Ingesting legacy data into Purview can trigger false positives, alert fatigue, and misleading compliance signals

What does that mean? As Shelley notes in this post, among other things, it means that Purview eDiscovery performance can grind to a halt once large volumes of legacy journal data are introduced. Searches that once took minutes now take hours or days. Case setup stalls. Legal timelines slip. Costs rise.

This isn’t a tuning issue. It’s a structural problem rooted in how Microsoft 365 handles retention, indexing, and discovery, combined with how legacy email archives were historically designed.

So, what else is Purview not designed to do with legacy data? And how does Microsoft Purview indexing actually work? Find out here and here, it’s only one, er, two clicks! So much useful info, just one click won’t do! 😉

So, what do you think? Is your organization finding Microsoft Purview challenging? Please share any comments you might have or if you’d like to know more about a particular topic.

Advertisement
Casepoint

Image created using Microsoft Designer, using the term “robot lawyer frustrated with his computer”.

Disclosure: Cloudficient is an Educational Partner and sponsor of eDiscovery Today

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by my employer, my partners or my clients. eDiscovery Today is made available solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Today should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.


Discover more from eDiscovery Today by Doug Austin

Subscribe to get the latest posts sent to your email.

Leave a Reply