You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/release-notes.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,25 @@ This article summarizes what's new in Microsoft Defender for Cloud. It includes
32
32
33
33
| Date | Category | Update |
34
34
| -------- | -------- | -------- |
35
+
| April 20, 2026 | GA |[General availability of Defender for Storage integration in Azure Portal Storage Center](#general-availability-of-defender-for-storage-integration-in-azure-poartal-storage-center)|
35
36
| April 1, 2026 | GA |[General availability of container security capabilities in Azure Government cloud](#general-availability-of-container-security-capabilities-in-azure-government-cloud)|
36
37
| April 1, 2026 | Upcoming change |[Update to Defender for SQL servers on machines plan for Fairfax customers](#update-to-defender-for-sql-servers-on-machines-plan-for-fairfax-customers)|
37
38
39
+
40
+
## General availability of Defender for Storage integration in Azure Portal Storage Center
41
+
42
+
April 20, 2026
43
+
44
+
This integration brings Defender for Storage insights directly into the native storage management experience. This approach makes it easier for customers to understand and improve their storage security posture at scale.
45
+
46
+
Customers can now view Defender for Storage threat protection and security posture coverage directly in Storage Center, next to their storage resources.
47
+
48
+
Storage Center provides a centralized, storage-native view of Defender for Storage protection status. This view helps customers quickly understand the following items:
49
+
50
+
1. Which storage accounts are protected, partly protected, or not protected
51
+
1. Where malware scanning, activity monitoring, and sensitive data discovery are enabled
52
+
1. Where security gaps exist across Azure Blob Storage and Azure Files storage
53
+
38
54
### General availability of container security capabilities in Azure Government cloud
0 commit comments