Added service connector links into AKS docs

Author: schaffererin

articles/aks/csi-secrets-store-identity-access.md

@@ -347,10 +347,10 @@ A key vault certificate also contains public x509 certificate metadata. The key
 
 ## Next steps
 
-In this article, you learned how to create and provide an identity to access your Azure Key Vault. If you want to configure extra configuration options or perform troubleshooting, continue to the next article.
+In this article, you learned how to create and provide an identity to access your Azure Key Vault. The [Service Connector](../service-connector/overview.md) integration helps simplify the connection configuration for AKS workloads and Azure backing services. It securely handles authentication and network configurations and follows best practices for connecting to Azure services. For more information, see [Use the Azure Key Vault provider for Secrets Store CSI Driver in an AKS cluster](../service-connector/tutorial-python-aks-keyvault-csi-driver.md) and the [Service Connector introduction](https://azure.github.io/AKS/2024/05/23/service-connector-intro).
+
+If you want to configure extra configuration options or perform troubleshooting, see [Configuration options and troubleshooting resources for Azure Key Vault provider with Secrets Store CSI Driver in AKS](./csi-secrets-store-configuration-options.md).
 
-> [!div class="nextstepaction"]
-> [Configuration options and troubleshooting resources for Azure Key Vault provider with Secrets Store CSI Driver in AKS](./csi-secrets-store-configuration-options.md)
 
 <!-- LINKS INTERNAL -->
 

articles/aks/workload-identity-deploy-cluster.md

@@ -258,6 +258,8 @@ az aks update --resource-group "${RESOURCE_GROUP}" --name myAKSCluster --disable
 
 In this article, you deployed a Kubernetes cluster and configured it to use a workload identity in preparation for application workloads to authenticate with that credential. Now you're ready to deploy your application and configure it to use the workload identity with the latest version of the [Azure Identity][azure-identity-libraries] client library. If you can't rewrite your application to use the latest client library version, you can [set up your application pod][workload-identity-migration] to authenticate using managed identity with workload identity as a short-term migration solution.
 
+The [Service Connector](../service-connector/overview.md) integration helps simplify the connection configuration for AKS workloads and Azure backing services. It securely handles authentication and network configurations and follows best practices for connecting to Azure services. For more information, see [Connect to Azure OpenAI Service in AKS using Workload Identity](../service-connector/tutorial-python-aks-openai-workload-identity.md) and the [Service Connector introduction](https://azure.github.io/AKS/2024/05/23/service-connector-intro).
+
 <!-- EXTERNAL LINKS -->
 [kubectl-describe]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#describe