Sensitivity label consent changes

November 2024 Update 2

• Change Sensitivity label consent changes
• Change Sensitivity label changes
• Preview Defender for Storage Malware Scanning for blobs up to 50GB

Sensitivity label consent changes
Estimated date for change: November 26, 2024

You no longer need to select the dedicated consent button under the "Information Protection" section within the "Labels" page, to benefit from custom information types and sensitivity labels configured in the Microsoft 365 Defender portal or Microsoft Purview compliance portal.

With this change, all custom information types and sensitivity labels are automatically imported into the Microsoft Defender for Cloud portal.
Learn more about data sensitivity settings.

Sensitivity label changes
November 26, 2024
Until recently, Defender for Cloud imported all sensitivity labels from the Microsoft 365 Defender portal that met the following two conditions:

Sensitivity labels that have their scope set to "Items -> Files", or "Items -> Emails", under the "Define the scope of your label" section in the Information Protection section.
The sensitivity label has an automatic labeling rule configured.
As of November 26, 2024 the names of the sensitivity label scopes in the user interface (UI) have been updated in both the Microsoft 365 Defender portal and the Microsoft Purview compliance portal. Defender for Cloud now will only import sensitivity labels with the "Files and other data assets" scope applied to them. Defender for Cloud no longer imports labels with the "Emails" scope applied to them.

Defender for Storage Malware Scanning for blobs up to 50GB (Preview)
November 25, 2024
Estimated date for change: December 31, 2024

Starting on December 31, 2024, Defender for Storage Malware Scanning will support blobs up to 50GB in size (previously limited to 2GB).

Please note that for storage accounts where large blobs are uploaded, the increased blob size limit will result in higher monthly charges.

To avoid unexpected high charges, you may want to set an appropriate cap on total GB scanned per month. For more information, see Cost control for on-upload malware scanning.