logo
search
SharePoint Document Issues

Fix SharePoint Sensitivity Column Not Showing Labels for PDF Files

Elise WilliamsElise Williams Oct 21, 2026 868 views

Question details

The Sensitivity column in SharePoint Online does not display sensitivity labels for PDF files, despite properly showing them for standard Office documents.

Fix SharePoint Sensitivity Column Not Showing Labels for PDF Files
Product
SharePoint Online
Device & OS
not provided
Scenario
Managing document security and tracking Microsoft Purview sensitivity labels within a SharePoint document library.
Observed behavior
Sensitivity labels applied to PDF files remain blank or hidden in the SharePoint Sensitivity column, which disrupts business processes that rely on visibility of these security labels.
Before you start

Ensure you have SharePoint Administrator privileges to run PowerShell commands and verify that your organization's Microsoft Purview sensitivity labels are properly configured.

Solution 1Recommended

Enable PDF Sensitivity Labels via SharePoint Online Management Shell

Use a PowerShell command to toggle the tenant setting that allows sensitivity labels to display correctly for PDF files in SharePoint Online.

By default, SharePoint Online may not synchronize or display sensitivity label metadata for PDF documents. Administrators can resolve this by enabling PDF sensitivity label support at the tenant level using PowerShell.

1
Open SharePoint Online Management Shell

Launch the SharePoint Online Management Shell application on your computer as an administrator.

2
Connect to your SharePoint Admin Center

Execute the connection command: Connect-SPOService -Url https://[your-tenant-name]-admin.sharepoint.com and log in with your global or SharePoint admin credentials.

3
Run the configuration command

Type and execute the command: Set-SPOTenant -EnableSensitivityLabelforPDF $true to enable the display of PDF labels.

Propagation Time: It may take several hours for this tenant-level configuration change to propagate and for the sensitivity labels to start appearing on PDFs in your SharePoint libraries.
Free Microsoft Office alternative

Try WPS Office for Seamless PDF and Document Management

If you are frustrated by complex Microsoft Office configurations and sync issues, try WPS Office. It provides a lightweight, unified office suite with powerful built-in PDF editing tools, offering a reliable and familiar experience without the hassle.

  1. 1. Download WPS Office: Visit the official WPS website and click the download button to get the free installer.
  2. 2. Install the application: Run the downloaded installer file and follow the simple on-screen instructions to complete the setup.
  3. 3. Manage your PDFs effortlessly: Open WPS Office to instantly read, edit, and convert your PDFs and Office documents in one unified workspace.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats.Built-in, robust PDF editor for creating, editing, and annotating PDFs natively.Lightweight and fast performance with no complicated tenant-level configurations required.Free to download with a highly familiar, user-friendly interface for easy migration.
microsoft office alternative - wps office

Frequently Asked Questions

Why do Office files show sensitivity labels in SharePoint while PDFs do not?

SharePoint is natively designed to read and sync metadata from standard Office formats (like .docx or .xlsx). PDF files require specific tenant-level configurations, such as the EnableSensitivityLabelforPDF PowerShell setting, to properly extract and display this metadata.

Will labels applied in Adobe Acrobat show up in SharePoint?

Generally, no. Sensitivity labels applied locally using tools like Adobe Acrobat often fail to synchronize their metadata to the SharePoint Online Sensitivity column. Microsoft recommends applying the label in the original Office file before exporting it to PDF.

What should I do if the PowerShell command does not fix the missing labels?

If running 'Set-SPOTenant -EnableSensitivityLabelforPDF $true' does not resolve the issue after a sufficient propagation period, it may be due to a bug or an unsupported feature in your specific tenant ring. You should submit feedback or open a support ticket via the Microsoft 365 admin center.