Merge pull request #212215 from gabesmsft/patch-8

Update ingress.md

Author: prmerger-automator[bot]

articles/container-apps/ingress.md

@@ -12,7 +12,7 @@ ms.custom: ignite-fall-2021, event-tier1-build-2022
 
 # Set up HTTPS ingress in Azure Container Apps
 
-Azure Container Apps allows you to expose your container app to the public web by enabling ingress. When you enable ingress, you don't need to create an Azure Load Balancer, public IP address, or any other Azure resources to enable incoming HTTPS requests.
+Azure Container Apps allows you to expose your container app to the public web, to your VNET, or to other container apps within your environment by enabling ingress. When you enable ingress, you don't need to create an Azure Load Balancer, public IP address, or any other Azure resources to enable incoming HTTPS requests.
 
 With ingress enabled, your container app features the following characteristics:
 
@@ -64,7 +64,11 @@ With ingress enabled, your application is assigned a fully qualified domain name
 | External | `<APP_NAME>.<UNIQUE_IDENTIFIER>.<REGION_NAME>.azurecontainerapps.io`|
 | Internal | `<APP_NAME>.internal.<UNIQUE_IDENTIFIER>.<REGION_NAME>.azurecontainerapps.io` |
 
-Your Container Apps environment has a single public IP address for applications with `external` ingress visibility, and a single internal IP address for applications with `internal` ingress visibility. Therefore, all applications within a Container Apps environment with `external` ingress visibility share a single public IP address. Similarly, all applications within a Container Apps environment with `internal` ingress visibility share a single internal IP address. HTTP traffic is routed to individual applications based on the FQDN in the host header.
+HTTP traffic is routed to individual applications based on the FQDN in the host header.
+
+For applications with external ingress visibility, the following conditions apply:
+- An internal Container Apps environment has a single private IP address for applications. For container apps in internal Environments, you must configure [DNS](./networking.md#dns) for VNET-scope ingress.
+- An external Container Apps environment or Container Apps environment that is not in a VNET has a single public IP address for applications.
 
 You can get access to the environment's unique identifier by querying the environment settings.