Merge pull request #251921 from miwithro/patch-245

Update http-proxy.md

Author: prmerger-automator[bot]

articles/aks/http-proxy.md

@@ -5,7 +5,7 @@ ms.subservice: aks-networking
 ms.custom: devx-track-arm-template, devx-track-azurecli
 author: asudbring
 ms.topic: how-to
-ms.date: 02/01/2023
+ms.date: 09/18/2023
 ms.author: allensu
 ---
 
@@ -22,7 +22,6 @@ 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 HTTP/HTTPS proxy settings post cluster creation
 - User/Password authentication
 - Custom CAs for API server communication
 - Windows-based clusters
@@ -109,7 +108,10 @@ In your template, provide values for *httpProxy*, *httpsProxy*, and *noProxy*. I
 
 ## Updating Proxy configurations
 
-Values for *httpProxy*, and *httpsProxy* can't be changed after cluster creation. However, the values for *trustedCa* and *NoProxy* can be changed and applied to the cluster with the [az aks update][az-aks-update] command. An aks update for *NoProxy* will automatically inject new environment variables into pods with the new *NoProxy* values.  Pods must be rotated for the apps to pick it up.  For components under kubernetes, like containerd and the node itself, this won't take effect until a node image upgrade is performed.
+> [!NOTE]
+> If switching to a new proxy, the new proxy must already exist for the update to be successful.  Then, after the upgrade is completed the old proxy can be deleted.
+
+Values for *httpProxy*, *httpsProxy*, *trustedCa* and *NoProxy* can be changed and applied to the cluster with the [az aks update][az-aks-update] command. An aks update for *httpProxy*, *httpsProxy*, and/or *NoProxy* will automatically inject new environment variables into pods with the new *httpProxy*, *httpsProxy*, or *NoProxy* values.  Pods must be rotated for the apps to pick it up.  For components under kubernetes, like containerd and the node itself, this won't take effect until a node image upgrade is performed.
 
 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: