Anyone who has worked with SharePoint development in the golden age of server-side object model development (SOM) likely used the property bag for different requirements in their solutions. With the onset of new development techniques and foundations, the property bag went by the wayside and wasn’t used as often (or at all) when creating solutions. With the new adaptive scope feature in Microsoft Purview, property bag usage has made a resurgence as a necessary location to store values when assigning policies. I will be covering these features in a future post, but for now, I’d like to set the foundation for these posts by discussing property bags and their usage.
I don’t usually blog about announcements as Microsoft does a great job, as do all of the others that share Microsoft posts, but this is big. Microsoft just added a considerable feature coming to your Microsoft 365 tenant in the near future. Integration of your information governance processes with Power Automate. Specifically, the integration of disposition reviews with Power Automate. Let’s chat about what that could mean to your organization.
In my previous posts, I have covered several topics around retention labels. I have mentioned retention policies but never discussed the differences between the two features, and I thought I would cover that here. As a bonus, I created a video to cover this topic and provide you with the process for creating a retention policy. You can access the video here.
In this second video blog, I build on the previous presentation and publish my retention label with a retention label policy.
You can review the related blog post here: Information and Records Management in Office 365 – Publish a Retention Label
You can access the video here: Retention Label Policies in Microsoft 365
Thanks for reading!