Skip to content

Commit e0433ea

Browse files
Learn Editor: Update defender-for-storage-malware-scan.md
1 parent 5423aa7 commit e0433ea

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -135,10 +135,10 @@ Learn how to configure Malware Scanning so that [every scan result is sent autom
135135

136136
You may want to log your scan results for compliance evidence or investigating scan results. By setting up a Log Analytics Workspace destination, you can store every scan result in a centralized log repository that is easy to query. You can view the results by navigating to the Log Analytics destination workspace and looking for the `StorageMalwareScanningResults` table.
137137

138-
Learn more about [setting up Log Analytics results](../azure-monitor/logs/quick-create-workspace.md).
138+
Learn more about [setting up logging for malware scanning](advanced-configurations-for-malware-scanning.md#setting-up-logging-for-malware-scanning).
139139

140140
> [!TIP]
141-
> We recommend you try a hands-on lab to try out Malware Scanning in Defender for Storage: the [Ninja](https://github.com/Azure/Microsoft-Defender-for-Cloud/blob/main/Labs/Modules/Module%2019%20-%20Defender%20for%20Storage.md) training instructions for detailed step-by-step instructions on how to test Malware Scanning end-to-end with setting up responses to scanning results. This is part of the 'labs' project that helps customers get ramped up with Microsoft Defender for Cloud and provide hands-on practical experience with its capabilities.
141+
> We invite you to explore the Malware Scanning feature in Defender for Storage through our hands-on lab. Follow the [Ninja training](https://github.com/Azure/Microsoft-Defender-for-Cloud/blob/main/Labs/Modules/Module%2019%20-%20Defender%20for%20Storage.md) instructions for a detailed, step-by-step guide on how to set up and test Malware Scanning end-to-end, including configuring responses to scanning results. This is part of the 'labs' project that helps customers get ramped up with Microsoft Defender for Cloud and provide hands-on practical experience with its capabilities.
142142
143143
## Cost control
144144

@@ -151,7 +151,7 @@ By default, a limit of 5 TB (5,000 GB) is established if no specific capping mec
151151
> [!TIP]
152152
> 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).
153153
154-
Follow [these steps](/azure/storage/common/azure-defender-storage-configure?toc=%2Fazure%2Fdefender-for-cloud%2Ftoc.json&tabs=enable-subscription#azure-portal) to configure the capping mechanism.
154+
Follow [these steps](tutorial-enable-storage-plan.md#set-up-and-configure-microsoft-defender-for-storage) to configure the capping mechanism.
155155

156156
## Handling possible false positives
157157

@@ -188,3 +188,4 @@ Despite the scanning process, access to uploaded data remains unaffected, and th
188188
## Next steps
189189

190190
Learn more on how to [set up response for malware scanning](defender-for-storage-configure-malware-scan.md#setting-up-response-to-malware-scanning) results.
191+

0 commit comments

Comments
 (0)