A unified data governance solution that helps manage, protect, and discover data across your organization
Hello @Haim Nazarovsky ,
Thank you for reaching out.
I believe the issue might be due to limitations in File Type. Current endpoint DLP only applies advanced classification to Office documents and PDF files. This is a critical difference: if your source code is in .py, .cs, .java, or other plaintext code files, the endpoint DLP agent may not scan those file types for trainable classifier matches. https://learn.microsoft.com/en-us/purview/dlp-configure-endpoint-settings#advanced-classification-file-scanning-size-limits.
You can also Verify that Advanced classification scanning and protection is turned on in your Endpoint DLP settings. Endpoint DLP requires this cloud-assisted scanning to detect trainable classifier content. If it’s off (or if the device exceeded any set bandwidth limits), the policy won’t recognize content via trainable classifiers on the endpoint.
If you are still facing this issue after following the above, kindly reply back on the comments.
If you find the answer above helpful, please Accept the answer to help anyone in the community who might have a similar question to quickly find the solution.