Security Policy Errors

How to Fix Invalid Custom Sensitive Information Type Error in Microsoft 365 DLP

Tauseeq MagsiTauseeq Magsi Nov 3, 2026 871 views

Question details

The user needs to resolve an 'Invalid sensitive info type' error that occurs when applying a custom sensitive information type to a Microsoft 365 DLP policy, even though the custom type passed preliminary tests.

How to Fix Invalid Custom Sensitive Information Type Error in Microsoft 365 DLP
Product
Microsoft 365 Data Loss Prevention (DLP)
Device & OS
not provided
Scenario
Configuring a Data Loss Prevention (DLP) policy in the Microsoft Purview compliance portal using a newly created custom sensitive information type.
Observed behavior
The custom sensitive information type tests successfully in isolation but produces an 'Invalid sensitive info type' error when actively used within a Microsoft 365 DLP policy.
Before you start

Ensure you have the necessary administrative privileges, such as Compliance Administrator or Organization Management roles, in the Microsoft Purview compliance portal before modifying sensitive info types and DLP policies.

Solution 1Recommended

Review and Reconfigure the Custom Sensitive Information Type

Verify that your custom sensitive information type's regular expressions, confidence levels, and supporting elements are correctly defined and fully compatible with Microsoft 365 DLP policies.

Even if a custom sensitive information type tests correctly on its own, it may fail in a live policy if the parameters (like regex syntax, confidence thresholds, or proximity rules) conflict with the broader DLP configuration.

1
Verify regular expressions

Navigate to the Microsoft Purview compliance portal. Check your custom sensitive info type's regular expression syntax, ensuring it complies precisely with Microsoft's supported regex format.

2
Check confidence levels

Review the confidence level (low, medium, or high) assigned to your custom type. Ensure that the confidence level matches the threshold expected by the specific DLP policy rule you are trying to enforce.

3
Inspect supporting elements

Examine the configuration for supporting elements, such as mandatory keywords or proximity parameters (character distance). Confirm they are logically defined and do not conflict with the primary matching pattern.

4
Review policy locations

Go to your DLP policy settings and check the selected locations (e.g., Exchange email, SharePoint sites, OneDrive accounts). Verify that these chosen locations support the specific criteria of your custom sensitive information type.

Review and Reconfigure the Custom Sensitive Information Type
Free Microsoft Office alternative

Need a Reliable and Free Office Suite? Try WPS Office

While resolving Microsoft 365 compliance and DLP errors requires advanced administrative access, your everyday document editing tasks shouldn't be complicated. WPS Office provides a lightweight, fast, and highly compatible alternative for handling all your office documents efficiently.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installation package for your operating system.
  2. 2. Install the software: Run the downloaded installer and follow the simple on-screen instructions to set up the lightweight office suite on your device.
  3. 3. Start editing documents: Open WPS Office to immediately start viewing, editing, and creating documents with seamless Microsoft Office format compatibility.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight installation without the heavy enterprise overhead of Microsoft 365.Familiar, user-friendly interface for seamless migration and zero learning curve.Built-in PDF editing tools and local document encryption for everyday security.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my custom sensitive info type test successfully but fail in the DLP policy?

The standalone test tool verifies if your regex or keyword logic successfully identifies a string in a sample text. However, when applied to a DLP policy, it must also align with broader compliance validations, confidence level thresholds, and location restrictions, which can trigger an invalid error if mismatched.

What is the recommended confidence level for a custom sensitive information type?

The ideal confidence level depends on how restrictive your pattern is. Broad patterns should use a lower confidence level, while highly specific patterns (like a strict 16-digit regex with a checksum) can use a high confidence level. Ensure your DLP rule threshold matches the level set in your custom type.

Where do I configure sensitive information types in Microsoft 365?

You can create and manage both default and custom sensitive information types by navigating to the Microsoft Purview compliance portal, selecting 'Data classification' from the left menu, and then clicking on the 'Classifiers' or 'Sensitive info types' tab.