Forum Discussion
Auto label based on content matching by Information protection scanner
I have on premises repository in TBs. I have already configured information protection scanner and added repository where files are placed and my scanner is scanning the files also. I want to auto label them based on content matching.
for example:
Auto label files as "Confidential" when there is a match of world "budget"
Auto label files as "Internal use only" when there is a match of word "leave request form"
I know auto labeling is available for M365 for example exchange, ondrive and sharepoint. but How can I achieve above using information protection scanner.
Please help. Thanks
- miller34mike
Microsoft
- I followed exactly what you said but labels are not being applied.
Shall I create auto labeling policy also?- miller34mike
- miller34mike
Thank you for posting your question here, I understand you're looking to apply labels automatically in your on-premises repositories through the MPIP scanner.
To do this, you will actually need to set the auto labeling option within the sensitivity label itself that you want to be applied and then make sure that label or the labels are assigned to your service account through a label policy.
Then when you configure the content scan jobs in the purview admin portal, I recommend leaving the label settings as the policy default.
You can read more on this here:
Hi Mike!
This is interesting. So I have the AIP Scanner installed and it is not labeling. I understand from following this thread that we need to add the Service Account to the auto label policies (with the SITs defined). My question though is where do we add the Service Account on this "choose locations" page...
for example, the UNC path I am trying to point to is I:\Security\AIP Scanner Test Data
Thanks for any guidance!
Best regards,
Luke Fisher
- miller34mike
Hey Luke!
So, yes, you need to add the service account to the auto-labeling scope, but not that auto-labeling scope. You need to have one of your labels configured for auto-labelling and then have that label deployed to your service account through the label policy.
I'd recommend checking out this article for getting everything setup.
