diff --git a/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md b/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md
index f15983d..053c1de 100644
--- a/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md
+++ b/10.1-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts.md
@@ -10,6 +10,32 @@ Despite an AKS created and kubectl and Azure CLI installed and configured to use
 
 You need to have helm installed on your machine, and Tiller must be installed on the AKS. Follow [these instructions](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/kubernetes-helm.md) to setup Helm and Tiller for AKS
 
+**Note** If your ASK cluster is not RBAC-enabled (default option in portal) you may receive following error when running a helm command:
+
+```
+Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp [::1]:8080: connect: connection refused
+```
+
+If so, type:
+
+```
+kubectl --namespace=kube-system edit deployment/tiller-deploy
+```
+
+Your default text editor will popup with the YAML definition of the tiller deploy. Search for:
+
+```
+automountServiceAccountToken: false
+```
+
+And change it to:
+
+```
+automountServiceAccountToken: false
+```
+
+Save the file and close the editor. This should reapply the deployment in the cluster. Now Helm commands should work.
+
 ### AKS created with _http routing_ enabled (optional but recommended)
 
 If creating AKS using CLI be sure to use `--enable-addons http_application_routing` in `az aks create` command. If using Azure Portal just be sure to check the checkbox "Http application routing" on "Networking" settings. For more info, read the [documentation](https://docs.microsoft.com/en-us/azure/aks/http-application-routing)