In this second article of our series addressing discovery challenges associated with pointers, i.e., “modern attachments” in the Microsoft 365 (“M365”) ecosystem, we turn to preservation. When it comes to preservation, pointers are not the problem; they are easy to preserve as part of the sent message.
The problem with preservation pertains to referenced content and whether organizations need to retain “as sent” versions of content referenced in messages with pointers. We explained in our previous article that no family relationship exists between messages with pointers and referenced content; thus, there is no duty to retain “as sent” versions of referenced content (where that is even possible) to ensure those versions are available for preservation at some later date.
This content has been archived. It is available through our partners, LexisNexis® and Bloomberg Law.
To view this content, please continue to their sites.
Not a Lexis Subscriber?
Subscribe Now
Not a Bloomberg Law Subscriber?
Subscribe Now
LexisNexis® and Bloomberg Law are third party online distributors of the broad collection of current and archived versions of ALM's legal news publications. LexisNexis® and Bloomberg Law customers are able to access and use ALM's content, including content from the National Law Journal, The American Lawyer, Legaltech News, The New York Law Journal, and Corporate Counsel, as well as other sources of legal information.
For questions call 1-877-256-2472 or contact us at [email protected]
