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

Author: abhishjain002

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

@@ -33,7 +33,7 @@ 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.
 > * 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. 
-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).
+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).