Hi Eric,
We have record retention policies to enforce in our organization. We do that by adding 'Process' and 'Content Classification' metadata fields to our libraries. Together those two fields determine the length a document lives (after its last modification), before being flagged for deletion. Upon receiving a flag, the library owner(s) get notified via email their document(s)/file(s) are about to expire at which point they have the option of resaving them to reset the last modified date and thus start the retention clock over again.
We have a procedure for creating SharePoint sites and as part of that, the owners identify the process and content classification(s) they need. We then build them the library(s) with the identified processes and content classifications built into their libraries.
The other roadblock for our organization allowing Groups is the administration of group content by the Office 365/SharePoint Admin team. When we build private SharePoint sites, we still build them with a SharePoint Admins AD group as co-owners to the requesting owners. We can then run our scripts to check for content expiration without having to actually get into the group and see the content.
With Groups, in order to monitor content, we would need to add ourselves to the Group membership. That would make us part of the Group and thus we would get all the Group communication (which we don’t want and in the case of private Groups, shouldn't get). Therefore, monitoring of content in Groups becomes unmanageable.
For us to even consider to begin using Groups, the file storage behind O365 Groups must have configurable content type support, and support use of the tenant Content Type Hub.
