Forum Discussion
Roger Gu
Microsoft
MicrosoftVersioning update to Document Libraries in team sites in SharePoint Online and OneDrive for Business
The announcement has been moved to New Updates to OneDrive and SharePoint Team Site Versioning.
In various articles I read about this, including this one, "all Document Libraries" eventually changes to "all libraries". Is this versioning going to strictly be limited to Document Libraries?
Roger GuThis change only applies to Document Libraries that are in Team Sites(both Groups-connected and not connected). In other words, other types of libraries or Document Libraries in other types of sites won't be affected.
Not sure I would agree with this assertion Roger, because fundamentally all libraries are based off the common root library template. Microsoft as deprecated and removed many of the branching variations of libraries over the last couple of years and have standardised on one multi-purpose library.
In new Communications sites and Modern Teams site templates you only have 1 library option available (until you re-enable or create a new one - which you can't do via the UI anymore) - so it's easy to say that it's likely to only be in site based on Modern site-template, but not guaranteed, because its the same root template as std document library in any site - including Classic site templates. So the options on global changes are script to a single set of specific site-templates (unlikely, because we know they will do at least 3 - communications, modern teams and OneDrive) *or* update the root app - which impacts all inheriting from it.
I suspect they'll go global, because its marketed as "enable great experiences"...
Agree.
I'm also not convinced that the site assets library (which is a doc lib) won't be updated to default forced versioning and thow us back in a situation of over consumption of quotas due to files in this library (as the default group onenote).
Despite Onenote having it's own versioning control, this was never taken in consideration on sharepoint doc libs, hence our actions to limit versioning on site asstes library - which we could do easily.
