Skip to content

Commit 1c5bfb2

Browse files
Update defender-for-storage-malware-scan.md
removing capping mechanism limitation
1 parent 82cc065 commit 1c5bfb2

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

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

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -250,10 +250,6 @@ Malware Scanning doesn't block access or change permissions to the uploaded blob
250250

251251
Upon uploading a blob to the storage account, the Malware Scanning will initiate an additional read operation and update the index tag. In most cases, these operations do not generate significant load.
252252

253-
### Capping mechanism
254-
255-
The “capping” mechanism, which would allow you to set limitations on the scanning process to manage cost, is currently not functional (Malware Scanning is free during preview). However, we encourage you to set the desired limitations now, and these will be automatically implemented when the "capping" feature becomes functional.
256-
257253
### Impact on access and storage IOPS
258254

259255
Despite the scanning process, access to uploaded data remains unaffected, and the impact on storage Input/Output Operations Per Second (IOPS) is minimal.

0 commit comments

Comments
 (0)