Merge pull request #98963 from jluk/outboundtype

Outboundtype

Author: PMEds28

articles/aks/TOC.yml

@@ -174,6 +174,8 @@
       href: internal-lb.md
     - name: Use a Standard Load Balancer
       href: load-balancer-standard.md
+    - name: Use a user defined route for egress
+      href: egress-outboundtype.md
     - name: Use a static IP address
       href: static-ip.md
     - name: Ingress

articles/aks/egress-outboundtype.md

@@ -55,7 +55,10 @@ The following limitations apply when you create and manage AKS clusters that sup
 
 ## Use the *Standard* SKU load balancer
 
-When you create an AKS cluster, by default, the *Standard* SKU load balancer is used when you run services in that cluster. For example, [the quickstart using the Azure CLI][aks-quickstart-cli] deploys a sample application that uses the *Standard* SKU load balancer. 
+When you create an AKS cluster, by default, the *Standard* SKU load balancer is used when you run services in that cluster. For example, [the quickstart using the Azure CLI][aks-quickstart-cli] deploys a sample application that uses the *Standard* SKU load balancer.
+
+> [!IMPORTANT]
+> Public IP addresses can be avoided by customizing a user-defined route (UDR). Specifying an AKS cluster's outbound type as UDR can skip IP provisioning and backend pool setup for the AKS created Azure load balancer. See [setting a cluster's `outboundType` to 'userDefinedRouting'](egress-outboundtype.md).
 
 ## Configure the load balancer to be internal