Purview auto-labeling works in simulation but doesn’t label existing SharePoint files

Question

Hi everyone,

I’m facing an issue with Microsoft Purview sensitivity auto-labeling:

• Auto-labeling simulation detects existing files correctly (180 files in 1 SharePoint site)
• After turning the policy On, no labels are applied to existing files, even after waiting over a few days.

No errors shown, audit logs and labeling progress remain empty.

Setup highlights:

M365 E5 tenant

Auto-labeling policy for SharePoint

• Conditions: Custom SIT or Trainable Classifier

Auditing enabled, no conflicting policies

According to Microsoft docs, auto-labeling should apply to existing files asynchronously, but it never starts.

Has anyone experienced this?
Is this a known limitation/bug with custom SITs or trainable classifiers?
Is there any way to force a rescan or troubleshoot further?

Thanks in advance for any insights or suggestions!

Answer 1

Hello @Dai Tran , We are facing the same kind of issue now. The above listed parameters were tested and I believe none of the above applies to us. Did you find a solution to this problem ? Would be helpful if we could know what worked for you.

Answer 2

Hi @Dai Tran

Thank you for contacting Microsoft Q&A. Please find below the detailed steps to address the reported issue.

It looks like you're encountering some challenges with the Microsoft Purview sensitivity auto-labeling, particularly with existing files not getting labeled after your policy deployment. Here are a few suggestions to troubleshoot this issue:

Check Classification Status: First, go to the asset details page in the Microsoft Purview Governance portal and verify if the existing files have been classified. If they are not classified, then sensitivity labels will not be applied. Ensure that your SharePoint files meet the minimum distinct value threshold for classification.

Audit and Label Definition: Make sure that the label definition associated with your policy has the Sensitive Information Type (SIT) you intend to use, and that it’s published to at least one user in the Label Policies. If it's not correctly set up, it could prevent labels from being applied.

Verify Supported Data Sources: Confirm that your SharePoint setup and the files you are attempting to label are listed in the supported data sources and file types as mentioned in the documentation. Issues may arise if the asset type doesn’t support auto-labeling.

Check for Conflicting Policies: While you noted that there are no conflicting policies, it’s worthwhile to double-check if there are any other labeling policies that might unintentionally interfere with the auto-labeling process.

Run a Full Scan: Sometimes, a full scan might be necessary to label existing files. Ensure that your data source is scanned properly. You might consider re-triggering a scan to see if that helps with applying the labels.

Refer to Microsoft Docs: There are limitations noted in Microsoft Purview documentation regarding the classification and labeling process. You can review the Classification best practices and troubleshooting guidelines for additional insights.

Email Support: If nothing seems to solve the issue, it might be beneficial to reach out to Microsoft Support for further assistance.

Follow-Up Questions:

• Have you confirmed that the files in question meet the threshold for classification?
• Are there any specific file types that you are trying to auto-label?
• Can you check if there have been any recent updates or changes to the auto-labeling policy that might have affected its operation?
• Have you tried manually applying a label to any of the existing files to see if that works?

I hope these steps help you troubleshoot your auto-labeling issue! Let me know if you have any further questions.