Record management capabilities within Microsoft Purview have vastly improved over the last few years. With features such as adaptive scopes, auto-apply retention capabilities, and much more, the ability to apply different techniques to your record management needs is vastly growing. Throughout all of these features and enhancements, the foundation of records management in Microsoft 365 is based on one real component: the record label. Now before all of you get upset and rage close this blog post, I am not saying retention policies, retention label policies, or other components aren’t important. They all have their place for information governance in Microsoft 365. But record labels have all the real options and where all the real record management magic happens. In this series, I am going to do a deep dive into the different Microsoft Purview retention label types. What the differences are, the options available to you as administrators or record managers, and how they can be used within your organization.
In October 2021, Microsoft announced a significant change in how retention labels could be applied to locations. The concept for adaptive scopes is pretty straightforward, deploy labels or apply labels automatically based on some piece (or pieces) of metadata the system can scan for. This means you can now dynamically assign retention labels with adaptive scopes to your SharePoint (including Teams), OneDrive, and Exchange locations without directly declaring them in the policy.
Previously I discussed what a property bag was and how to configure it within your environment. The next step in utilizing this property bag is to make it searchable. This can help users find locations they need to based on the site’s property bag values. Even better, however, Microsoft 365 can use the property bag values to enhance features within Microsoft Purview, such as retention policies and retention label policies. In this post, we’ll cover how to make your property bag searchable by linking a property bag to a managed property.
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.