Merge pull request #287841 from aimee-littleton/patch-774711

Update troubleshoot-nat-and-azure-services.md

Author: prmerger-automator[bot]

articles/nat-gateway/troubleshoot-nat-and-azure-services.md

@@ -67,6 +67,13 @@ NAT gateway can be deployed with AKS clusters in order to allow for explicit out
 
 Learn more at [Managed NAT Gateway](/azure/aks/nat-gateway).
 
+### Connecting from AKS cluster to the AKS API server over the internet
+
+To manage an AKS cluster, you interact with its API server. When you create a non-private cluster that resolves to the API server's fully qualified domain name (FQDN), the API server is assigned a public IP address by default. After you attach a NAT Gateway to the subnets of your AKS cluster, NAT Gateway will be used to connect to the public IP of the AKS API server. See the following documentation for additional information and design guidance:
+* [Access an AKS API server](/azure/architecture/guide/security/access-azure-kubernetes-service-cluster-api-server)
+* [Use API Management with AKS](/azure/api-management/api-management-kubernetes)
+* [Define API server authorized IP ranges](/azure/aks/api-server-authorized-ip-ranges)
+
 ### Can't update my NAT gateway IPs or idle timeout timer for an AKS cluster 
 
 Public IP addresses and the idle timeout timer for NAT gateway can be updated with the `az aks update` command for a managed NAT gateway ONLY.