Edits

Author: tejaswikolli-web

articles/container-registry/container-registry-private-link.md

@@ -465,9 +465,18 @@ If you created all the Azure resources in the same resource group and no longer
 az group delete --name $RESOURCE_GROUP
 ```
 
-## Integrating with AKS
+## Integrating with a registry with private link enabled
 
-Once the private link configuration to the ACR is successfully complete, the registry handles the pull requests through the data endpoints. You have to update the routing configuration for the client proxy and client firewall with the data endpoints to handle the pull requests successfully. A client proxy will provide central traffic control to the [outbound requests][outbound-connection]. To handle local traffic a client proxy is not required, you can add into `noProxy` section to bypass the proxy. Requests to token server over private endpoint connection doesn't require the data endpoint configuration.
+To pull content from a registry with private link enabled, clients must allow access to the registry REST endpoint, as well as all regional data endpoints." The client proxy or firewall must allow access to
+
+REST endpoint: `.azurecr.io`
+Data endpoint(s): `..data.azurecr.io`
+
+For a geo-replicated registry, customer needs to configure access to the data endpoint for each regional replica.
+
+You have to update the routing configuration for the client proxy and client firewall with the data endpoints to handle the pull requests successfully. A client proxy will provide central traffic control to the [outbound requests][outbound-connection]. To handle local traffic a client proxy is not required, you can add into `noProxy` section to bypass the proxy. Learn more about [HTTP proxy doc](../aks/http-proxy.md) to integrate with AKS. 
+
+Requests to token server over private endpoint connection doesn't require the data endpoint configuration.
 
 ## Next steps