Forum Discussion

mollybrean1's avatar
mollybrean1
Copper Contributor
Mar 01, 2026
Solved

Auto-labelling does not support content marking

We’ve hit a limitation with service-side auto-labeling in Purview: when a sensitivity label is applied by an auto-labeling policy, any configured visual markings (headers, footers, watermarks) are not written into the document.

A further complication is that there is a requirement which includes a custom script that applies sensitivity labels at the folder level and relies on the service-side engine to cascade those labels down to the folder's contents. This means automation isn't just a 'nice to have' for scale — it is a core dependency of our labeling architecture. The inability to also apply visual markings through this same automated path creates a direct gap in our compliance posture and the MS solution. 

For environments where visible classification is mandated by regulation, this effectively means we can’t rely on service-side auto-labeling alone, which is a big constraint.

I’d really appreciate:

  • Any confirmed best practices/workarounds others are using, and
  • Input from the product team on whether server-side visual markings tied to auto-labeling are being considered / and what to consider meeting this requirement as an alternative 

1 Reply