Skip to content

Commit f240409

Browse files
Merge pull request #2612 from yoavfr/docs-editor/defender-for-storage-configure-1773325856
Update defender-for-storage-configure-malware-scan.md
2 parents 3e21b21 + 5c26059 commit f240409

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/defender-for-cloud/defender-for-storage-configure-malware-scan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ If you haven't enabled soft delete for blobs on the storage account, Defender fo
6262

6363
- 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.
6464

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.
6666

6767
- 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.
6868

0 commit comments

Comments
 (0)