It seems SharePoint Intelligent Versioning and the 500 Version Limit we may end up with major version of more than 500 as well according to this blog post. Minor versions have been enabled on all SMP libraries and hence minor versions will creep quicker unless users intentionally update to major which does not happen regularly. At the point of initial migration, the retention requirement for the file does not get kicked in probably explaining loss of migrated version if version count is more than 500. https://office365itpros.com/2025/01/06/intelligent-versioning-500/
https://office365itpros.com/2024/11/13/intelligent-versioning-spo/ - Another one Intelligent Versioning & Retention: Where do Versions Go? explaining the expiry date getting adjusted to a later date for sites with retention policies. Retention labels are behaving similar to retention policies in BoE environment in respect to keeping all versions and why?
minor versions: minor versions have a different limit with a maximum threshold of 511 - Steve I suspect one of your “512” has been manually deleted?
we’re not able to control that number - The ‘Version Count limit’ allows for which major version you store minor versions for, but not the number of minor versions.
So if you choose “3” for ‘keep drafts for…’ then you’re potentially keeping 1533 minor versions on top of the major version count.
would it not be ’every file that has a label’ ? we might be able to script getting some numbers on that?
it was a little tricky to find, because you have to locate a file that has a label has multiple versions which are older than 6 months
References
https://office365itpros.com/2025/01/06/intelligent-versioning-500/ https://office365itpros.com/2024/11/13/intelligent-versioning-spo/