Merge pull request #297120 from abhishjain002/patch-4

Updated note with NAT Gateway metric evaluation for slowness

Author: prmerger-automator[bot]

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

@@ -6,7 +6,7 @@ ms.topic: how-to
 author: abhishjain002
 ms.author: abhishjain
 ms.reviewer: sairamyeturi
-ms.date: 03/03/2025
+ms.date: 03/31/2025
 ---
 
 # Basic Load balancer deprecation: Guidelines for Azure HDInsight
@@ -132,7 +132,12 @@ NAT gateway provides outbound network connectivity for the cluster. NSG controls
 
          
        * **Method 2:** Create a new subnet and then create the cluster with the new subnet.
- 
+
+> [!IMPORTANT]
+> * If you experience job slowness or network issues after cluster recreation with a standard load balancer, check the "Total SNAT Connection Count" and "Dropped Packets" on your NAT Gateway. High values may indicate SNAT port exhaustion. To address this, consider implementing one of the following methods:
+>   * Bind additional IP addresses or IP prefixes to your NAT Gateway. For more information, see [Troubleshoot Azure NAT Gateway connectivity](/azure/nat-gateway/troubleshoot-nat-connectivity) and [Metrics and alerts for Azure NAT Gateway](/azure/nat-gateway/nat-metrics#total-snat-connection-count).
+>   * Enable private link to storage accounts which could reduce SNAT port dependency. For more information, see [Use private endpoints for Azure Storage](/azure/storage/common/storage-private-endpoints).
+
 > [!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.
 

articles/hdinsight/use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md

@@ -3,10 +3,10 @@ title: Use Managed Identity for SQL Database authentication in Azure HDInsight
 description: Learn how to use managed identity for SQL Database authentication in Azure HDInsight. 
 ms.service: azure-hdinsight 
 ms.topic: how-to 
-author: hareshg
-ms.author: hgowrisankar
+author: abhishjain002
+ms.author: abhishjain
 ms.reviewer: nijelsf
-ms.date: 01/09/2025 
+ms.date: 03/31/2025 
 ---
 
 # Use Managed Identity for SQL Database authentication in Azure HDInsight 
@@ -33,7 +33,6 @@ The Managed Identity (MI) option is available for the following Databases:
 > * It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
 > * When you recreate an MSI with the same name, you must recreate the contained user and reassign roles, as the new MSI will have different object and client IDs even if the name remains unchanged.
 
-
 ## Steps to Use Managed Identity during cluster creation in Azure portal
 
 1. During cluster creation, navigate to the Storage section and select the SQL database for Ambari/Hive/Oozie. Choose Managed Identity as the Authentication method.
@@ -56,7 +55,7 @@ Object ID of managed identity can be obtained from portal on the managed identit
    > For example: 
    > * MSI Name: contosoMSI 
    > * Object ID: `aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb`
-   > * user_name could be `contosoMSI-2ba6c`
+   > * user_name could be `contosoMSI_aaaaaaaa`
 
 
     ```