We are implementing a maximum number (500) of unique instances detected for each Sensitive Information Type (SIT) per document scanned.
Affected Workloads
- Microsoft 365 suite
When this will happen
This update will go into effect November 8, 2021.
How this will affect your organization
Many compliance solutions within the Microsoft 365 compliance center support definition of minimum and maximum SITs detected as part of policy configuration. With this update, the number of unique instances detected per SIT per document will be a maximum of 500. This applies to policies for this following solutions: Data Loss Prevention, Information Protection, Information Governance, Communication Compliance, Records Management, Microsoft Cloud App Security, and Privacy Management.
The Compliance center user interface and PowerShell cmdlets will support values ranging from 0 to 500 for both the minimum and maximum instance count settings. When using the Test cmdlet in either the Compliance center or via the PowerShell cmdlets to test a document for the presence of a SIT, the maximum number of sensitive information type instance matches returned will be 500. Additionally, the number of SIT matches shown for documents in Content explorer will display a maximum of 500 matches per document per SIT.
What you need to do to prepare
After this update takes place, any policies that have been configured with larger minimum or maximum instance counts than 500 will no longer match. Please update any existing policies that have minimum and / or maximum instance counts greater than 500 instances to enable these to continue matching.
If you wish to detect content that may contain greater than 500 unique instances of a sensitive information type, you should set the lower value to 500 and the upper value to Any or 500.
You can learn more about sensitive information types here: Learn about sensitive information types.
Message ID: MC290048
Published: 08 October 2021
Updated: 08 October 2021