Microsoft Purview Information Protection content markings in PDF

Last updated on Jul 27, 2026

Learn how Adobe Acrobat represents Microsoft Purview Information Protection (MPIP) content markings in PDF using Form XObjects and the ADBE_MIP dictionary.

Overview

If you create or process PDFs that contain Microsoft Purview Information Protection (MPIP) content markings, this article explains how Adobe Acrobat stores those markings. MPIP is a Microsoft service. It can add markings such as watermarks, headers, and footers to a document. Acrobat saves each marking, so it stays compatible with other PDF tools. It also saves each marking so Acrobat can still recognize it. When the markings are stored correctly, Acrobat maintains the document's sensitivity label, so the label can be updated or removed later without breaking.

How the markings are stored

  • Form XObject:  Each marking is saved as a Form XObject. This is a standard, self-contained piece of PDF content that a page can reuse. It holds what the marking looks like on the page.
  • ADBE_MIP dictionary:  Each marking also includes an ADBE_MIP dictionary. This small data set holds details specific to the marking. Its presence tells Acrobat the object is an MPIP marking. Acrobat can then recognize and manage the marking during later labeling.

Generating and printing to PDF

Some workflows convert an MPIP-labeled document to PDF. Examples include Save as PDF and Print to PDF. When one of these keeps a marking in the output, it must also create the marking's ADBE_MIP dictionary.

If the visible marking is kept without its ADBE_MIP dictionary, Acrobat can't recognize it. Acrobat treats the marking as a normal object rather than a marking. The marking might then not be preserved, updated, replaced, or removed correctly when the document's MPIP label changes.

After generation, the marking appears in the file's object tree as a Form XObject carrying the ADBE_MIP dictionary.