Merge pull request #279380 from mbender-ms/lb-freshness-june-2024-IV

load balancer - freshness updates June - Part IV

Author: AnnaMHuff

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

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/01/2023
+ms.date: 06/26/2024
 ms.custom: template-how-to, devx-track-azurepowershell, devx-track-azurecli,engagement-fy23
 ---
 

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

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/05/2023
+ms.date: 06/26/2024
 ms.custom: template-how-to
 ---
 
@@ -27,7 +27,7 @@ Health probes have the following properties:
 | 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 |
 | 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 attemps to the virtual machine |
+| 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).
 

articles/load-balancer/move-across-regions-external-load-balancer-portal.md

@@ -4,7 +4,7 @@ description: Use an Azure Resource Manager template to move an external load bal
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 06/27/2023
+ms.date: 06/27/2024
 ms.author: mbender
 ms.custom: template-how-to, devx-track-arm-template, engagement-fy23
 ---

articles/load-balancer/move-across-regions-external-load-balancer-powershell.md

@@ -4,7 +4,7 @@ description: Use Azure Resource Manager template to move Azure external Load Bal
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 06/27/2023
+ms.date: 06/27/2024
 ms.author: mbender 
 ms.custom: devx-track-azurepowershell, template-how-to, devx-track-arm-template, engagment-fy23
 ---

articles/load-balancer/move-across-regions-internal-load-balancer-portal.md

@@ -4,35 +4,35 @@ description: Use Azure Resource Manager template to move Azure internal Load Bal
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 06/27/2023
+ms.date: 06/27/2024
 ms.author: mbender
 ms.custom: template-how-to, devx-track-arm-template, engagement-fy23
 ---
 
 # Move Azure internal Load Balancer to another region using the Azure portal
 
-There are various scenarios in which you'd want to move your existing internal load balancer from one region to another. For example, you may want to create an internal load balancer with the same configuration for testing. You may also want to move an internal load balancer to another region as part of disaster recovery planning.
+There are various scenarios in which you'd want to move your existing internal load balancer from one region to another. For example, you might want to create an internal load balancer with the same configuration for testing. You might also want to move an internal load balancer to another region as part of disaster recovery planning.
 
-Azure internal load balancers can't be moved from one region to another. You can however, use an Azure Resource Manager template to export the existing configuration and virtual network of an internal load balancer.  You can then stage the resource in another region by exporting the load balancer and virtual network to a template, modifying the parameters to match the destination region, and then deploy the templates to the new region.  For more information on Resource Manager and templates, see [Quickstart: Create and deploy Azure Resource Manager templates by using the Azure portal](../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
+Azure internal load balancers can't be moved from one region to another. You can however, use an Azure Resource Manager template to export the existing configuration and virtual network of an internal load balancer. You can then stage the resource in another region by exporting the load balancer and virtual network to a template, modifying the parameters to match the destination region, and then deploy the templates to the new region. For more information on Resource Manager and templates, see [Quickstart: Create and deploy Azure Resource Manager templates by using the Azure portal](../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
 
 
 ## Prerequisites
 
 - Make sure that the Azure internal load balancer is in the Azure region from which you want to move.
 
-- Azure internal load balancers can't be moved between regions.  You have to associate the new load balancer to resources in the target region.
+- Azure internal load balancers can't be moved between regions. You have to associate the new load balancer to resources in the target region.
 
 - To export an internal load balancer configuration and deploy a template to create an internal load balancer in another region, you need the Network Contributor role or higher.
 
 - Identify the source networking layout and all the resources that you're currently using. This layout includes but isn't limited to load balancers, network security groups, virtual machines, and virtual networks.
 
 - Verify that your Azure subscription allows you to create internal load balancers in the target region that's used. Contact support to enable the required quota.
 
-- Make sure that your subscription has enough resources to support the addition of load balancers for this process.  See [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits)
+- Make sure that your subscription has enough resources to support the addition of load balancers for this process. See [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits)
 
 
 ## Prepare and move
-The following steps show how to prepare the internal load balancer for the move using a Resource Manager template, and move the internal load balancer configuration to the target region using the Azure portal.  As part of this process, the virtual network configuration of the internal load balancer must be included and must be done first before moving the internal load balancer.
+The following steps show how to prepare the internal load balancer for the move using a Resource Manager template, and move the internal load balancer configuration to the target region using the Azure portal. As part of this process, the virtual network configuration of the internal load balancer must be included and must be done first before moving the internal load balancer.
 
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
@@ -57,13 +57,13 @@ The following steps show how to prepare the internal load balancer for the move
         }
     }
     ```
-7. Change the source virtual network name value in the editor to a name of your choice for the target VNET. Ensure you enclose the name in quotes.
+7. Change the source virtual network name value in the editor to a name of your choice for the target virtual network. Ensure you enclose the name in quotes.
 
 8. Select **Save** in the editor.
 
 9. Select **TEMPLATE** > **Edit template** to open the **template.json** file in the online editor.
 
-10. To edit the target region where the VNET will be moved, change the **location** property under resources:
+10. To edit the target region where the virtual network will be moved, change the **location** property under resources:
 
     ```json
     "resources": [
@@ -83,11 +83,11 @@ The following steps show how to prepare the internal load balancer for the move
 
     ```
 
-11. To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/).  The code for a region is the region name with no spaces, **Central US** = **centralus**.
+11. To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, **Central US** = **centralus**.
 
 12. You can also change other parameters in the **template.json** file if you choose, and are optional depending on your requirements:
 
-    * **Address Space** - The address space of the VNET can be altered before saving by modifying the **resources** > **addressSpace** section and changing the **addressPrefixes** property in the **template.json** file:
+    * **Address Space** - The address space of the virtual network can be altered before saving by modifying the **resources** > **addressSpace** section and changing the **addressPrefixes** property in the **template.json** file:
 
         ```json
                 "resources": [
@@ -138,7 +138,7 @@ The following steps show how to prepare the internal load balancer for the move
                 ]
         ```
 
-         In the **template.json** file, to change the address prefix, it must be edited in two places, the section listed above and the **type** section listed below.  Change the **addressPrefix** property to match the one above:
+         In the **template.json** file, to change the address prefix, it must be edited in two places, the section listed above and the **type** section listed below. Change the **addressPrefix** property to match the one above:
 
         ```json
          "type": "Microsoft.Network/virtualNetworks/subnets",
@@ -176,11 +176,11 @@ The following steps show how to prepare the internal load balancer for the move
 
 13. Select **Save** in the online editor.
 
-14. Select **BASICS** > **Subscription** to choose the subscription where the target VNET will be deployed.
+14. Select **BASICS** > **Subscription** to choose the subscription where the target virtual network will be deployed.
 
-15. Select **BASICS** > **Resource group** to choose the resource group where the target VNET will be deployed.  You can select **Create new** to create a new resource group for the target VNET.  Ensure the name isn't the same as the source resource group of the existing VNET.
+15. Select **BASICS** > **Resource group** to choose the resource group where the target virtual network will be deployed. You can select **Create new** to create a new resource group for the target virtual network. Ensure the name isn't the same as the source resource group of the existing virtual network.
 
-16. Verify **BASICS** > **Location** is set to the target location where you wish for the VNET to be deployed.
+16. Verify **BASICS** > **Location** is set to the target location where you wish for the virtual network to be deployed.
 
 17. Verify under **SETTINGS** that the name matches the name that you entered in the parameters editor above.
 
@@ -217,7 +217,7 @@ The following steps show how to prepare the internal load balancer for the move
     1. Select to the [Azure portal](https://portal.azure.com) > **Resource Groups** in another browser tab or window.
     2. Locate the target resource group that contains the moved virtual network from the steps above, and select it.
     3. Select > **Settings** > **Properties**.
-    4. On the right side of the portal, highlight the **Resource ID** and copy it to the clipboard.  Alternatively, you can select the **copy to clipboard** button to the right of the **Resource ID** path.
+    4. On the right side of the portal, highlight the **Resource ID** and copy it to the clipboard. Alternatively, you can select the **copy to clipboard** button to the right of the **Resource ID** path.
     5. Paste the resource ID into the **defaultValue** property into the **Edit Parameters** editor open in the other browser window or tab:
 
         ```json
@@ -251,7 +251,7 @@ The following steps show how to prepare the internal load balancer for the move
                 },
     ```
 
-9.  To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/).  The code for a region is the region name with no spaces, **Central US** = **centralus**.
+9. To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, **Central US** = **centralus**.
 
 10. You can also change other parameters in the template if you choose, and are optional depending on your requirements:
 
@@ -271,7 +271,7 @@ The following steps show how to prepare the internal load balancer for the move
         ```
       For more information on the differences between basic and standard sku load balancers, see [Azure Standard Load Balancer overview](./load-balancer-overview.md)
 
-    * **Availability zone** - You can change the zone(s) of the load balancer's frontend by changing the **zone** property. If the zone property isn't specified, the frontend is created as no-zone. You can specify a single zone to create a zonal frontend or all 3 zones for a zone-redundant frontend.
+    * **Availability zone** - You can change the zones of the load balancer's frontend by changing the **zone** property. If the zone property isn't specified, the frontend is created as no-zone. You can specify a single zone to create a zonal frontend or all three zones for a zone-redundant frontend.
 
         ```json
         "frontendIPConfigurations": [
@@ -406,27 +406,27 @@ The following steps show how to prepare the internal load balancer for the move
 
 13. Select **BASICS** > **Subscription** to choose the subscription where the target internal load balancer will be deployed.
 
-15. Select **BASICS** > **Resource group** to choose the resource group where the target load balancer will be deployed.  You can select **Create new** to create a new resource group for the target internal load balancer or choose the existing resource group that was created above for the virtual network.  Ensure the name isn't the same as the source resource group of the existing source internal load balancer.
+15. Select **BASICS** > **Resource group** to choose the resource group where the target load balancer will be deployed. You can select **Create new** to create a new resource group for the target internal load balancer or choose the existing resource group that was created previously for the virtual network. Ensure the name isn't the same as the source resource group of the existing source internal load balancer.
 
 16. Verify **BASICS** > **Location** is set to the target location where you wish for the internal load balancer to be deployed.
 
-17. Verify under **SETTINGS** that the name matches the name that you entered in the parameters editor above.  Verify the resource IDs are populated for any virtual networks in the configuration.
+17. Verify under **SETTINGS** that the name matches the name that you entered in the parameters editor previously. Verify the resource IDs are populated for any virtual networks in the configuration.
 
 18. Check the box under **TERMS AND CONDITIONS**.
 
 19. Select the **Purchase** button to deploy the target virtual network.
 
 ## Discard
 
-If you wish to discard the target virtual network and internal load balancer, delete the resource group that contains the target virtual network and internal load balancer.  To do so, select the resource group from your dashboard in the portal and select **Delete** at the top of the overview page.
+If you wish to discard the target virtual network and internal load balancer, delete the resource group that contains the target virtual network and internal load balancer. To do so, select the resource group from your dashboard in the portal and select **Delete** at the top of the overview page.
 
 ## Clean up
 
 To commit the changes and complete the move of the virtual network and internal load balancer, delete the source virtual network and internal load balancer or resource group. To do so, select the virtual network and internal load balancer or resource group from your dashboard in the portal and select **Delete** at the top of each page.
 
 ## Next steps
 
-In this tutorial, you moved an Azure internal load balancer from one region to another and cleaned up the source resources.  To learn more about moving resources between regions and disaster recovery in Azure, refer to:
+In this tutorial, you moved an Azure internal load balancer from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
 
 
 - [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)

articles/load-balancer/move-across-regions-internal-load-balancer-powershell.md

@@ -4,7 +4,7 @@ description: Use Azure Resource Manager template to move Azure internal Load Bal
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 06/27/2023
+ms.date: 06/27/2024
 ms.author: mbender 
 ms.custom: devx-track-azurepowershell, template-how-to, devx-track-arm-template, engagement-fy23
 ---