Forum Discussion
Relabeling files won't reflect the Label changes
I am running Microsoft Purview Scanner, where we scanned and applied the Default Label "Internal" to all the documents in the file share for "One Folder". After that has been applied successfully, we realized that some of the Access Controls in the Label called "Internal" need to be updated. So we enabled Access control permissions for this label to include the "Export" option.
I thought changes made to a published label would reflect already labeled files. But it doesn't. Even though we opened and closed one file and didn't reflect my changes.
Steps we tried:
- Re-ran scan with the option to re-label existing files (already labeled files) with the same label to see if it reflect new changes. But nothing.
- We reset the Scan service and restarted the server too. nothing worked.
Do anyone know if a Label is applied already to files in file share and we update some of the settings for the same label, with the changes reflect properly? I know it reflects in cloud, but not sure why it can't reflect in file shares
1 Reply
Hi rgadagotti,
When you apply a sensitivity label like “Internal” to files on an on‑premises file share, the files store the label settings as they existed at that moment. Updating the label’s published access control permissions (enabling “Export”) doesn’t automatically update already-labeled files. To apply the new settings, you must either remove and reapply the label or explicitly relabel the files using a supported tool. The most reliable method is the Purview PowerShell module, using Set-FileLabel with parameters such as ‑Path and ‑AutoLabel ‑Force to overwrite existing labels with updated settings. While the scanner can attempt relabeling, PowerShell gives precise control over which files are updated.
https://learn.microsoft.com/en-us/powershell/module/purviewinformationprotection/set-filelabel?view=azureipps
