Sep 14 2021
- last edited on
Feb 01 2023
Is it possible to apply sensitivity labels to documents in SharePoint (not sites or groups) using PowerShell?
Sep 14 2021 01:25 PM
Sep 14 2021 10:32 PM
Sep 15 2021 07:48 AM
Sep 15 2021 08:04 AM
Sep 15 2021 11:05 PMSolution
Sep 15 2021 11:34 PM
Sep 15 2021 11:43 PM
Sep 16 2021 08:21 AM - edited Sep 16 2021 08:33 AM
@JSlei Hello again, didn't you look for an option to protect at scale without anyone have to review the documents? Are you saying this isn't applicable even if using PowerShell cmdlets for it?
"Manual application of sensitivity labels is a good way to protect new messages and documents but does nothing to deal with the mass of documents and messages that already exist inside Office 365. To address the issue, Microsoft is running a preview program for auto-labeling Word, Excel, and PowerPoint files stored in SharePoint Online sites and OneDrive for Business accounts (Exchange Online will come later). The solution is intended to allow Office 365 tenants to protect existing content at scale without needing anyone to review large quantities of documents."
Sep 16 2021 12:03 PM
"It is definitely possible to solve with a script, however, with the MIP SDK. But why bother, MCAS can put a label on all documents in an SP site. Then Microsoft is rebuilding SharePoint online right now to force all files that do not have a manually set label in an SP site based on its container label."
The latter being the roadmap item I linked to above scheduled for release in December.
Sep 17 2021 12:16 AM
@JSlei About MCAS and Auto-labeling Microsoft Cloud App Security and Sensitivity Labels – Joanne C Klein
(a bit old but still relevant)
Sep 17 2021 10:33 AM
Oct 26 2021 06:51 PM - edited Oct 26 2021 06:56 PM
Just bringing a slightly similar scenario to this thread - and wondering if anyone can confirm if it's possible? We have a Client with millions of Docs in Sharepoint 2013 OnPrem today where they have been very rigorous in using TermSet from the TermStore to tag all sensitive docs/files with the appropriate MetaData and this has been in use for some 6 - 7 years.
We are now assisting with the Sharepoint Migration and the question becomes - what is the *best* (least painful/best chance of success) method of ensuring that all the contents get from - Sharepoint 2013 onPrem to Sharepoint Online:
One of the key things we are trying to achieve is do this "at scale" without having to open each file individually - if AutoLabelling is the way to go then fine, but from what we have reviewed so far this is NOT a case where we need to identify docs based on SIT's - the intent is to simply identify docs/files based on TermSet attributes and then apply the matching SL
Any advice or suggestions welcome, we're still researching, but thought it might be worth checking if anyone else has come across this?
Oct 27 2021 06:06 AM - edited Oct 27 2021 06:06 AM
The challenges with a manual approach are user error and scalability. Not to mention that once you have completed the project it will only be for a moment in time and if an employee creates a sensitive file 15 minutes after you've finished then it will be missed.
The best way to do this may be this third-party tool (Data Validation & Classification Tools | AvePoint) which will automate this process with AI rules. Disclaimer- I am currently employed by AvePoint.
Hope this helps.
Dec 31 2021 09:46 AM
Jan 25 2022 07:15 AM
Feb 23 2022 05:09 PM
How would someone using PowerShell change a label on a document? For example, a document was classified as Confidential. A request has come in to have the document reclassified as Internal. Is there a way for the Security Admin to change the classification of the document assuming we do not allow our base to change the classification themselves?
Feb 24 2022 12:18 AM