removed screenshot

Author: mbender-ms

articles/load-balancer/load-balancer-monitor-alert-health-event-logs.md

@@ -32,9 +32,6 @@ In this section, you learn configure diagnostic settings to collect LoadBalancer
 
 1. In the Azure portal, navigate to your load balancer resource.
 1. From your load balancer resource's **Overview** page, choose  **Monitoring** > **Diagnostic settings**.
-   
-   :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/add-diagnostic-settings.png" alt-text="Screenshot of diagnostic settings window in Azure portal.":::
-
 1. Select **+ Add diagnostic setting**.
 1. In the **Diagnostic setting** window, select or enter the following settings:
 
@@ -62,12 +59,12 @@ In this section, you learn how to query LoadBalancerHealthEvent logs in a Log An
 
 1. In the Azure portal, navigate to your load balancer resource.
 1. From your load balancer resource’s **Overview** page, choose  **Monitoring** > **Logs**.
-3. In the **Queries** window, enter **Latest SNAT Port** in the search bar.
-4. From the results, select **Load to editor** under **Latest SNAT Port Exhaustion per LB Frontend**.
+1. In the **Queries** window, enter **Latest SNAT Port** in the search bar.
+1. From the results, select **Load to editor** under **Latest SNAT Port Exhaustion per LB Frontend**.
 
    :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/search-queries.png" alt-text="Screenshot of Queries window performing search for built-in query.":::
 
-5. The following code is displayed in the query editor:
+1. The following code is displayed in the query editor:
 
     ```kusto
         // Latest Snat Port Exhaustion Per LB Frontend 
@@ -79,11 +76,10 @@ In this section, you learn how to query LoadBalancerHealthEvent logs in a Log An
     ```
     :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/view-snat-query.png" alt-text="Screenshot of query editor with SNAT port exhaustion kusto query.":::
 
-6. Select **Run** to execute the query.
+1. Select **Run** to execute the query.
 1. If you want to modify and save the query, make your query changes and select **Save**>**Save as query**.
 1. In the **Save a query** window, enter a name for the query, other optional information, and select **Save**.
 
-    :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/save-snat-query.png" alt-text="Screenshot of Save a query window.":::
 
 ## Create alerts based on LoadBalancerHealthEvent logs
 

articles/load-balancer/media/monitor-alert-load-balancer-health-event-logs/add-diagnostic-settings.png

@@ -40,25 +40,16 @@ In this section, you chain an existing virtual machine’s public IP to a gatewa
 1. Under **Overview** of the public IP address, confirm that the SKU is **Standard**.
 1. Return to your virtual machine.
 1. In **Overview** of the virtual machine, select **Networking** > **Network settings**.
-1. Select the network interface attached to the virtual machine. This example uses **myvm1185_z1**.
-
-    :::image type="content" source="media/tutorial-gateway-outbound-connectivity/select-network-interface.png" alt-text="Screenshot of network interface attached to virtual machine.":::
-
+1. Select the network interface attached to the virtual machine. 
 1. In **Network interface**, select **IP configurations** under **Settings**.
-6. Under **IP settings**, select **myFrontend** from the **Gateway Load balancer** dropdown menu.
-
-    :::image type="content" source="media/tutorial-gateway-outbound-connectivity/select-gateway-load-balancer.png" alt-text="Screenshot of gateway load balancer selection in IP configuration settings.":::
-
+1. Under **IP configurations**, select **myGWFrontend** from the **Gateway Load balancer** dropdown menu.
 1. Select **Save**.
 
 ## Create a load balancer frontend
 
 In this section, you create a new frontend IP configuration for outbound traffic in our existing standard public load balancer. Using separate public IPs for inbound and outbound traffic is a recommend best practice. Reusing the same public IP for inbound and outbound traffic can increase the risk of SNAT exhaustion, as load balancing and inbound NAT rules decrease the number of available SNAT ports. 
 
 1. Navigate to **myLoadBalancer** or your existing standard public load balancer and go to the **Frontend IP configuration** under **Settings**.
-
-    :::image type="content" source="media/tutorial-gateway-outbound-connectivity/frontend-settings.png" alt-text="Screenshot of frontend IP configuration.":::
-
 1. Select **+ Add** to create a new frontend IP configuration
 1. In the **Add frontend IP configuration** page, enter or select the following information:
 
@@ -68,11 +59,7 @@ In this section, you create a new frontend IP configuration for outbound traffic
     | IP version | Select **IPv4**. |
     | IP type | Select **IP address**. |
     | Public IP address | <br> Select **Create new**.</br> <br/> In **Add a public IP address**, enter **myOutboundPublicIP** for name, and select **Ok**.<br/>|
-    | Gateway Load balancer | Select **myGatewayLoadBalancerFrontEnd**. |    
-
-
-    :::image type="content" source="media/tutorial-gateway-outbound-connectivity/add-frontend-ip-configuration.png" alt-text="Screenshot of Add frontend ip configuration screen.":::
-
+    | Gateway Load balancer | Select **myGWFrontEnd**. |    
 1.	Select **Add**.
 
 > [!NOTE] 
@@ -82,10 +69,7 @@ In this section, you create a new frontend IP configuration for outbound traffic
 ## Create outbound rule
 
 1. In **Load balancer**, select **Outbound rules** under **Settings**.
-2. Select **+ Add** in **Outbound rules** to add a rule.
-
-    :::image type="content" source="media/tutorial-gateway-outbound-connectivity/outbound-rules.png" alt-text="Screenshot of Load Balancer Outbound rules settings.":::
-
+1. Select **+ Add** in **Outbound rules** to add a rule.
 1. In **Add outbound rule** window, Enter or select the following information in:
 
     | Setting | Value |
@@ -102,10 +86,6 @@ In this section, you create a new frontend IP configuration for outbound traffic
     | **Outbound ports** | |
     | Choose by | Select **Maximum number of backend instances**. |
     | Ports per instance | Enter the anticipated maximum number of backend instances. This example uses **2** backend instances.
-
-    
-    :::image type="content" source="media/tutorial-gateway-outbound-connectivity/add-outbound-rule.png" alt-text="Screenshot of Add Outbound Rule screen.":::
-
 1. Select **Add**.
 
     > [!IMPORTANT]