I’m pleased to announce the General Availability of automatic sensitivity labeling in Office apps using trainable classifiers. Now, within Microsoft 365 Compliance Center you will be able to create sensitivity labels and corresponding automatic or recommended labeling policies in Office apps using built-in classifiers and your own custom trainable classifiers as well. With this capability, customers can quickly classify more of their ever-increasing data and protect sensitive content
The five built-in classifiers available are:
- Resume: detects written accounts of an applicant's personal, educational, and professional qualifications and experience
- Source code: detects a set of instructions and statements written in the top 25 computer programming languages of GitHub
- Threat: detects a specific category of offensive language related to threats to commit violence or do physical harm/damage to a person/property.
- Harassment: detects a specific category of offensive language related to offensive conduct targeting one or multiple individuals regarding race, color, religion, national origin, gender, sexual orientation, age, disability, and genetic information.
- Profanity: detects a specific category of offensive language that contains swear words or vulgar language.
The Office apps which will support automatic sensitivity labeling using the above classifiers include the following:
- Microsoft 365 Apps for enterprise (formerly Office 365 ProPlus) for Windows, Current Channel in version 2009 and later:
- Word
- Excel
- PowerPoint
- Outlook
- Office Online Apps (Opt-in to enable sensitivity labels required)
- Word Online
- Excel Online
- PowerPoint Online
- Outlook Web
The subscription and license requirements for this feature are similar to what is needed to enable automatic sensitivity labels in Office apps. You need one of Microsoft 365 E5, Office 365 E5, or Azure Information Protection Premium P2. For more details, see subscription and licensing requirements for sensitivity labels
For more details on this feature please visit our documentation.