r/Office365
Purview sensitivity labels with encryption won’t apply to signed PDF/A files from DocuSign. How are you handling this?
- upvotes
- 1
- comments
- 2
Post
Highlighted: the lines this signal was extracted from
We’re rolling out Microsoft Purview sensitivity labels with encryption. Standard PDFs label without issue. The problem is PDFs that come back digitally signed from DocuSign. The completed files are PDF/A (archival format), and Purview won’t apply the label to them. This may be working as designed, since the PDF/A standard prohibits encryption. What we’ve looked at so far: Vendor cloud conversion: One PDF vendor offered an API-based workaround that uploads each document to their cloud for conversion and sends it back. That means sending sensitive files to a third party and loosening DLP egress rules to allow it. Not an option for us. Desktop PDF tools: We’re testing whether Adobe Acrobat or Foxit handle signed PDF/A files differently on the desktop. (Do you have suggestions for others?) Switching e-sign platforms: Not realistic, since external signers expect DocuSign. Our understanding is that any platform applying a digital signature would produce the same result. It would be an impossibly hard lift to switch from DocuSign. Questions: Do you use Microsoft Purview to label and encrypt your data? If so, have you hit this with signed or PDF/A files? How did you handle it: labeling before signing, a setting in your e-sign platform, a different protection method, or a documented exception? Side question: what PDF viewer/editor does your org standardize on? This isn’t...
Keep reading with a free account
The rest of this post, and every signal for DocuSign, is in your free account.