Fix links.

Author: v-jaswel

articles/container-apps/billing.md

@@ -42,7 +42,7 @@ The following resources are free during each calendar month, per subscription:
 Free usage doesn't appear on your bill. You're only charged as your resource usage exceeds the monthly free grants amounts.
 
 > [!NOTE]
-> If you use Container Apps with [your own virtual network](networking-configuration.md#managed-resources) or your apps utilize other Azure resources, additional charges may apply.
+> If you use Container Apps with [your own virtual network](custom-virtual-networks.md#managed-resources) or your apps utilize other Azure resources, additional charges may apply.
 
 ### Resource consumption charges
 

articles/container-apps/custom-virtual-networks.md

@@ -26,7 +26,7 @@ As you create a virtual network, keep in mind the following situations:
   - You can restrict inbound requests to the environment exclusively to the VNet by deploying the environment as [internal](vnet-custom.md).
 
 > [!NOTE]
-> When you provide your own virtual network, additional [managed resources](networking-configuration.md#managed-resources) are created. These resources incur costs at their associated rates.
+> When you provide your own virtual network, additional [managed resources](custom-virtual-networks.md#managed-resources) are created. These resources incur costs at their associated rates.
 
 As you begin to design the network around your container app, refer to [Plan virtual networks](../virtual-network/virtual-network-vnet-plan-design-arm.md).
 

articles/container-apps/ingress-overview.md

@@ -73,7 +73,7 @@ HTTP ingress adds headers to pass metadata about the client request to your cont
 Container Apps supports TCP-based protocols other than HTTP or HTTPS. For example, you can use TCP ingress to expose a container app that uses the [Redis protocol](https://redis.io/topics/protocol).
 
 > [!NOTE]
-> External TCP ingress is only supported for Container Apps environments that use a [virtual network](vnet-custom.md). TCP ingress is not supported for apps that accept inbound traffic through a [private endpoint](custom-virtual-networks.md#private-endpoint).
+> External TCP ingress is only supported for Container Apps environments that use a [virtual network](vnet-custom.md). TCP ingress is not supported for apps that accept inbound traffic through a [private endpoint](networking.md#private-endpoint).
 
 With TCP ingress enabled, your container app:
 
@@ -119,7 +119,7 @@ Azure Container Apps provides built-in authentication and authorization features
 
 You can configure your app to support client certificates (mTLS) for authentication and traffic encryption. For more information, see [Configure client certificates](client-certificate-authorization.md).
 
-For details on how to use peer-to-peer environment level network encryption, see [networking configuration](./networking-configuration.md#peer-to-peer-encryption).
+For details on how to use peer-to-peer environment level network encryption, see [networking configuration](./environment-level-networking.md#peer-to-peer-encryption).
 
 ## Traffic splitting
 

articles/container-apps/networking.md

@@ -184,4 +184,4 @@ IP addresses are broken down into the following types:
 
 ## Next steps
 
-- [Networking configuration in Azure Container Apps environment](networking-configuration.md)
+- [Networking configuration in Azure Container Apps environment](environment-level-networking.md)

articles/container-apps/whats-new.md

@@ -84,7 +84,7 @@ Azure Container Apps updates can be found in [GitHub](https://aka.ms/aca/updates
 | [Generally Available: Session affinity](./sticky-sessions.md) | Session affinity enables you to route all requests from a single client to the same Container Apps replica. This is useful for stateful workloads that require session affinity. |
 | [Generally Available: Azure Key Vault references for secrets](https://azure.microsoft.com/updates/generally-available-azure-key-vault-references-for-secrets-in-azure-container-apps/) | Azure Key Vault references enable you to source a container app’s secrets from secrets stored in Azure Key Vault. Using the container app's managed identity, the platform automatically retrieves the secret values from Azure Key Vault and injects it into your application's secrets. |
 | [Public preview: additional TCP ports](./ingress-overview.md#additional-tcp-ports) | Azure Container Apps now support additional TCP ports, enabling applications to accept TCP connections on multiple ports. This feature is in preview. |
-| [Public preview: environment level peer-to-peer encryption](./networking-configuration.md#peer-to-peer-encryption) | When end-to-end encryption is required, peer-to-peer encryption will encrypt data transmitted between applications within an environment. |
+| [Public preview: environment level peer-to-peer encryption](./environment-level-networking.md#peer-to-peer-encryption) | When end-to-end encryption is required, peer-to-peer encryption will encrypt data transmitted between applications within an environment. |
 | [Retirement: ACA preview API versions 2022-06-01-preview and 2022-11-01-preview](https://azure.microsoft.com/updates/retirement-azure-container-apps-preview-api-versions-20220601preview-and-20221101preview/) | Starting on November 16, 2023, Azure Container Apps control plane API versions 2022-06-01-preview and 2022-11-01-preview will be retired. Before that date, migrate to the latest stable API version (2023-05-01) or latest preview API version (2023-04-01-preview). |
 | [Dapr: Stable Configuration API](https://docs.dapr.io/developing-applications/building-blocks/configuration/) | Dapr's Configuration API is now stable and supported in Azure Container Apps. Learn how to do [Dapr integration with Azure Container Apps](./dapr-overview.md)|
 

articles/spring-apps/migration/migrate-to-azure-container-apps-custom-domain.md

@@ -113,7 +113,7 @@ az containerapp env update \
 
 After you enable peer-to-peer-encryption, one container app can access other container apps using HTTPS with mTLS - for example, `https://<app-name>`. The certificate used in mTLS is system-assigned.
 
-For more information, see the [Peer-to-peer encryption](../../container-apps/networking-configuration.md#peer-to-peer-encryption) section of [Networking configuration in Azure Container Apps environment](../../container-apps/networking-configuration.md).
+For more information, see the [Peer-to-peer encryption](../../container-apps/environment-level-networking.md#peer-to-peer-encryption) section of [Networking configuration in Azure Container Apps environment](../../container-apps/networking-configuration.md).
 
 ## Traffic to external services
 

articles/spring-apps/migration/migrate-to-azure-container-apps-network.md

@@ -134,7 +134,7 @@ Azure Container Apps supports deployment with a private DNS zone. For more infor
 
 ## Access an app in Azure Container Apps within a customer virtual network
 
-Azure Container Apps provides both [Public network access](../../container-apps/networking.md#public-network-access) and [Private endpoint](../../container-apps/custom-virtual-networks.md#private-endpoint) features to expose applications to the internet or to secure them within a private network. Similarly, Azure Spring Apps supports these features as described in the following articles:
+Azure Container Apps provides both [Public network access](../../container-apps/networking.md#public-network-access) and [Private endpoint](../../container-apps/networking.md#private-endpoint) features to expose applications to the internet or to secure them within a private network. Similarly, Azure Spring Apps supports these features as described in the following articles:
 
 - [Access an app in Azure Spring Apps in a virtual network](../basic-standard/access-app-virtual-network.md)
 - [Access applications using Azure Spring Apps Standard consumption and dedicated plan in a virtual network](../consumption-dedicated/quickstart-access-standard-consumption-within-virtual-network.md)