Microsoft Purview SIT detection issues

Question

I opened a support ticket with Microsoft and hopped on a call with a Support Engineer for compliance Purview. The ticket was generated because the detection of SIT has been spotty and inconsistent. Specifically, labels configured to be automatically applied if a document contains a social security number, for example. We have run numerous tests, Word, Excel documents and copied SIT in or or added the SIT manually. Sometimes it works and sometimes it doesn't. Within 5 minutes on the call, the support engineer indicated that this was a known issue. He pointed us to this link suggesting that we monitor it for any updates. Is anyone else experiencing these issues? Are there any workarounds or suggestions?

Answer 1

@jpcapone

Thanks for reaching out to Microsoft Q&A.

It seems like you're dealing with an issue. Inconsistent detection of Sensitive Information Types (SITs) in Microsoft Purview can indeed be challenging.

Here are workarounds

• Microsoft provides detailed guidance on testing the performance of SITs. You can use the Microsoft Purview portal to test how your SITs perform and troubleshoot any issues
• If you're using Exact Data Match SITs, ensure that any changes you make are given enough time to propagate across the system before testing again. Microsoft recommends waiting at least an hour after making changes
• Ensure that your SITs are correctly configured with appropriate regular expressions and keyword lists. Sometimes, tweaking these settings can improve detection accuracy
• Keep an eye on the link provided by the support engineer for any updates or patches that might address this issue. Microsoft often releases updates to improve the functionality of their services.

Thank you