Blog Post

Microsoft Security Community Blog
10 MIN READ

Sensitivity Auto-labelling via Document Property

Tim_Addison's avatar
Tim_Addison
Icon for Microsoft rankMicrosoft
Aug 05, 2025

This article explores the use of Office document properties as conditions for sensitivity auto-labelling. We will walk through some applicable scenarios and explore configuration options.

Why is this needed? Sensitivity labels are generally relevant within an organisation only. If a file is labelled within one environment and then moved to another environment, sensitivity label cont...
Updated Aug 05, 2025
Version 2.0
admin
automation
compliance
compliance management
data loss prevention
governance
information protection and governance
microsoft 365
microsoft information protection
microsoft purview
CameronStephens2's avatar
CameronStephens2
Copper Contributor
Aug 07, 2025

Thanks, this has been really useful and came at the right time. I've been trying to get auto-label policies to detect the document property fields created by Titus labeling, so I can replace them with the equivalent Purview sensitivity labels.. Fingers crossed after reindexing and the auto-label simulation running again it will detect my test documents.

CameronStephens2's avatar
CameronStephens2
Copper Contributor
Aug 11, 2025

I had a lot of trouble getting this working. Titus creates 2 document property entries, one with the GUID of the label and the other with the name, like below:

  • TitusGUID:1111ab11-1a11-11a1-1abc-a11a1a1a1a11
  • Classification:Public

Even when I followed this guide it would not detect the guid doc property, even when I added the name/value in quotes. I can only assume it doesnt like the dashes, as I started getting detections when I targeted the classification field.