Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-mto-configure-portal-feedback

Author: rolyon

articles/aks/http-proxy.md

@@ -5,7 +5,7 @@ ms.service: azure-kubernetes-service
 ms.subservice: aks-networking
 author: asudbring
 ms.topic: how-to
-ms.date: 05/23/2022
+ms.date: 02/01/2023
 ms.author: allensu
 ---
 
@@ -22,7 +22,7 @@ Some more complex solutions may require creating a chain of trust to establish s
 The following scenarios are **not** supported:
 
 - Different proxy configurations per node pool
-- Updating proxy settings post cluster creation
+- Updating HTTP/HTTPS proxy settings post cluster creation
 - User/Password authentication
 - Custom CAs for API server communication
 - Windows-based clusters
@@ -105,11 +105,11 @@ Deploying an AKS cluster with an HTTP proxy configured using an ARM template is
 
 In your template, provide values for *httpProxy*, *httpsProxy*, and *noProxy*. If necessary, provide a value for *trustedCa*. Deploy the template, and your cluster should initialize with your HTTP proxy configured on the nodes.
 
-## Handling CA rollover
+## Updating Proxy configurations
 
-Values for *httpProxy*, *httpsProxy*, and *noProxy* can't be changed after cluster creation. However, to support rolling CA certs, the value for *trustedCa* can be changed and applied to the cluster with the [az aks update][az-aks-update] command.
+Values for *httpProxy*, and *httpsProxy* can't be changed after cluster creation. However, to support rolling CA certs and No Proxy settings, the values for *trustedCa* and *NoProxy* can be changed and applied to the cluster with the [az aks update][az-aks-update] command.
 
-For example, assuming a new file has been created with the base64 encoded string of the new CA cert called *aks-proxy-config-2.json*, the following action updates the cluster:
+For example, assuming a new file has been created with the base64 encoded string of the new CA cert called *aks-proxy-config-2.json*, the following action updates the cluster.  Or, you need to add new endpoint urls for your applications to No Proxy:
 
 ```azurecli
 az aks update -n $clusterName -g $resourceGroup --http-proxy-config aks-proxy-config-2.json
@@ -141,4 +141,4 @@ For more information regarding the network requirements of AKS clusters, see [co
 [az-provider-register]: /cli/azure/provider#az_provider_register
 [az-extension-add]: /cli/azure/extension#az_extension_add
 [az-extension-update]: /cli/azure/extension#az-extension-update
-[install-azure-cli]: /cli/azure/install-azure-cli
+[install-azure-cli]: /cli/azure/install-azure-cli