MicrosoftThanks Tim_Addison for this blog post and tutorial how to use document property for DLP/Sensitivity Label...This is often use more in the record management parts of Purview
In your last use case to detect a downgrade, I am quite sure it won't really work as if you downgrade the label there is a big chance that all you Purview properties (ClassificationContentMarkingHeaderText:PROTECTED,ClassificationContentMarkingFooterText:PROTECTED,Objective-Classification:PROTECTED) will be changed too so I am not sure the Purview Managed Property are the ones to use in that use case.
Thanks
MicrosoftGood callout Christophe! The Purview properties would change but those for the 3rd party applications would remain static. You'd be able to detect the mismatch between a Titus or Janus property and the sensitivity label though. Such a policy could be annoying in case of legitimate changes though as an item with lowered classifications would still have the static 3rd party properties applied. Potentially a good scenario for an aligning IRM policy to capture user risk rather than a policy blocking transmission. All depends on the org/scenario I guess. ;)
