Merge pull request #265731 from yoavfr/patch-8

Update defender-for-storage-malware-scan.md

Author: v-regandowner

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

@@ -164,6 +164,10 @@ By default, a limit of 5 TB (5,000 GB) is established if no specific capping mec
 
 Follow [these steps](tutorial-enable-storage-plan.md#set-up-and-configure-microsoft-defender-for-storage) to configure the capping mechanism.
 
+## Additional costs of malware scanning
+
+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.
+
 ## Handling possible false positives and false negatives
 
 If you have a file that you suspect might be malware but isn't being detected (false negative) or is being incorrectly detected (false positive), you can submit it to us for analysis through the [sample submission portal](/microsoft-365/security/intelligence/submission-guide). Select “Microsoft Defender for Storage” as the source.