docs(Azure): note for kubernetes get-credentials

Added link to create service principal steps for UI

Author: David Tesar

src/quickstart/provider/azure-acs/boot.md

@@ -70,7 +70,7 @@ $ az acs create --resource-group="${RG_NAME}" --location="${DC_LOCATION}" \
   --ssh-key-value @/home/myusername/.ssh/id_rsa.pub
 ```
 
-> Note: When `az acs create` starts, the provisioning process runs in the background by first creating a service principal and then waiting for AAD role to propagate.  After a few minutes the `az` command should return with information about the deployment created as shown below.
+> Note: When `az acs create` starts, the provisioning process runs in the background by first creating a service principal named ${SERVICE_NAME} assigned appropriate permissions.  After a few minutes the `az` command should return with information about the deployment created as shown below.
 
 ```
 {
@@ -116,10 +116,10 @@ When the required information is filled out, click "Ok".
 
 ![](images/step3.png)
 
-The next step takes the Service Principal name and password generated using the Azure CLI.
+Create a new service principal via [instructions at this link](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authenticate-service-principal-cli#create-service-principal-with-password) and put them into the UI.
 
-* Service Principal Client ID: the name of the principal created above e.g. `http://workflow-on-acs`
-* Service Principal Client Secret: the password returned by the Azure CLI e.g. 349d4728-438a-52a5-ad25-a740aa0bd240
+* Service Principal Client ID: the name of the principal created in the example document after the `-n` parameter e.g. `exampleapp`
+* Service Principal Client Secret: the password specified after the `-p` parameter or auto-generated in the Azure CLI e.g. 349d4728-438a-52a5-ad25-a740aa0bd240
 
 ![](images/step4.png)
 
@@ -154,7 +154,8 @@ Download the master kubernetes cluster configuration to the ~/.kube/config file
 ```console
 az acs kubernetes get-credentials --resource-group=$RG_NAME --name=$SERVICE_NAME
 ```
-
+ > Note: If the cluster was provisioned using any other SSH key than `/root/.ssh/id_rsa` then the `--ssh-key-file` parameter must be used pointing to the SSH key utilized to provision the cluster.
+ 
 Verify connectivity to the new ACS Kubernetes cluster by running `kubectl cluster-info`
 
 ```