Skip to content

Commit 082255e

Browse files
Update use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md
1 parent 028ab50 commit 082255e

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

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

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@ title: Use Managed Identity for SQL Database authentication in Azure HDInsight
33
description: Learn how to use managed identity for SQL Database authentication in Azure HDInsight.
44
ms.service: azure-hdinsight
55
ms.topic: how-to
6-
author: hareshg
7-
ms.author: hgowrisankar
6+
author: abhishjain002
7+
ms.author: abhishjain
88
ms.reviewer: nijelsf
9-
ms.date: 03/27/2025
9+
ms.date: 03/31/2025
1010
---
1111

1212
# Use Managed Identity for SQL Database authentication in Azure HDInsight
@@ -32,10 +32,6 @@ The Managed Identity (MI) option is available for the following Databases:
3232
> [!IMPORTANT]
3333
> * It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
3434
> * 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.
35-
> * Following the migration to a standard load balancer, if you experience job slowness or network connectivity issues within your cluster, please examine the "Total SNAT Connection Count" and "Dropped Packets" metrics of your NAT Gateway. The hiigh values in these metrics may indicate that job slowness is due to SNAT port exhaustion. It is advisable to bind additional IP addresses or IP prefixes to your NAT Gateway.
36-
For further information, please refer to [Troubleshoot Azure NAT Gateway connectivity - Azure NAT Gateway](/azure/nat-gateway/troubleshoot-nat-connectivity.md) and [Metrics and alerts for Azure NAT Gateway - Azure NAT Gateway](/azure/nat-gateway/nat-metrics#total-snat-connection-count.md).
37-
38-
3935
4036
## Steps to Use Managed Identity during cluster creation in Azure portal
4137

@@ -59,7 +55,7 @@ Object ID of managed identity can be obtained from portal on the managed identit
5955
> For example:
6056
> * MSI Name: contosoMSI
6157
> * Object ID: `aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb`
62-
> * user_name could be `contosoMSI-2ba6c`
58+
> * user_name could be `contosoMSI_aaaaaaaa`
6359
6460

6561
```

0 commit comments

Comments
 (0)