Answered
Feature Request: Preserve Microsoft Purview label metadata in PDFs so Microsoft DLP can show policy
Please enhance Acrobat’s Microsoft Purview Information Protection (MPIP) integration to reliably embed and preserve label metadata (e.g., authoritative label IDs, assignment method) in PDF/XMP so Microsoft Outlook/Exchange can evaluate attachments and present DLP policy tips + override. Goal: behavior parity with Office files—no silent blocks, clear prompts, and audit‑friendly overrides for justified external sharing.
Problem
In Purview environments, PDFs created or labeled in Acrobat ( or save as pdf in winword) can fail downstream evaluation in Microsoft Outlook (Classic)/Exchange DLP, producing blocked sends without policy tips, while Office attachments with the same labels do show tips/override.
In Purview environments, PDFs created or labeled in Acrobat ( or save as pdf in winword) can fail downstream evaluation in Microsoft Outlook (Classic)/Exchange DLP, producing blocked sends without policy tips, while Office attachments with the same labels do show tips/override.
Current behavior
• Acrobat supports MPIP labeling, but if required metadata is missing/incomplete/not preserved, Microsoft services may not recognize the label for DLP tips.
• Outcomes differ between PDF and Office under identical DLP rules and label priorities.
• Acrobat supports MPIP labeling, but if required metadata is missing/incomplete/not preserved, Microsoft services may not recognize the label for DLP tips.
• Outcomes differ between PDF and Office under identical DLP rules and label priorities.
Expected behavior
Acrobat should embed complete Purview label metadata in XMP so Microsoft services can reliably recognize labels, show policy tips, and—if configured—allow user justification to override. Metadata should persist across save/export and common workflows (and avoid breaking signatures).
Steps
Save using winword as pdf with a Unified “Confidential” label; send externally under a DLP rule that permits override—observe missing tip in some Outlook clients.
Attach a DOCX with the same label—observe policy tip + override.
Impact
• PDF‑centric workflows (contracts, forms, reports) are disrupted.
• Extra handling (manual relabeling, format conversion) adds friction and support load.
• Inconsistent outcomes erode user confidence in labeling + DLP
• PDF‑centric workflows (contracts, forms, reports) are disrupted.
• Extra handling (manual relabeling, format conversion) adds friction and support load.
• Inconsistent outcomes erode user confidence in labeling + DLP
Proposed solution
• Align Acrobat’s MPIP labeling with Microsoft’s MIP SDK metadata expectations (authoritative SensitivityLabelId/ImmutableId, assignment method, timestamps, content marking flags).
• Preserve label metadata through save/export/sign; where signatures prevent changes, provide guidance/options to pre‑label before signing.
• Provide admin diagnostics to verify embedded label metadata so Microsoft DLP can evaluate consistently.
• Align Acrobat’s MPIP labeling with Microsoft’s MIP SDK metadata expectations (authoritative SensitivityLabelId/ImmutableId, assignment method, timestamps, content marking flags).
• Preserve label metadata through save/export/sign; where signatures prevent changes, provide guidance/options to pre‑label before signing.
• Provide admin diagnostics to verify embedded label metadata so Microsoft DLP can evaluate consistently.
Benefits
• Seamless interop between Acrobat‑labeled PDFs and Microsoft DLP tips/overrides.
• Fewer blocks, reduced manual work.
• Stronger cross‑vendor experience for ubiquitous PDF workflows.
• Seamless interop between Acrobat‑labeled PDFs and Microsoft DLP tips/overrides.
• Fewer blocks, reduced manual work.
• Stronger cross‑vendor experience for ubiquitous PDF workflows.
***Digitally signed PDFs can’t be rewritten post‑signing without invalidating signatures; recommend pre‑label before signing and document supported sequences.
AdChoices