Skip to main content
Participant
March 10, 2023
Question

Sensitivity labels applying to PDF files automatically from Sharepoint site

  • March 10, 2023
  • 1 reply
  • 4113 views

We are currently migrating file shares to Sharepoint. We have default sensitivity of internal set on the Sharepoint site.

Recently pdf files have started to gain this label automatically also. When you open the pdf file, it is protected by Purview. Previously, it was only the office Applications that this sensitivty label applied. All the Adobe documentation advises to use full Acrobat to remove this label - this is not feasable as all our end users do not use Acrobat. Has anyone else experienced this issue? I can't believe they don't have the option to remove sensitivity on Reader. I tried adobe and chatting to support but they advised I had to use Acrobat. I'm sure this will become more and more of an issue as others move to Sharepoint and default sensitivity labels.

This topic has been closed for replies.

1 reply

S_S
Community Manager
Community Manager
March 10, 2023

Hi @defaultnknex7zphghu,

 

Hope you are doing well. Sorry for your experience with Acrobat Reader.

 

I was going through the process and found a helpful article from Microsoft that portrays how to remove the sensitivity label from PDFs on SharePoint.

 

Would you mind trying the steps given here: How to remove sensitivity labels from PDFs automatically?

 

Let me know if this helps.

 

 

Participant
March 13, 2023

Thanks @S. S 

That does seem to at least allow me to remove sensitivity from a file after installing Azure information protection and then using the PowerShell command Set-AIPFileLabel, so I can do it without full Acrobat.

I've asked Microsoft if they can advise how to exclude pdf files from applying default sensitivity on a Document Library.

I guess our only other alternative is creating a Document Library with Public sensitivity especially for pdf files that need to be sent out and making sure they don't go in one with Internal Sensitivity. This seems a bit fiddly and means teams are not storing them with the rest of their files.