Merge pull request #227933 from AlizaBernstein/WI-45763-add-deploy-procedure-screenshots

WI-45763-add deploy procedure screenshots

Author: PMEds28

articles/defender-for-cloud/auto-deploy-azure-monitoring-agent.md

@@ -4,7 +4,7 @@ description: Learn how to deploy the Azure Monitor Agent on your Azure, multiclo
 author: bmansheim
 ms.author: benmansheim
 ms.topic: how-to
-ms.date: 08/03/2022
+ms.date: 02/28/2023
 ms.custom: template-how-to, ignite-2022
 ---
 
@@ -40,15 +40,20 @@ To deploy the Azure Monitor Agent with Defender for Cloud:
 1. From Defender for Cloud's menu, open **Environment settings**.
 1. Select the relevant subscription.
 1. In the Monitoring coverage column of the Defender for Server plan, select **Settings**.
+    :::image type="content" source="media/auto-deploy-azure-monitoring-agent/select-server-setting.png" alt-text="Screenshot showing selecting settings for server service plan." lightbox="media/auto-deploy-azure-monitoring-agent/select-server-setting.png":::
+
 1. Enable deployment of the Azure Monitor Agent:
 
     1. For the **Log Analytics agent/Azure Monitor Agent**, select the **On** status.
+        :::image type="content" source="media/auto-deploy-azure-monitoring-agent/turn-on-azure-monitor-agent-auto-provision.png" alt-text="Screenshot showing turning on status for Log Analytics/Azure Monitor Agent." lightbox="media/auto-deploy-azure-monitoring-agent/turn-on-azure-monitor-agent-auto-provision.png":::
 
         In the Configuration column, you can see the enabled agent type. When you enable Defender plans, Defender for Cloud decides which agent to provision based on your environment. In most cases, the default is the Log Analytics agent.
 
     1. For the **Log Analytics agent/Azure Monitor Agent**, select **Edit configuration**.
 
     1. For the Auto-provisioning configuration agent type, select **Azure Monitor Agent**.
+      
+        :::image type="content" source="media/auto-deploy-azure-monitoring-agent/select-azure-monitor-agent-auto-provision.png" alt-text="Screenshot showing selecting Azure Monitor Agent for auto-provisioning." lightbox="media/auto-deploy-azure-monitoring-agent/select-azure-monitor-agent-auto-provision.png":::  
 
     By default:
 
@@ -85,9 +90,17 @@ To configure a custom destination workspace for the Azure Monitor Agent:
 1. From Defender for Cloud's menu, open **Environment settings**.
 1. Select the relevant subscription.
 1. In the Monitoring coverage column of the Defender for Server plan, select **Settings**.
+
+    :::image type="content" source="media/auto-deploy-azure-monitoring-agent/select-server-setting.png" alt-text="Screenshot showing selecting settings in Monitoring coverage column." lightbox="media/auto-deploy-azure-monitoring-agent/select-server-setting.png":::
+
 1. For the **Log Analytics agent/Azure Monitor Agent**, select **Edit configuration**.
+
+    :::image type="content" source="media/auto-deploy-azure-monitoring-agent/configure-azure-monitor-agent-auto-provision.png" alt-text="Screenshot showing where to select edit configuration for Log Analytics agent/Azure Monitor Agent." lightbox="media/auto-deploy-azure-monitoring-agent/configure-azure-monitor-agent-auto-provision.png":::
+
 1. Select **Custom workspace**, and select the workspace that you want to send data to.
 
+    :::image type="content" source="media/auto-deploy-azure-monitoring-agent/select-azure-monitor-agent-auto-provision-custom.png" alt-text="screenshot showing selection of custom workspace." lightbox="media/auto-deploy-azure-monitoring-agent/select-azure-monitor-agent-auto-provision-custom.png":::
+
 ### Log analytics workspace solutions
 
 The Azure Monitor Agent requires Log analytics workspace solutions. These solutions are automatically installed when you auto-provision the Azure Monitor Agent with the default workspace. 
@@ -99,7 +112,7 @@ The required [Log Analytics workspace solutions](../azure-monitor/insights/solut
 
 ### Additional extensions for Defender for Cloud
 
-The Azure Monitor Agent requires additional extensions. The ASA extension, which supports endpoint protection recommendations, fileless attack detection, and Adaptive Application controls, is automatically installed when you auto-provision the Azure Monitor Agent.
+The Azure Monitor Agent requires more extensions. The ASA extension, which supports endpoint protection recommendations, fileless attack detection, and Adaptive Application controls, is automatically installed when you auto-provision the Azure Monitor Agent.
 
 ### Additional security events collection
 

articles/defender-for-cloud/auto-deploy-vulnerability-assessment.md

@@ -5,18 +5,18 @@ ms.topic: how-to
 ms.custom: ignite-2022
 ms.author: benmansheim
 author: bmansheim
-ms.date: 11/09/2021
+ms.date: 02/28/2023
 ---
 
 # Automatically configure vulnerability assessment for your machines
 
-Defender for Cloud collects data from your machines using agents and extensions. To save you the process of manually installing the extensions, such as [the manual installation of the Log Analytics agent](working-with-log-analytics-agent.md#manual-agent-provisioning), Defender for Cloud reduces management overhead by installing all required extensions on existing and new machines. Learn more [monitoring components](monitoring-components.md).
+Defender for Cloud collects data from your machines using agents and extensions. To save you the process of manually installing the extensions, such as [the manual installation of the Log Analytics agent](working-with-log-analytics-agent.md#manual-agent-provisioning), Defender for Cloud reduces management overhead by installing all required extensions on existing and new machines. Learn more about [monitoring components](monitoring-components.md).
 
 To assess your machines for vulnerabilities, you can use one of the following solutions:
 
 - Microsoft's threat and vulnerability management module of Microsoft Defender for Endpoint (included with Microsoft Defender for Servers)
 - An integrated Qualys agent (included with Microsoft Defender for Servers)
-- A Qualys or Rapid7 scanner which you have licensed separately and configured within Defender for Cloud (this is called the Bring Your Own License, or BYOL, scenario)
+- A Qualys or Rapid7 scanner that you've licensed separately and configured within Defender for Cloud (this scenario is called the Bring Your Own License, or BYOL, scenario)
 
 > [!NOTE]
 > To automatically configure a BYOL solution, see [Integrate security solutions in Microsoft Defender for Cloud](partner-integration.md).
@@ -25,8 +25,10 @@ To assess your machines for vulnerabilities, you can use one of the following so
 
 1. From Defender for Cloud's menu, open **Environment settings**.
 1. Select the relevant subscription.
-1. In the Monitoring coverage column of the Defender for Server plan, select **Settings**.
-1. Turn on the vulnerability assessment for machines and select the relevant solution.
+1. In the Monitoring coverage column of the Defender for Servers plan, select **Settings**.
+    :::image type="content" source="media/auto-deploy-azure-monitoring-agent/select-server-setting.png" alt-text="Screenshot showing selecting service plan settings for server." lightbox="media/auto-deploy-azure-monitoring-agent/select-server-setting.png":::
+1. Turn on the **Vulnerability assessment for machines** and select the relevant solution.
+    :::image type="content" source="media/auto-deploy-vulnerability-assessment/turn-on-deploy-vulnerability-assessment.png" alt-text="Screenshot showing where to turn on deployment of vulnerability assessment for machines." lightbox="media/auto-deploy-vulnerability-assessment/turn-on-deploy-vulnerability-assessment.png":::
 
     > [!TIP]
     > Defender for Cloud enables the following policy: [(Preview) Configure machines to receive a vulnerability assessment provider](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2f13ce0167-8ca6-4048-8e6b-f996402e3c1b).