An important concept to organizing data in SharePoint is to use metadata. Organizations are starting to see the benefit of moving away from a purely folder-based form of organization and are starting to embrace the use of metadata. Metadata as a method of describing your content is great for filtering, sorting, and even creating custom views to help you find your data quicker and more efficiently. In addition, having a strong metadata architecture for all of your content vastly assists organizations in adopting other key features such as records management, information protection, and now CoPilot. When you create metadata for particular types or categories of content, you should organize it into a content type to help ensure only the relevant metadata is gathered for a file or document. Content types exist at the library level, at the site level (for reuse in other libraries within the site), and at the tenant level in the content type gallery. Creating the content type at the gallery (previously known as the Content Type Hub) is important for additional capabilities like linking to the tenant search schema to aid in additional capabilities, such as locating data for Microsoft Purview features. This post will cover the process for the creation of content types in the content type gallery to further support Purview features such as records management, sensitivity labels, and other features found within Purview.
I recently had the fantastic opportunity to speak at the Microsoft 365 Conference in Las Vegas this May 2023. It was a great time and a fantastic turnout. I think I had 170 – 200 people in my session. I want to use this opportunity to share the slides with the attendees, so I have uploaded them to this post. Please feel free to review them and send me any questions you may require.
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.
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!
I have a new announcement to make! In addition to my blog posts, I have also started to create video blogs to go along with my written posts. I know that many prefer to learn visually as opposed to reading text all the time. So I am now going to build video blogs along with many of my written posts. The first one is about retention labels.