Microsoft Purview | Removing support for relaxed proximity matching in out-of-box sensitive information types
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredIntroduction
We are updating Microsoft Purview’s out-of-box (OOB) sensitive information type (SIT) detection logic to improve accuracy and reduce false positives. As part of this update, the relaxed proximity matching behavior previously used in some OOB SITs will be removed. After this change, all OOB SITs will consistently use stricter proximity rules for more consistent and precise detections.
When this will happen
General Availability (Production, GCC, GCC High, DoD): Available now
How this affects your organization
Who is affected
- Organizations using Microsoft Purview out-of-box sensitive information types in data classification or Data Loss Prevention (DLP) policies.
What will happen
- OOB SITs will stop using the relaxed proximity behavior previously applied in some detection rules.
- All OOB SITs will consistently use stricter proximity matching rules going forward.
- Content that previously matched under relaxed proximity conditions may no longer trigger a detection unless it meets the stricter proximity requirements.
- This may result in fewer detections in scenarios that relied on broader proximity matching.
- Custom sensitive information types are not affected and can still be configured to use broader proximity logic if required.
What you can do to prepare
- Review existing DLP and classification policies that rely on OOB SIT detections.
- Test policy behavior in a non-production environment if broader proximity matching is required for certain workflows.
- Create custom sensitive information types if your organization needs relaxed proximity logic.
Learn more: Sensitive Information Types in Microsoft Purview
Compliance considerations
| Question | Explanation |
|---|---|
| Does the change modify, interrupt, or disable Data Loss Prevention (DLP) policies or enforcement? | Stricter proximity detection may reduce the number of matches, which could indirectly affect DLP behavior. |
| Does the change modify Information Protection labels or sensitive information types? | Out-of-box SITs are updated to retire relaxed proximity matching and use stricter proximity logic. |
What changed
Between archive captures, newest firstThe archive supplies one version of this notice.
Learn more
Links from the notice and their documentation checks- Sensitive Information Types in Microsoft PurviewNot read yet
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 1 linked page has not been read yet.