Skip to content

Commit d95ecf0

Browse files
authored
Update defender-for-storage-malware-scan.md
Add clarity around other costs related to enabling Malware Scanning
1 parent c8bf725 commit d95ecf0

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,6 +160,9 @@ By default, a limit of 5 TB (5,000 GB) is established if no specific capping mec
160160
> You can set the capping mechanism on either individual storage accounts or across an entire subscription (every storage account on the subscription will be allocated the limit defined on the subscription level).
161161
162162
Follow [these steps](tutorial-enable-storage-plan.md#set-up-and-configure-microsoft-defender-for-storage) to configure the capping mechanism.
163+
## Addtional costs of malware scanning
164+
165+
Malware scanning uses other Azure services as its foundation. This means that when you enable Malware scanning, you will also be charged for the Azure services that it requires. These services include Azure Storage read operations, Azure Storage blob indexing and Azure Event Grid notifications.
163166

164167
## Handling possible false positives and false negatives
165168

0 commit comments

Comments
 (0)