Forum Discussion

Microsoft

Apr 17, 2017

Announcing support for custom sensitive information types in the Security & Compliance Center

Wesley Holley is a program manager on the Office 365 team. Core to protecting your organization’s data is identifying which data is sensitive and creating policies to govern its use. We includ...

Microsoft

Apr 20, 2017

Hi Dale,

This has already rolled out to all customers. Like in Exchange, the feature is currently accessible via PowerShell. Just connect to the Security & Compliance Center using remote PowerShell where you can use the New/Get/Set/Remove-DlpSensitiveInformationTypeRulePackage cmdlet to upload and manage your custom sensitive information types. The structure of the XML has not changed from Exchange, just the cmdlet name. Full instructions are in the article linked above. Let me know if you have any trouble seeing or using the feature.

Daniel van den Hoek

Copper Contributor

Jun 01, 2017

I tried the command, but got the following message:

New-DlpSensitiveInformationTypeRulePackage : The term 'New-DlpSensitiveInformationTypeRulePackage' is not recognized as the name of a cmdlet, function, script file, or operable program.

Sebastian Zamorano
Former Employee
Oct 03, 2017
Hi Daniel, you need connect to SCC service, not EAC. After you import your Rulepack you need wait around 15 minute to sync the new sensitive information types from SCC to EAC.