refine aks quickstart and trouble shooting doc

Author: houk-ms

articles/service-connector/how-to-use-service-connector-in-aks.md

@@ -185,6 +185,28 @@ If there's an error during the extension installation, and the error message in
 
 ### Common errors and mitigations
 
+#### Extension creation errors
+
+**Error Message:**
+`Unable to get a response from the agent in time`.
+
+**Mitigation:**
+Refer to [extension creation errors](/troubleshoot/azure/azure-kubernetes/extensions/cluster-extension-deployment-errors#extension-creation-errors)
+
+
+#### Helm errors
+
+**Error Message:**
+- `Timed out waiting for resource readiness`
+- `Unable to download the Helm chart from the repo URL`
+- `Helm chart rendering failed with given values`
+- `Resource already exists in your cluster`
+- `Operation is already in progress for Helm`
+
+**Mitigation:**
+Refer to [Helm errors](/troubleshoot/azure/azure-kubernetes/extensions/cluster-extension-deployment-errors#helm-errors)
+
+
 #### Conflict
 
 **Error Message:**
@@ -202,18 +224,6 @@ This error usually occurs when attempting to create a service connection while t
 - Ensure your cluster is in a "Succeeded" state and retry the creation.
 
 
-#### Timeout
-
-**Error Message:**
-- `Long running operation failed with status 'Failed'. Unable to get a response from the Agent in time`.
-- `Timed out waiting for the resource to come to a ready/completed state`
-
-**Reason:**
-This error often happens when the Kubernetes job used to create or update the Service Connector cluster extension fails to be scheduled due to resource limitations or other issues.
-
-**Mitigation:**
-Refer to [Check Kubernetes cluster logs](#check-kubernetes-cluster-logs) to identify and resolve the detailed reasons. A common issue is that no nodes are available due to preemption. In this case, consider adding more nodes or enabling auto-scaling for your nodes.
-
 #### Unauthorized resource access
 
 **Error Message:**
@@ -225,6 +235,7 @@ Service Connector requires permissions to operate the Azure resources you want t
 **Mitigation:**
 Check the permissions on the Azure resources specified in the error message. Obtain the required permissions and retry the creation.
 
+
 #### Missing subscription registration
 **Error Message:**
 `The subscription is not registered to use namespace 'Microsoft.KubernetesConfiguration'`
@@ -239,21 +250,6 @@ Register the `Microsoft.KubernetesConfiguration` resource provider by running th
 az provider register -n Microsoft.KubernetesConfiguration
 ```
 
-#### Other issues
-
-If the above mitigations don't resolve your issue, try resetting the service connector cluster extension by removing it and then retrying the creation. This method is expected to resolve most issues related to the Service Connector cluster extension.
-
-Use the following CLI commands to reset the extension:
-
-```azurecli
-az extension add --name k8s-extension
-
-az k8s-extension delete \
-    --resource-group <MyClusterResourceGroup> \
-    --cluster-name <MyCluster> \
-    --cluster-type managedClusters \
-    --name sc-extension
-```
 
 ## Next steps
 

articles/service-connector/quickstart-portal-aks-connection.md

@@ -60,6 +60,8 @@ Sign in to the Azure portal at [https://portal.azure.com/](https://portal.azure.
     ---
 
 1. Select **Next: Networking** to configure the network access to your target service and select **Configure firewall rules to enable access to your target service**.
+    > [!NOTE]
+    > Service Connector for AKS now supports only the firewall option. Private link and service endpoint options are not supported.
 1. Select **Next: Review + Create**  to review the provided information. Then select **Create** to create the service connection. This operation may take a minute to complete.
 
 ## View service connections in AKS cluster