Announcing new options for custom sensitive information types

As previously messaged in (MC232031) and (MC233488), as part of your data classification efforts in the Microsoft 365 compliance center you can now customize built-in classifiers (sensitive information types) to meet your organization’s needs. We are rolling out some minor feature updates to enhance this customization experience.

When this will happen

Rollout will begin in early May and is expected to be complete by end of May 2021.

How this will affect your organization

The following feature updates will be made available to support customization of your sensitive information types (SITs):

Ability to edit custom dictionaries.You will now be able to edit any custom dictionaries that you have created for SITs used by your organization.

Edit keyword DictionaryView image in new tabNew validation functions. You can now utilize the following 9 regex validator functions when testing and validating your custom SITs:

  • Custom checksum validator
  • Date validator
  • Luhn check
  • Australian Medicare number
  • New Zealand National health index number
  • New Zealand IRD/tax number
  • People’s Republic of China ID
  • Hong Kong ID
  • Denmark personal identification number

Ability to define Proximity at pattern and element level.

While creating or customizing a SIT, you can now define the proximity at pattern or element level. This enables you to define a different proximity for each support element or a different proximity for patterns of varying confidence levels.

What you need to do to prepare

You might want to notify your users about this new capability and update your training and documentation as appropriate.

Add a keyword listView image in new tabThese updates will not impact any existing functionality and are optional to use.

Learn more

Message ID: MC254429

No comments yet

Leave a Reply

I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.

%d bloggers like this: