Hi @Shim Kwan ,
Thank you for your question. I understand that you are looking to do a discovery and then a label of on-premises data using AIP Scanner, and that you were hoping to do this by adding your discovery and labeling content jobs to the same UNC repositories.
A cluster can only contain one scan job, so you won't be able to add them to the same repository. If you need more jobs, you will need to add more clusters. Once you assign a cluster to a content scan job, it is not available to other content scan jobs.
But you can run your scanner in discovery mode to read information about your files, and then switch to enforce mode to apply the sensitivity labels based on your policy. This is documented here and there is a good video here with an example of stepping through a content scan job.
Let me know if this is what you are looking for and if you need additional details, and feel free to share more details about your use case and why you are looking to use separate content scan jobs. I have also passed your question along to the product team to see if they have any additional best practices to share.
Marilee
-
If this answer helps resolve your question, please "mark as answer" so that others in the community with similar questions can more easily find a solution.