Merge pull request #260925 from cachai2/cliTCPports

fix CLI instructions

Author: prmerger-automator[bot]

articles/container-apps/ingress-how-to.md

@@ -61,7 +61,7 @@ az containerapp ingress enable \
 | `--target-port` | targetPort | The port your container listens to for incoming requests. | Set this value to the port number that your container uses. Your application ingress endpoint is always exposed on port `443`. | Yes |
 |`--exposed-port` | exposedPort | (TCP ingress only) An port for TCP ingress. If `external` is `true`, the value must be unique in the Container Apps environment if ingress is external. | A port number from `1` to `65535`. (can't be `80` or `443`) | No |
 |`--transport` | transport | The transport protocol type. | auto (default) detects HTTP/1 or HTTP/2,  `http` for HTTP/1, `http2` for HTTP/2, `tcp` for TCP. | No |
-
+ 
 ::: zone-end
 
 ::: zone pivot="azure-portal"
@@ -149,6 +149,9 @@ Disable ingress for your container app by omitting the `ingress` configuration p
 
 You can expose additional TCP ports from your application. To learn more, see the [ingress concept article](ingress-overview.md#additional-tcp-ports).
 
+> [Note]
+> To use this preview feature, you must have the container apps CLI extension. Run `az extension add -n containerapp` in order to install the latest version of the container apps CLI extension.
+
 
 ::: zone pivot="azure-cli"
 

articles/container-apps/ingress-overview.md

@@ -82,6 +82,9 @@ With TCP ingress enabled, your container app:
 
 In addition to the main HTTP/TCP port for your container apps, you might expose additional TCP ports to enable applications that accept TCP connections on multiple ports. This feature is in preview.
 
+> [!NOTE]
+> As the feature is in preview, make sure you are using the latest preview version of the container apps CLI extension.
+
 The following apply to additional TCP ports:
 - Additional TCP ports can only be external if the app itself is set as external and the container app is using a custom VNet.
 - Any externally exposed additional TCP ports must be unique across the entire Container Apps environment. This includes all external additional TCP ports, external main TCP ports, and 80/443 ports used by built-in HTTP ingress. If the additional ports are internal, the same port can be shared by multiple apps.