Updated articles

Author: mbender-ms

articles/load-balancer/load-balancer-distribution-mode.md

@@ -44,9 +44,6 @@ The following options are available:
 
 5. Choose the distribution mode and then select **Save**.
 
-:::image type="content" source="./media/load-balancer-distribution-mode/session-persistence.png" alt-text="Change session persistence on load balancer rule." border="true" lightbox="./media/load-balancer-distribution-mode/session-persistence.png":::
-
-
 # [**PowerShell**](#tab/azure-powershell)
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]

articles/load-balancer/load-balancer-multiple-ip.md

@@ -117,14 +117,10 @@ For more information on configuring floating IP in the virtual machine configura
 
 5. In **Networking**, select the name of the network interface next to **Network interface**. The network interface begins with the name of the VM and has a random number assigned. In this example, **myVM1266**.
 
-    :::image type="content" source="./media/load-balancer-multiple-ip/myvm1-nic.png" alt-text="Screenshot of myVM1 networking configuration in Azure portal.":::
-
 6. In the network interface page, select **IP configurations** in **Settings**.
 
 7. In **IP configurations**, select **ipconfig1**.
 
-    :::image type="content" source="./media/load-balancer-multiple-ip/myvm1-ipconfig1.png" alt-text="Screenshot of myVM1 network interface configuration.":::
-
 8. Select **Static** in **Assignment** in the **ipconfig1** configuration.
 
 9. Select **Save**.
@@ -135,8 +131,6 @@ For more information on configuring floating IP in the virtual machine configura
 
 12. In the **Networking** page, select **Attach network interface**.
 
-    :::image type="content" source="./media/load-balancer-multiple-ip/myvm1-attach-nic.png" alt-text="Screenshot of myVM1 attach network interface.":::
-
 13. In **Attach network interface**, select **Create and attach network interface**.
 
 14. In **Create network interface**, enter or select the following information:

articles/load-balancer/load-balancer-standard-diagnostics.md

@@ -69,10 +69,6 @@ To view the metrics for your load balancer resources:
   >
   >Recommendation: When analyzing metric aggregation type Sum and Count, we recommend using a time aggregation value that is greater than one minute.
 
-:::image type="content" source="./media/load-balancer-standard-diagnostics/lbmetrics1anew.png" alt-text="Metric for data path availability for a standard load balancer.":::
-
-*Figure: Metric for data path availability for a standard load balancer*
-
 ### Retrieve multi-dimensional metrics programmatically via APIs
 
 For API guidance for retrieving multi-dimensional metric definitions and values, see [Azure Monitoring REST API walkthrough](/azure/azure-monitor/essentials/rest-api-walkthrough#retrieve-metric-definitions). These metrics can be written to a storage account by adding a [diagnostic setting](/azure/azure-monitor/essentials/diagnostic-settings) for the 'All Metrics' category. 
@@ -101,10 +97,6 @@ To get the Data Path Availability for your load balancer resources:
 
 1. Additionally, add a filter on the frontend IP address or frontend port as the dimension with the required frontend IP address or frontend port. Then group them by the selected dimension.
 
-:::image type="content" source="./media/load-balancer-standard-diagnostics/lbmetrics-vipprobing.png" alt-text="Load balancer frontend probing details.":::
-
-*Figure: Load balancer frontend probing details*
-
 The metric is generated by a probing service within the region that simulates traffic. The probing service periodically generates a packet that matches your deployment's frontend and load balancing rule. The packet then traverse the region from the source to the host of a VM in the backend pool. The load balancer infrastructure performs the same load balancing and translation operations as it does for all other traffic. After the probe arrives on the host, where a VM in the backend pool is located, the host generates a response to the probing service. Your VM doesn’t see this traffic. 
 
 Please note that the Data Path Availability metric will only be generated on frontend IP configurations with load balancing rules.
@@ -161,10 +153,6 @@ To get SNAT connection statistics:
 
 2. Group by **Connection State** for successful and failed SNAT connection counts to be represented by different lines. 
 
-:::image type="content" source="./media/load-balancer-standard-diagnostics/lbmetrics-snatconnection.png" alt-text="Load balancer SNAT connection count.":::
-
-*Figure: Load balancer SNAT connection count*
-
 </details>
 
 #### How do I check my SNAT port usage and allocation?
@@ -195,14 +183,6 @@ To view SNAT port usage and allocation:
 
 5. For example, to monitor SNAT usage for TCP flows per machine, aggregate by **Average**, split by **Backend IPs** and filter by **Protocol Type**. 
 
-:::image type="content" source="./media/load-balancer-standard-diagnostics/snat-usage-and-allocation.png" alt-text="Average TCP SNAT port allocation and usage for a set of backend VMs.":::
-
-*Figure: Average TCP SNAT port allocation and usage for a set of backend VMs*
-
-:::image type="content" source="./media/load-balancer-standard-diagnostics/snat-usage-split.png" alt-text="TCP SNAT port usage per backend instance.":::
-
-*Figure: TCP SNAT port usage per backend instance*
-
 </details>
 
 #### How do I check inbound/outbound connection attempts for my service?
@@ -216,10 +196,6 @@ For more information on outbound connections, see [Source Network Address Transl
 
 Use **Sum** as the aggregation for most scenarios.
 
-:::image type="content" source="./media/load-balancer-standard-diagnostics/lbmetrics-syncount.png" alt-text="Load balancer SYN count.":::
-
-*Figure: Load balancer SYN count*
-
 </details>
 
 #### How do I check my network bandwidth consumption? 
@@ -242,10 +218,6 @@ To get byte or packet count statistics:
 
     * Get overall statistics for your load balancer resource without any filtering.
 
-:::image type="content" source="./media/load-balancer-standard-diagnostics/lbmetrics-bytecount.png" alt-text="Load balancer byte count.":::
-
-*Figure: Load balancer byte count*
-
 </details>
 
 #### <a name = "vipavailabilityandhealthprobes"></a>How do I diagnose my load balancer deployment?
@@ -327,21 +299,9 @@ To view the health of your public standard load balancer resources:
 
 1. Select  **Monitor** > **Service health**.
 
-    :::image type="content" source="./media/load-balancer-standard-diagnostics/lbhealth1.png" alt-text="The service health link on Azure Monitor.":::
-
-   *Figure: The service health link on Azure Monitor*
-
 2. Select **Resource health**, and then make sure that **Subscription ID** and **Resource type = load balancer** are selected.
 
-    :::image type="content" source="./media/load-balancer-standard-diagnostics/lbhealth3.png" alt-text="Select resource for health view.":::
-
-   *Figure: Select resource for health view*
-
 3. In the list, select the load balancer resource to view its historical health status.
-
-    :::image type="content" source="./media/load-balancer-standard-diagnostics/lbhealth4.png" alt-text="Resource health status.":::
-
-   *Figure: Resource health status*
 
 A generic description of a resource health status is available in the [resource health documentation](/azure/service-health/resource-health-overview).