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/defender-for-storage-configure-malware-scan.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ If you haven't enabled soft delete for blobs on the storage account, Defender fo
62
62
63
63
- If you turn on Versioning for Blobs on your storage account, see [Manage and restore soft delete for blobs](/azure/storage/blobs/soft-delete-blob-manage) to learn how to restore a soft deleted blob.
64
64
65
-
-For the *Soft Delete Malicious Blobs* feature to work on a Storage Account with Versioning turned on, you also need to enable the use of blob index tags for storing scan results. Ensure the parameter *Store scan results as blob index tags* is checked.
65
+
-Blobs that are detected as malicious and soft deleted will always be marked with index tags. If you have selected to not store scan results in index tags, these tags will be removed upon restoring of the soft deleted blob.
66
66
67
67
- The retention period defaults to seven days if you turn on the soft delete malicious blobs feature, but you can change it (range: 1–365 days). You can change the default retention period in your storage account settings.
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/defender-sensor-change-log.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,11 +17,25 @@ To see the version of the sensor run:
17
17
18
18
`kubectl get -n kube-system daemonsets/microsoft-defender-collector-ds -o jsonpath='{.metadata.labels.app\.kubernetes\.io/version}'`
19
19
20
+
21
+
## Defender for Containers – Sensor Support Policy
22
+
23
+
The support policy here applies to all Helm-based and multicloud installations. For scenarios where the sensor is deployed as part of AKS, please refer to: [Supported Kubernetes versions in Azure Kubernetes Service (AKS) - Azure Kubernetes Service | Microsoft Learn](/azure/aks/supported-kubernetes-versions?tabs=azure-cli)
24
+
25
+
|Version|Preview Date|GA Date|End of support|
26
+
| -------- | -------- | -------- | -------- |
27
+
|0.8||Feb 2025|Feb 2027|
28
+
|0.9|July 2025|Apr 2026|Apr 2027|
29
+
|0.10|Feb 2026|Apr 2026|Apr 2027|
30
+
|0.11|Apr 2026|Jul 2026|Jul 2027|
31
+
32
+
Each stable (GA) version is supported for 12 months from its GA release date. After the 12-month window ends, the version is no longer supported. Customers should upgrade to the latest stable or Public release to maintain support and access new capabilities.
33
+
20
34
## Sensor versions available per release
21
35
22
36
### Sensor v0.10 (deployed by Helm or Arc for K8s in Preview mode)
23
37
24
-
**Sensor v0.10.28 — Preview**
38
+
**Sensor v0.10.3 — Preview**
25
39
26
40
-**Released:** March 2026
27
41
@@ -195,18 +209,7 @@ To see the version of the sensor run:
195
209
- Better memory efficiency and reduced CPU consumption
196
210
- Bug fixes and security enhancements
197
211
198
-
## Defender for Containers – Sensor Support Policy
199
-
200
-
The support policy here applies to all Helm-based and multicloud installations. For scenarios where the sensor is deployed as part of AKS, please refer to: [Supported Kubernetes versions in Azure Kubernetes Service (AKS) - Azure Kubernetes Service | Microsoft Learn](/azure/aks/supported-kubernetes-versions?tabs=azure-cli)
201
-
202
-
|Version|Preview Date|GA Date|End of support|
203
-
| -------- | -------- | -------- | -------- |
204
-
|0.8||Feb 2025|Feb 2027|
205
-
|0.9|July 2025|Apr 2026|Apr 2027|
206
-
|0.10|Feb 2026|Apr 2026|Apr 2027|
207
-
|0.11|Apr 2026|Jul 2026|Jul 2027|
208
212
209
-
Each stable (GA) version is supported for 12 months from its GA release date. After the 12-month window ends, the version is no longer supported. Customers should upgrade to the latest stable or Public release to maintain support and access new capabilities.
0 commit comments