MicrosoftThanks, 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.
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:
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.
MicrosoftThanks Cameron. Great to hear that you got it working with the Classification field. Not too sure why GUID isn't working. Could be a character limit being applied somewhere, but can't spot a limit that might influence things. Also thought that it could be attempting to match via RegEx but the hyphen character wouldn't cause any issues there. I'll keep an eye out for an answer to this and report back if I find something. ;)
