updated ESP UPN and troubleshooting for private endpoint

Author: omidm1

articles/hdinsight/hadoop/apache-hadoop-use-hive-beeline.md

@@ -54,19 +54,21 @@ Replace `<username>` with the name of an account on the domain with permissions
 
 ### Over public or private endpoints
 
-When connecting to a cluster using the public  or private endpoints, you must provide the cluster login account name (default `admin`) and password. For example, using Beeline from a client system to connect to the `<clustername>.azurehdinsight.net` address. This connection is made over port `443`, and is encrypted using SSL:
+When connecting to a cluster using the public or private endpoints, you must provide the cluster login account name (default `admin`) and password. For example, using Beeline from a client system to connect to the `<clustername>.azurehdinsight.net` address. This connection is made over port `443`, and is encrypted using SSL:
 
 ```bash
-beeline -u 'jdbc:hive2://clustername.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/hive2' -n admin -p password
+beeline -u 'jdbc:hive2://clustername.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/hive2' -n <username> -p password
 ```
 
 or for private endpoint:
 
 ```bash
-beeline -u 'jdbc:hive2://clustername-int.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/hive2' -n admin -p password
+beeline -u 'jdbc:hive2://clustername-int.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/hive2' -n <username> -p password
 ```
 
-Replace `clustername` with the name of your HDInsight cluster. Replace `admin` with the cluster login account for your cluster. Replace `password` with the password for the cluster login account.
+Replace `clustername` with the name of your HDInsight cluster. Replace `<username>` with the cluster login account for your cluster. Note for ESP clusters use the full UPN (e.g. [email protected]). Replace `password` with the password for the cluster login account.
+
+Private endpoints point to a basic load balancer which can only be accessed from the VNETs peered in the same region. See [this](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#what-are-the-constraints-related-to-global-vnet-peering-and-load-balancers) for more info. You can use `curl` command with `-v` option to troubleshoot any connectivity problem to with public or private endpoints before using beeline.
 
 ---
 
@@ -79,16 +81,18 @@ Apache Spark provides its own implementation of HiveServer2, which is sometimes
 The connection string used  is slightly different. Instead of containing `httpPath=/hive2` it's `httpPath/sparkhive2`:
 
 ```bash 
-beeline -u 'jdbc:hive2://clustername.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/sparkhive2' -n admin -p password
+beeline -u 'jdbc:hive2://clustername.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/sparkhive2' -n <username> -p password
 ```
 
 or for private endpoint:
 
 ```bash 
-beeline -u 'jdbc:hive2://clustername-int.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/sparkhive2' -n admin -p password
+beeline -u 'jdbc:hive2://clustername-int.azurehdinsight.net:443/;ssl=true;transportMode=http;httpPath=/sparkhive2' -n <username> -p password
 ```
 
-Replace `clustername` with the name of your HDInsight cluster. Replace `admin` with the cluster login account for your cluster. Replace `password` with the password for the cluster login account.
+Replace `clustername` with the name of your HDInsight cluster. Replace `<username>` with the cluster login account for your cluster. Note for ESP clusters use the full UPN (e.g. [email protected]). Replace `password` with the password for the cluster login account.
+
+Private endpoints point to a basic load balancer which can only be accessed from the VNETs peered in the same region. See [this](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#what-are-the-constraints-related-to-global-vnet-peering-and-load-balancers) for more info. You can use `curl` command with `-v` option to troubleshoot any connectivity problem to with public or private endpoints before using beeline.
 
 ---