Trimming SharePoint file versions to reduce storage costs 

Great content and extremely helpful topic. Thank you!

Very good! It's exacly what i'm looking for! Thank you!

awesome, thanks

Hi Kasper, great video. About the number of versions, isn't version a part of the cyber security defence also, to prevent Onedrive Sync overwriting all versions, before the sync engine detects it is a cyberattack, stops the sync and offer roll back ? What is the magic number of veresion to keep this defence in tact, but still reduce cost without introducing a risk of dataloss in case of a cryptoware attack, over Onedrive Sync ?

Hi Kasper, Great video. We are in the final stage of "Binary offload to Azure Blob Storage" there by significantly reducing the storage cost while still having the file in SharePoint with all metadata and version history intact. We provide two options. Offload the entire file or only version history. individual files can be restored including all version history and metadata also for users no longer in the AD). Let me know if you are interested. ps. I sent you a teams chat. Thanks!

@3:31 I tried to change the version number to 5, I got an error "You must enter a number between 100 and 50000". Thanks Microsoft.

I have been running into problem with file larger than 2GB and trying to delete versions. Have you seen this issue or found a fix?