Update load-balancer-migration-guidelines.md

abhishjain002 · web-flow · commit 2c11e4286bfe · 2024-10-18T13:08:24.000+05:30
diff --git a/articles/hdinsight/load-balancer-migration-guidelines.md b/articles/hdinsight/load-balancer-migration-guidelines.md
@@ -16,7 +16,7 @@ This transition is done in line with the announcement of retirement of Azure bas
 
 ### Long running clusters (when you don’t create and delete cluster frequently for your use case)
 
-   * **Scenario 1:**  Existing HDInsight clusters without custom virtual network (No virtual network provided during cluster creation).
+   * **Scenario 1:**  Existing HDInsight clusters without custom virtual network (No virtual network used during cluster creation).
 
      * No immediate disruption until Mar 31, 2025. However, we strongly recommend re-creating the cluster before Mar 31, 2025 to avoid potential disruption.
 
@@ -26,7 +26,7 @@ This transition is done in line with the announcement of retirement of Azure bas
 
 ### New cluster creation
 
-* **Scenario 1:** HDInsight clusters without custom virtual network (No virtual network selected during cluster creation).
+* **Scenario 1:** HDInsight clusters without custom virtual network (Creating cluster without any virtual network).
 
    * In this case, no impact. You can recreate the cluster directly.
 
@@ -65,66 +65,69 @@ This transition is done in line with the announcement of retirement of Azure bas
 
       The most recommended way is to attach a network security group and a NAT gateway to the subnet. Since the existing subnet which has HDInsight clusters with Azure basic load balancers can't be associated with an NAT gateway due to incompatibility with basic load balancer, there are two scenarios:
 
-#### Case 1: Existing subnet has no HDInsight clusters with Azure Basic Load Balancers
+      * **Case 1:** Existing subnet has no HDInsight clusters with Azure Basic Load Balancers
 
-   Follow these steps:
+        Follow these steps:
 
-   1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
-     
-      > [!NOTE]
-      > You could use an existing NAT gateway and NSG.
+         1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
 
-      Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
-       
-      You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
-    
-      
-1. Associate the NAT gateway with your subnet along with a network security group.
+            > [!NOTE]
+            > You could use an existing NAT gateway and NSG.
+            
+            Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
 
-      :::image type="content" source="./media/load-balancer-migration-guidelines/associate-gateway.png" alt-text="Screenshot showing how to associate gateway." border="true" lightbox="./media/load-balancer-migration-guidelines/associate-gateway.png":::
+            You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
+         
+        1. Associate the NAT gateway with your subnet along with a network security group.
 
-1. Create the cluster with the subnet.
-              
-    :::image type="content" source="./media/load-balancer-migration-guidelines/security-networking.png" alt-text="Screenshot showing security networking tab." border="true" lightbox="./media/load-balancer-migration-guidelines/security-networking.png":::
-   
-      > [!NOTE]
-      > If you are unable to find the NAT gateway, see, [FAQ of the NAT gateway (Azure NAT Gateway frequently asked questions)](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway). 
+           :::image type="content" source="./media/load-balancer-migration-guidelines/associate-gateway.png" alt-text="Screenshot showing how to associate gateway." border="true" lightbox="./media/load-balancer-migration-guidelines/associate-gateway.png":::
 
-#### Case 2: Existing subnet has HDInsight clusters with Azure Basic load balancers
-            
-   Consider one of these methods:
+        1. Create the cluster with the subnet.
 
-   * **Method 1:** The most recommended way is to associate a NAT gateway to the subnet along with network security group.
+           :::image type="content" source="./media/load-balancer-migration-guidelines/security-networking.png" alt-text="Screenshot showing security networking tab." border="true" lightbox="./media/load-balancer-migration-guidelines/security-networking.png":::
 
-      According to [Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway), NAT gateway is incompatible with Azure basic load balancer.
+           > [!NOTE]
+           > If you are unable to find the NAT gateway, see, [FAQ of the NAT gateway (Azure NAT Gateway frequently asked questions)](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway). 
 
-      To associate with a NAT Gateway, perform the following steps.
+     * **Case 2:** Existing subnet has HDInsight clusters with Azure Basic load balancers
+            
+        Consider one of these methods:
 
-      1. Delete all the existing HDInsight clusters with Azure basic load balancers in this subnet.
+         * **Method 1:** The most recommended way is to associate a NAT gateway to the subnet along with network security group.
 
-      1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
-         
-         > [!NOTE]
-         > You could use an existing NAT gateway and NSG.
+           According to [Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway), NAT gateway is incomaptible with Azure basic load balancer.
+
+           To associate with a NAT Gateway, perform the following steps.
+
+              1. Delete all the existing HDInsight clusters with Azure basic load balancers in this subnet.
+        
+              1. Create a new NAT gateway and a new Network Security Group(NSG) or use the existing ones.
          
-         Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
-          
-         You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
+                 > [!NOTE]
+                 > You could use an existing NAT gateway and NSG.
+                 
+                 Follow this document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
+                  
+                 You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
            
-       1. Associate the subnet with the NAT gateway and network security group.
+             1. Associate the subnet with the NAT gateway and network security group.
 
-          :::image type="content" source="./media/load-balancer-migration-guidelines/add-subnet.png" alt-text="Screenshot showing how to add subnet." border="true" lightbox="./media/load-balancer-migration-guidelines/add-subnet.png":::
+                :::image type="content" source="./media/load-balancer-migration-guidelines/add-subnet.png" alt-text="Screenshot showing how to add subnet." border="true" lightbox="./media/load-balancer-migration-guidelines/add-subnet.png":::
          
-          > [!NOTE]
-          > If you are unable to find the NAT gateway, see, [FAQ of the NAT gateway (Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway). 
+                > [!NOTE]
+                > If you are unable to find the NAT gateway, see, [FAQ of the NAT gateway (Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway). 
     
-      1. Re-create the clusters with the subnet.
-         :::image type="content" source="./media/load-balancer-migration-guidelines/virtual-network.png" alt-text="Screenshot showing virtual network." border="true" lightbox="./media/load-balancer-migration-guidelines/virtual-network.png":::
+            1. Re-create the clusters with the subnet.
+              
+               :::image type="content" source="./media/load-balancer-migration-guidelines/virtual-network.png" alt-text="Screenshot showing virtual network." border="true" lightbox="./media/load-balancer-migration-guidelines/virtual-network.png":::
 
    
-   * **Method 2:** Select option other than **Associate a NAT gateway to the subnet** provided in [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and follow the instruction for the selected option.
-
-   * **Method 3:** Create a new subnet and then create the cluster with the new subnet.
+       * **Method 2:** Select option other than **Associate a NAT gateway to the subnet** provided in [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and follow the instruction for the selected option.
+  
+       * **Method 3:** Create a new subnet and then create the cluster with the new subnet.
+ 
+> [!NOTE]
+> If you are using an ESP cluster with MFA disabled, ensure to check the MFA status once cluster is recreated using a NAT gateway.
 
 ## Next steps
 
