Merge pull request #291532 from mbender-ms/lb-screenshot-review-pt2

load balancer - screenshot removal - Pt2

Author: v-dirichards

articles/load-balancer/manage-inbound-nat-rules.md

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: azure-load-balancer
 ms.topic: how-to
-ms.date: 06/26/2024
+ms.date: 12/06/2024
 ms.custom: template-how-to, devx-track-azurepowershell, devx-track-azurecli,engagement-fy23
 ---
 
@@ -15,9 +15,9 @@ An inbound NAT rule is used to forward traffic from a load balancer frontend to
 
 There are two types of inbound NAT rule:
 
-* Inbound NAT rule V1 for VMs - Targets a single machine in the backend pool of the load balancer
+- **Inbound NAT rule V1 for virtual machines**: Targets a single machine in the backend pool of the load balancer.
 
-* Inbound NAT rule V2 for VMs and VMSS- Targets multiple virtual machines in the backend pool of the load balancer
+- **Inbound NAT rule V2 for virtual machines and virtual machine scale sets**: Targets multiple virtual machines in the backend pool of the load balancer.
 
 In this article, you learn how to add and remove an inbound NAT rule for both types. You learn how to change the frontend port allocation in a multiple instance inbound NAT rule. You can choose from the Azure portal, PowerShell, or CLI examples.
 
@@ -30,7 +30,7 @@ In this article, you learn how to add and remove an inbound NAT rule for both ty
 [!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
 
-## Inbound NAT rule V1 for VMs
+## Inbound NAT rule V1 for virtual machines
 
 Choose this option to configure a rule for a single VM. Select Azure portal, PowerShell, or CLI for instructions.
 
@@ -48,8 +48,6 @@ In this example, you create an inbound NAT rule to forward port **500** to backe
 
 5. Select **+ Add** in **Inbound NAT rules** to add the rule.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/add-rule.png" alt-text="Screenshot of the inbound NAT rules page for Azure Load Balancer":::
-
 6. Enter or select the following information in **Add inbound NAT rule**.
 
     | Setting | Value |
@@ -66,27 +64,23 @@ In this example, you create an inbound NAT rule to forward port **500** to backe
 
 7. Leave the rest of the settings at the defaults and select **Add**.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/add-single-instance-rule.png" alt-text="Screenshot of the create inbound NAT rule page":::
-
 # [**PowerShell**](#tab/inbound-nat-rule-powershell)
 
-Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
+In this example, you create an inbound NAT rule to forward port **500** to backend port **443**.
 
-Use [Add-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/add-azloadbalancerinboundnatruleconfig) to create the inbound NAT rule.
+- Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
 
-To save the configuration to the load balancer, use [Set-AzLoadBalancer](/powershell/module/az.network/set-azloadbalancer).
+- Use [Add-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/add-azloadbalancerinboundnatruleconfig) to create the inbound NAT rule.
+    - To save the configuration to the load balancer, use [Set-AzLoadBalancer](/powershell/module/az.network/set-azloadbalancer).
 
-Use [Get-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/get-azloadbalancerinboundnatruleconfig) to place the newly created inbound NAT rule information into a variable. 
+- Use [Get-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/get-azloadbalancerinboundnatruleconfig) to place the newly created inbound NAT rule information into a variable. 
 
-Use [Get-AzNetworkInterface](/powershell/module/az.network/get-aznetworkinterface) to place the network interface information into a variable.
+- Use [Get-AzNetworkInterface](/powershell/module/az.network/get-aznetworkinterface) to place the network interface information into a variable.
 
-Use [Set-AzNetworkInterfaceIpConfig](/powershell/module/az.network/set-aznetworkinterfaceipconfig) to add the newly created inbound NAT rule to the IP configuration of the network interface. 
+- Use [Set-AzNetworkInterfaceIpConfig](/powershell/module/az.network/set-aznetworkinterfaceipconfig) to add the newly created inbound NAT rule to the IP configuration of the network interface. 
 
 To save the configuration to the network interface, use [Set-AzNetworkInterface](/powershell/module/az.network/set-aznetworkinterface).
 
-
-
-
 ```azurepowershell
 ## Place the load balancer information into a variable for later use. ##
 $slb = @{
@@ -140,9 +134,9 @@ $NIC | Set-AzNetworkInterface
 
 In this example, you will create an inbound NAT rule to forward port **500** to backend port **443**. You will then attach the inbound NAT rule to a VM's NIC
 
-Use [az network lb inbound-nat-rule create](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-create) to create the NAT rule.
+- Use [az network lb inbound-nat-rule create](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-create) to create the NAT rule.
 
-Use [az network nic ip-config inbound-nat-rule add](/cli/azure/network/nic/ip-config/inbound-nat-rule) to add the inbound NAT rule to a VM's NIC
+- Use [az network nic ip-config inbound-nat-rule add](/cli/azure/network/nic/ip-config/inbound-nat-rule) to add the inbound NAT rule to a VM's NIC
 
 
 ```azurecli
@@ -165,7 +159,7 @@ Use [az network nic ip-config inbound-nat-rule add](/cli/azure/network/nic/ip-co
 ```
 ---
 
-## Inbound NAT rule V2 for VM and VMSS
+## Inbound NAT rule V2 for virtual machines and virtual machine scale sets
 Choose this option to configure a rule with a range of ports to a backend pool of virtual machines. Select Azure portal, PowerShell, or CLI for instructions.
 
 # [**Portal**](#tab/inbound-nat-rule-portal)
@@ -182,8 +176,6 @@ In this example, you create an inbound NAT rule to forward a range of ports star
 
 5. Select **+ Add** in **Inbound NAT rules** to add the rule.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/add-rule.png" alt-text="Screenshot of the inbound NAT rules page for Azure Load Balancer":::
-
 6. Enter or select the following information in **Add inbound NAT rule**.
 
     | Setting | Value |
@@ -198,18 +190,15 @@ In this example, you create an inbound NAT rule to forward a range of ports star
     | Protocol | Select **TCP**. |
 
 7. Leave the rest at the defaults and select **Add**.
-    
-    :::image type="content" source="./media/manage-inbound-nat-rules/add-inbound-nat-rule.png" alt-text="Screenshot of the add inbound NAT rules page":::
 
 # [**PowerShell**](#tab/inbound-nat-rule-powershell)
 
 In this example, you create an inbound NAT rule to forward a range of ports starting at port 500 to backend port 443. The maximum number of machines in the backend pool is set by the parameter `-FrontendPortRangeEnd` with a value of **1000**. This setting limits the backend pool to **500** virtual machines.
 
-Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
-
-Use [Add-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/add-azloadbalancerinboundnatruleconfig) to create the inbound NAT rule.
+- Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
 
-To save the configuration to the load balancer, use [Set-AzLoadBalancer](/powershell/module/az.network/set-azloadbalancer) 
+- Use [Add-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/add-azloadbalancerinboundnatruleconfig) to create the inbound NAT rule.
+    - To save the configuration to the load balancer, use [Set-AzLoadBalancer](/powershell/module/az.network/set-azloadbalancer) 
 
 ```azurepowershell
 ## Place the load balancer information into a variable for later use. ##
@@ -239,7 +228,7 @@ $lb | Set-AzLoadBalancer
 
 In this example, you create an inbound NAT rule to forward a range of ports starting at port 500 to backend port 443. The maximum number of machines in the backend pool is set by the parameter `--frontend-port-range-end` with a value of **1000**. This setting limits the backend pool to **500** virtual machines.
 
-Use [az network lb inbound-nat-rule create](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-create) to create the NAT rule.
+- Use [az network lb inbound-nat-rule create](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-create) to create the NAT rule.
 
 ```azurecli
     az network lb inbound-nat-rule create \
@@ -273,21 +262,17 @@ To accommodate more virtual machines in the backend pool in a multiple instance
 
 5. Select the inbound NAT rule you wish to change. In this example, it's **myInboundNATrule**.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/select-inbound-nat-rule.png" alt-text="Screenshot of inbound NAT rule overview.":::
-
 6. In the properties of the inbound NAT rule, change the value in **Maximum number of machines in backend pool** to **1000**.
 
 7. Select **Save**.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/change-frontend-ports.png" alt-text="Screenshot of inbound NAT rule properties page.":::
-
 # [**PowerShell**](#tab/inbound-nat-rule-powershell)
 
 To accommodate more virtual machines in the backend pool in a multiple instance rule, change the frontend port allocation in the inbound NAT rule. In this example, you change the parameter `-FrontendPortRangeEnd` to **1500**. This setting increases the maximum number of machines in the backend pool to **1000**.
 
-Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
+- Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
 
-To change the port allocation, use [Set-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/set-azloadbalancerinboundnatruleconfig).
+- To change the port allocation, use [Set-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/set-azloadbalancerinboundnatruleconfig).
 
 ```azurepowershell
 ## Place the load balancer information into a variable for later use. ##
@@ -315,7 +300,7 @@ $lb | Set-AzLoadBalancerInboundNatRuleConfig @rule
 
 To accommodate more virtual machines in the backend pool, change the frontend port allocation in the inbound NAT rule. In this example, you change the parameter `--frontend-port-range-end` to **1500**. This setting increases the maximum number of machines in the backend pool to **1000**
 
-Use [az network lb inbound-nat-rule update](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-update) to change the frontend port allocation.
+- Use [az network lb inbound-nat-rule update](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-update) to change the frontend port allocation.
 
 ```azurecli
     az network lb inbound-nat-rule update \
@@ -342,12 +327,8 @@ Port mappings for the virtual machines in the backend pool can be viewed by usin
 
 5. Select **myInboundNATrule** or your inbound NAT rule.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/view-inbound-nat-rule.png" alt-text="Screenshot of inbound NAT rule page.":::
-
 6. Scroll to the **Port mapping** section of the inbound NAT rule properties page.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/view-port-mappings.png" alt-text="Screenshot of inbound NAT rule port mappings.":::
-
 ## Remove an inbound NAT rule
 
 # [**Portal**](#tab/inbound-nat-rule-portal)
@@ -366,17 +347,13 @@ In this example, you remove an inbound NAT rule.
 
 6. Select **Delete**.
 
-    :::image type="content" source="./media/manage-inbound-nat-rules/remove-inbound-nat-rule.png" alt-text="Screenshot of inbound NAT rule removal.":::
-
 # [**PowerShell**](#tab/inbound-nat-rule-powershell)
 
 In this example, you remove an inbound NAT rule.
 
-Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
-
-To remove the inbound NAT rule, use [Remove-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/remove-azloadbalancerinboundnatruleconfig).
-
-To save the configuration to the load balancer, use [Set-AzLoadBalancer](/powershell/module/az.network/set-azloadbalancer).
+- Use [Get-AzLoadBalancer](/powershell/module/az.network/get-azloadbalancer) to place the load balancer information into a variable.
+- To remove the inbound NAT rule, use [Remove-AzLoadBalancerInboundNatRuleConfig](/powershell/module/az.network/remove-azloadbalancerinboundnatruleconfig).
+- To save the configuration to the load balancer, use [Set-AzLoadBalancer](/powershell/module/az.network/set-azloadbalancer).
 
 ```azurepowershell
 ## Place the load balancer information into a variable for later use. ##
@@ -397,7 +374,7 @@ $lb | Set-AzLoadBalancer
 
 In this example, you remove an inbound NAT rule.
 
-Use [az network lb inbound-nat-rule delete](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-delete) to remove the rule.
+- Use [az network lb inbound-nat-rule delete](/cli/azure/network/lb/inbound-nat-rule#az-network-lb-inbound-nat-rule-delete) to remove the rule.
 
 ```azurecli
     az network lb inbound-nat-rule delete \

articles/load-balancer/manage-probes-how-to.md

@@ -5,13 +5,13 @@ author: mbender-ms
 ms.author: mbender
 ms.service: azure-load-balancer
 ms.topic: how-to
-ms.date: 06/26/2024
+ms.date: 12/06/2024
 ms.custom: template-how-to
 ---
 
 # Manage health probes for Azure Load Balancer using the Azure portal
 
-Azure Load Balancer uses health probes to monitor the health of backend instances. In this article, you'll learn how to manage health probes for Azure Load Balancer.
+Azure Load Balancer uses health probes to monitor the health of backend instances. In this article, you learn how to manage health probes for Azure Load Balancer.
 
 There are three types of health probes:
 
@@ -25,11 +25,11 @@ Health probes have the following properties:
 | Health Probe configuration | Details |
 | --- | --- | 
 | Name | Name of the health probe. This is a name you get to define for your health probe |
-| Protocol | Protocol of health probe. This is the protocol type you would like the health probe to leverage. Available options are: TCP, HTTP, HTTPS |
+| Protocol | Protocol of health probe. This is the protocol type you would like the health probe to use. Available options are: TCP, HTTP, HTTPS |
 | Port | Port of the health probe. The destination port you would like the health probe to use when it connects to the virtual machine to check the virtual machine's health status. You must ensure that the virtual machine is also listening on this port (that is, the port is open). |
 | Interval (seconds) | Interval of health probe. The amount of time (in seconds) between consecutive health check attempts to the virtual machine |
 | Used by | The list of load balancer rules using this specific health probe. You should have at least one rule using the health probe for it to be effective |
-| Path | The URI used for requesting health status from the virtual machine instance by the health probe (only applicable for HTTP(s) probes).
+| Path | The URI used for requesting health status from the virtual machine instance by the health probe (only applicable for HTTPs probes).
 
 >[!IMPORTANT]
 >Load Balancer health probes originate from the IP address 168.63.129.16 and must not be blocked for probes to mark your instance as up. To see this probe traffic within your backend instance, review [the Azure Load Balancer FAQ](./load-balancer-faqs.yml).
@@ -45,11 +45,11 @@ Health probes have the following properties:
 
 ## TCP health probe
 
-In this section, you'll learn how to add and remove a TCP health probe. A public load balancer is used in the examples.
+In this section, you learn how to add and remove a TCP health probe. A public load balancer is used in the examples.
 
 ### Add a TCP health probe
 
-In this example, you'll create a TCP health probe to monitor port 80.
+In this example, you create a TCP health probe to monitor port 80.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -61,8 +61,6 @@ In this example, you'll create a TCP health probe to monitor port 80.
 
 5. Select **+ Add** in **Health probes** to add a probe.
 
-    :::image type="content" source="./media/manage-probes-how-to/add-probe.png" alt-text="Screenshot of the health probes page for Azure Load Balancer":::
-
 6. Enter or select the following information in **Add health probe**.
 
     | Setting | Value |
@@ -76,7 +74,7 @@ In this example, you'll create a TCP health probe to monitor port 80.
 
 ### Remove a TCP health probe
 
-In this example, you'll remove a TCP health probe.
+In this example, you remove a TCP health probe.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -90,15 +88,13 @@ In this example, you'll remove a TCP health probe.
 
 6. Select **Delete**.
 
-    :::image type="content" source="./media/manage-probes-how-to/remove-tcp-probe.png" alt-text="Screenshot of TCP probe removal.":::
-
 ## HTTP health probe
 
-In this section, you'll learn how to add and remove an HTTP health probe. A public load balancer is used in the examples.
+In this section, you learn how to add and remove an HTTP health probe. A public load balancer is used in the examples.
 
 ### Add an HTTP health probe
 
-In this example, you'll create an HTTP health probe.
+In this example, you create an HTTP health probe.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -110,8 +106,6 @@ In this example, you'll create an HTTP health probe.
 
 5. Select **+ Add** in **Health probes** to add a probe.
 
-    :::image type="content" source="./media/manage-probes-how-to/add-probe.png" alt-text="Screenshot of the health probes page for Azure Load Balancer":::
-
 6. Enter or select the following information in **Add health probe**.
 
     | Setting | Value |
@@ -126,7 +120,7 @@ In this example, you'll create an HTTP health probe.
 
 ### Remove an HTTP health probe
 
-In this example, you'll remove an HTTP health probe.
+In this example, you remove an HTTP health probe.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -140,15 +134,13 @@ In this example, you'll remove an HTTP health probe.
 
 6. Select **Delete**.
 
-    :::image type="content" source="./media/manage-probes-how-to/remove-http-probe.png" alt-text="Screenshot of HTTP probe removal.":::
-
 ## HTTPS health probe
 
-In this section, you'll learn how to add and remove an HTTPS health probe. A public load balancer is used in the examples.
+In this section, you learn how to add and remove an HTTPS health probe. A public load balancer is used in the examples.
 
 ### Add an HTTPS health probe
 
-In this example, you'll create an HTTPS health probe.
+In this example, you create an HTTPS health probe.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -160,8 +152,6 @@ In this example, you'll create an HTTPS health probe.
 
 5. Select **+ Add** in **Health probes** to add a probe.
 
-    :::image type="content" source="./media/manage-probes-how-to/add-probe.png" alt-text="Screenshot of the health probes page for Azure Load Balancer":::
-
 6. Enter or select the following information in **Add health probe**.
 
     | Setting | Value |
@@ -176,7 +166,7 @@ In this example, you'll create an HTTPS health probe.
 
 ### Remove an HTTPS health probe
 
-In this example, you'll remove an HTTPS health probe.
+In this example, you remove an HTTPS health probe.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -190,8 +180,6 @@ In this example, you'll remove an HTTPS health probe.
 
 6. Select **Delete**.
 
-    :::image type="content" source="./media/manage-probes-how-to/remove-https-probe.png" alt-text="Screenshot of HTTPS probe removal.":::
-
 ## Next steps
 
 In this article, you learned how to manage health probes for an Azure Load Balancer.