(ForumsTeam) fixes MicrosoftDocs/azure-docs#47239

Author: Karishma-Tiwari-MSFT

articles/aks/troubleshooting.md

@@ -55,7 +55,7 @@ The reason for the warnings on the dashboard is that the cluster is now enabled
 
 ## I can't connect to the dashboard. What should I do?
 
-The easiest way to access your service outside the cluster is to run `kubectl proxy`, which proxies requests sent to your localhost port 8001 to the Kubernetes API server. From there, the API server can proxy to your service: `http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/#!/node?namespace=default`.
+The easiest way to access your service outside the cluster is to run `kubectl proxy`, which proxies requests sent to your localhost port 8001 to the Kubernetes API server. From there, the API server can proxy to your service: `http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/`.
 
 If you don’t see the Kubernetes dashboard, check whether the `kube-proxy` pod is running in the `kube-system` namespace. If it isn't in a running state, delete the pod and it will restart.
 
@@ -491,4 +491,4 @@ This error is due to an upstream cluster autoscaler race condition where the clu
 
 <!-- LINKS - internal -->
 [view-master-logs]: view-master-logs.md
-[cluster-autoscaler]: cluster-autoscaler.md
+[cluster-autoscaler]: cluster-autoscaler.md