SOLVED

Retention disposition review vs delete

%3CLINGO-SUB%20id%3D%22lingo-sub-2157131%22%20slang%3D%22en-US%22%3ERetention%20disposition%20review%20vs%20delete%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2157131%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20anyone%20tell%20me%20what%20happens%20if%20you%20have%20the%20following%20scenario%20for%20a%20file%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%26nbsp%3B%20Retention%20policy%20to%20delete%20after%201%20year.%3C%2FP%3E%3CP%3E2.%26nbsp%3B%20Retention%20label%20to%20retain%20for%202%20years%20and%20then%20trigger%20a%20disposition%20review.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20happens%20when%20the%202%20years%20are%20up%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2158330%22%20slang%3D%22en-US%22%3ERe%3A%20Retention%20disposition%20review%20vs%20delete%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2158330%22%20slang%3D%22en-US%22%3E%3CP%3EA%20disposition%20review%20will%20be%20triggered%20and%20the%20reviewer%20can%20decide%20what%20to%20do%20with%20the%20item.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi

 

Could anyone tell me what happens if you have the following scenario for a file?

 

1.  Retention policy to delete after 1 year.

2.  Retention label to retain for 2 years and then trigger a disposition review.

 

What happens when the 2 years are up?

 

Thanks

4 Replies
best response confirmed by stromnessian (Occasional Contributor)
Solution

A disposition review will be triggered and the reviewer can decide what to do with the item.

Thanks @Vasil Michev.  I guess if the action on the label were to do nothing after the 2 year retention period, the file would be deleted because of the deferred delete action from the policy? 

Yes, detailed information on how multiple actions work can be found here: https://docs.microsoft.com/en-us/microsoft-365/compliance/retention?view=o365-worldwide#the-principl...

Awesome, thanks @Vasil Michev !