Data Protection Issues

Investigate False Positives in a Microsoft 365 Australia Tax File Number DLP Policy

Amos GikundaAmos Gikunda Nov 20, 2026 868 views

Question details

Investigate why a Microsoft 365 DLP policy identifies a value as an Australian tax file number and review options for reducing false positives.

Investigate Australia Tax File Number DLP False Positives in Microsoft 365
Product
Microsoft Purview Data Loss Prevention
Device & OS
not provided
Scenario
A user is reviewing a DLP policy based on the Australia Tax File Number sensitive information type.
Observed behavior
The policy detects a value that the user considers a false positive, and a previous sensitivity adjustment did not resolve the issue.
Before you start

Make sure you have permission to review DLP alerts and policy settings in the Microsoft Purview portal. Identify an affected alert and review its match evidence without sharing the full tax file number unnecessarily.

Solution 1Recommended

Review the DLP Match and Test the Confidence Level

Use this approach to identify why the policy matched the content and test whether a different confidence level reduces false positives.

A sensitive information type can use patterns and supporting evidence to determine a match. Changing the confidence level may reduce false positives, but it can also affect detection of genuine tax file numbers.

The built-in sensitive information type generally cannot be edited to exclude one exact number. Review Microsoft's documentation for the Australia Tax File Number sensitive information type before deciding whether a custom approach is needed.

1
Inspect the alert

In the Microsoft Purview portal, open Data Loss Prevention and review the relevant alert or activity. Inspect the matched sensitive information type, confidence level, and available match evidence.

2
Review the policy rule

Go to Data Loss Prevention > Policies, open the affected policy, and edit its rule. Under the content condition, check the Australia Tax File Number sensitive information type and its configured confidence level.

3
Test a different threshold

Adjust the confidence level in the rule if the setting is available, then use the policy's test or simulation mode. Test both the false-positive example and known valid examples before applying enforcement changes.

4
Compare the results

Return to the policy's alerts or activity results and check whether the unwanted match persists and genuine examples are still detected. If the previous adjustment had no effect, compare the evidence and rule conditions rather than assuming the threshold was the cause.

Review the DLP Match and Test the Confidence Level
Check the detection criteria: Consult Microsoft's documentation for the sensitive information type to understand its patterns and supporting evidence. If the built-in type cannot meet your requirements, assess a custom sensitive information type with your compliance team and test it before deployment.
Free Microsoft Office alternative

Work With Office Files in WPS Office

WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easy to move between office suites. It does not change or troubleshoot Microsoft Purview DLP policies.

Open and edit files that may be reviewed during a DLP investigationWorks with Microsoft Office formats including DOCX, XLSX, and PPTXFamiliar tools for documents, spreadsheets, and presentationsFree and lightweight for everyday office work
microsoft office alternative - wps office

Frequently Asked Questions

Why did the policy detect a number that is not a tax file number?

The value and nearby content may have matched the pattern and supporting evidence used by the sensitive information type. Review the alert's match evidence in Microsoft Purview and compare it with Microsoft's detection criteria.

Where can I change the sensitive information type's confidence level?

In the Microsoft Purview portal, go to Data Loss Prevention > Policies, edit the affected policy and rule, and review the sensitive information type settings in the content condition. Available controls can vary by rule configuration.

Can I exclude one exact number from the built-in tax file number type?

The built-in sensitive information type generally cannot be edited to exclude one exact number. If the built-in detection does not meet your needs, assess whether a custom sensitive information type is suitable and test it carefully.

What if changing the confidence level does not stop the match?

Inspect the alert evidence and the full policy rule, including other conditions and sensitive information types. Test representative examples in simulation mode and consult the Microsoft documentation to understand which criteria are triggering detection.