Modify Load balancer Page

Modify Load balancer Page
Ref-Abhishek Jain, Zhilong Hong

Author: sreekzz

articles/hdinsight/load-balancer-migration-guidelines.md

@@ -3,7 +3,7 @@ title: Basic Load balancer deprecation - Guidelines for Azure HDInsight
 description: Guidelines to transition to standard load balancer for Azure HDInsight.
 ms.service: azure-hdinsight
 ms.topic: how-to
-ms.date: 11/26/2024
+ms.date: 01/03/2025
 ---
 
 # Basic Load balancer deprecation: Guidelines for Azure HDInsight
@@ -12,6 +12,11 @@ This article describes the details about the impact on HDInsight clusters and th
 
 This transition is done in line with the announcement of retirement of Azure basic load balancer by 30 September 2025 and no support for new deployment by Mar 31, 2025. For more information, see [Azure Basic Load Balancer retires on 30 September 2025. Upgrade to Standard Load Balancer](https://azure.microsoft.com/updates/azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer).
 
+As part of the migration from the basic load balancer to the standard load balancer, the public IP address will be upgraded from basic SKU to standard SKU. For more details, see [Upgrade to Standard SKU public IP addresses in Azure by 30 September 2025 - Basic SKU will be retired](https://azure.microsoft.com/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired). Additionally, default outbound access will be deprecated. For further information, see [Default outbound access for VMs in Azure will be retired - transition to a new method of internet access](https://azure.microsoft.com/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access).
+
+> [!NOTE]
+> Please be advised not to alter any components created by HDInsight within your VNet, including load balancers, IP addresses, network interfaces, etc. Any modifications you make to these components may be reverted during cluster maintenance. 
+
 ## Impact on HDInsight clusters
 
 ### Long running clusters (when you don’t create and delete cluster frequently for your use case)
@@ -26,7 +31,8 @@ This transition is done in line with the announcement of retirement of Azure bas
 
 ### New cluster creation
 
-There are several ways provided in the document [Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections) that could provide outbound connectivity for a cluster. The only compatible way with HDInsight is to associate a NAT gateway to the subnet, which supports auto-scaling features of HDInsight clusters. 
+Due to the deprecation of the default outbound access, a new outbound connectivity method is required by the HDInsight cluster. There are several ways provided in the document [Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections) that could provide outbound connectivity for a cluster. The only compatible way with HDInsight is to associate a NAT gateway to the subnet, which supports auto-scaling features of HDInsight clusters. 
+NAT gateway provides outbound network connectivity for the cluster. NSG controls both the inbound and outbound traffic, which is required by the standard load balancer. 
 
 * **Scenario 1:** HDInsight clusters without custom virtual network (Creating cluster without any virtual network).
 
@@ -38,7 +44,8 @@ There are several ways provided in the document [Source Network Address Translat
 
       **Approach 1:** Create the cluster with a new subnet
 
-      1. Create a new NAT gateway and a new Network Security Group (NSG) or use the existing ones.
+      1. Create a new NAT gateway and a new Network Security Group (NSG) or use the existing ones. NAT gateway provides outbound network connectivity for the cluster. NSG controls both the inbound and outbound traffic, which is required by the standard load balancer.
+         
 
          > [!NOTE]
          > You can use an existing NAT gateway and NSG.
@@ -65,7 +72,7 @@ There are several ways provided in the document [Source Network Address Translat
 
         Follow these steps:
 
-         1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
+         1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones. NAT gateway provides outbound network connectivity for the cluster. NSG controls both the inbound and outbound traffic, which is required by the standard load balancer.
 
             > [!NOTE]
             > You could use an existing NAT gateway and NSG.