Better method for archiving users ; Unique Retention Policy or Litigation Hold?

%3CLINGO-SUB%20id%3D%22lingo-sub-1544192%22%20slang%3D%22en-US%22%3EBetter%20method%20for%20archiving%20users%20%3B%20Unique%20Retention%20Policy%20or%20Litigation%20Hold%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1544192%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20identify%20the%20best%20option%20for%20creating%20a%20standardized%20policy%20for%20keeping%20all%20my%20term'd%20employee%20OneDrive%20and%20Exchange%20data%20on%20an%20indefinite%20hold%2C%20without%20using%20up%20an%20M365%20license.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20read%20recommendations%20regarding%20creating%20dedicated%20Retention%20Policies%2C%20and%20other%20postings%20where%20the%20recommendation%20is%20to%20put%20the%20user's%20account%20on%20a%20Litigation%20Hold.%3CBR%20%2F%3E%3CBR%20%2F%3EWhich%20tends%20to%20be%20the%20more%20standardized%20method%20for%20archiving%20and%20holding%20terminated%20user%20data%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1544192%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELitigation%20Hold%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERetention%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1545621%22%20slang%3D%22en-US%22%3ERe%3A%20Better%20method%20for%20archiving%20users%20%3B%20Unique%20Retention%20Policy%20or%20Litigation%20Hold%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1545621%22%20slang%3D%22en-US%22%3E%3CP%3E-ERR%3AREF-NOT-FOUND-%40Robert%20Gordon%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERetention%20Policies%20are%20now%20the%20Microsoft%20default%20best%20practice%20for%20this%20sort%20of%20thing%20over%20Holds%20and%20eDiscovery%2C%20so%20I%20would%20recommend%20these%20first.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20I%20do%20personally%20tend%20to%20prefer%20more%20definitive%20action%20on%20terminated%20users%2C%20where%20the%20mailbox%20is%20converted%20to%20shared%20and%20delegate%20access%20granted%20as%20required%2C%20As%20for%20OneDrive%20data%2C%20this%20is%20more%20challenging%20if%20you%20are%20using%20AD%20sync%2C%20but%20when%20deleting%20a%20cloud%20only%20user%20object%20you%20may%20convert%20the%20mailbox%20to%20shared%20as%20part%20of%20the%20process%20and%20also%20grant%20a%20delegate%2030%20days%20access%20to%20the%20OneDrive%20before%20it%20is%20deleted.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

I am trying to identify the best option for creating a standardized policy for keeping all my term'd employee OneDrive and Exchange data on an indefinite hold, without using up an M365 license.

 

I have read recommendations regarding creating dedicated Retention Policies, and other postings where the recommendation is to put the user's account on a Litigation Hold.

Which tends to be the more standardized method for archiving and holding terminated user data?

1 Reply
Highlighted

@OneTechBeyond 

 

Retention Policies are now the Microsoft default best practice for this sort of thing over Holds and eDiscovery, so I would recommend these first.

 

However, I do personally tend to prefer more definitive action on terminated users, where the mailbox is converted to shared and delegate access granted as required, As for OneDrive data, this is more challenging if you are using AD sync, but when deleting a cloud only user object you may convert the mailbox to shared as part of the process and also grant a delegate 30 days access to the OneDrive before it is deleted.