1. Home
  2. Training Library
  3. Microsoft 365
  4. Microsoft 365 Courses
  5. A Practical Guide to Sensitivity Labels

Embedded Sensitivity Label Demo



The course is part of this learning path

Start course

Sensitivity labels are one way that data classification can be applied to files and documents. Aside from labels built into Microsoft 365, you can define custom labels and apply them to documents manually or automatically via rules. In this course, we create a sensitivity label and apply it to a document and then change that document's label. Labels are embedded in documents allowing classification to follow a document from one domain or file system to another. We look at how label embedding is achieved. Finally, we see how to integrate MS365 sensitivity label functionality with Azure AD groups and sites.

Learning Objectives

  • Create a sensitivity label
  • Use a sensitivity label
  • See how sensitivity labels are implemented within an MS365 Office document
  • Learn how to integrate sensitivity label functionality with Azure AD groups and sites

Intended Audience

  • Students who want to take a practical and in-depth look at sensitivity labels, from their creation, application, and how they are implemented within an office document



Let's see how a sensitivity label is embedded in a document. You can use an archive tool like WinRAR or WinZip to inspect an open XML office document. I'm using WinRAR and will open the docx file as an archive. At the root of the document, we can see the word folder. Inside the word folder, we have the document XML file. Let's confirm that this is, in fact, the same document by opening the XML node with Visual Studio Code and finding the document text of "This is a highly sensitive blank document" – great. 

Going back to the root of the XML doc and then into the doc props folder, we can see a node called custom XML. This node contains the label. Once again, opening the node slash file in an XML editor, we can see the label's unique identifier starting with MSIP for Microsoft information protection. Scrolling on a bit further, we can see the string identifier I  gave the label: MySensitiveLabel. Out of interest, the lpwstr node name means a long pointer of 32 bits to a wide or Unicode string made up of 16-bit characters.

About the Author
Learning Paths

Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a  Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.