Merge pull request #293098 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/container-apps/how-to-use-private-endpoint.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, ignite-2024
 ms.topic:  how-to
-ms.date: 11/6/2024
+ms.date: 1/14/2025
 ms.author: cshoe
 zone_pivot_groups: azure-cli-or-portal
 ---
@@ -127,8 +127,8 @@ RESOURCE_GROUP="my-container-apps"
 LOCATION="centralus"
 ENVIRONMENT_NAME="my-environment"
 CONTAINERAPP_NAME="my-container-app"
-VNET_NAME="my-custom-vnet"
-SUBNET_NAME="my-custom-subnet"
+VNET_NAME="my-vnet"
+SUBNET_NAME="my-subnet"
 PRIVATE_ENDPOINT="my-private-endpoint"
 PRIVATE_ENDPOINT_CONNECTION="my-private-endpoint-connection"
 PRIVATE_DNS_ZONE="privatelink.${LOCATION}.azurecontainerapps.io"
@@ -147,10 +147,7 @@ az group create \
 
 ## Create a virtual network
 
-An environment in Azure Container Apps creates a secure boundary around a group of container apps. Container Apps deployed to the same environment are deployed in the same virtual network and write logs to the same Log Analytics workspace.
-
-1. Create an Azure virtual network (VNet) to associate with the Container Apps environment. The VNet must have a subnet available for the environment deployment.
-    You can use an existing VNet, but private endpoints are only supported by workload profiles environments, which require a subnet with a minimum CIDR range of `/27` or larger. To learn more about subnet sizing, see the [networking architecture overview](./networking.md#subnet).
+1. Create an Azure virtual network (VNet). You can use an existing VNet, but private endpoints are only supported by workload profiles environments, which require a subnet with a minimum CIDR range of `/27` or larger. To learn more about subnet sizing, see the [networking architecture overview](./networking.md#subnet).
 
     ```azurecli
     az network vnet create \
@@ -183,7 +180,7 @@ An environment in Azure Container Apps creates a secure boundary around a group
 
 ## Create an environment
 
-1. Create the Container Apps environment using the VNet deployed in the preceding steps. Private endpoints are only supported by workload profiles environments, which is the default type for new environments.
+1. Create the Container Apps environment. Private endpoints are only supported by workload profiles environments, which is the default type for new environments.
 
     ```azurecli
     az containerapp env create \
@@ -417,7 +414,7 @@ The administrator password has the following requirements:
 
 ## Clean up resources
 
-If you're not going to continue to use this application, you can remove the **my-container-apps** resource group. This deletes the Azure Container Apps instance and all associated services. It also deletes the resource group that the Container Apps service automatically created and which contains the custom network components.
+If you're not going to continue to use this application, you can remove the **my-container-apps** resource group. This deletes the Azure Container Apps instance and all associated services.
 
 ::: zone pivot="azure-cli"
 

articles/expressroute/expressroute-howto-circuit-arm.md

@@ -445,7 +445,7 @@ Review the instructions in [Move ExpressRoute circuits from the classic to the R
 
 Note the following information:
 
-* All virtual networks must be unlinked from the ExpressRoute circuit. If this operation fails, check to see if any virtual networks are linked to the circuit.
+* All virtual networks, route filters, authorizations, and global reach associations must be unlinked from the ExpressRoute circuit. If this operation fails, check to see if any virtual networks are linked to the circuit.
 * If the ExpressRoute circuit service provider provisioning state is **Provisioning** or **Provisioned** you must work with your service provider to deprovision the circuit on their side. We continue to reserve resources and bill you until the service provider completes deprovisioning the circuit and notifies us.
 * If the service provider deprovisioned the circuit, meaning the service provider provisioning state gets set to **Not provisioned**, you can delete the circuit. The billing for the circuit stops.
 

articles/expressroute/expressroute-howto-circuit-portal-resource-manager.md

@@ -212,7 +212,7 @@ To modify an ExpressRoute circuit, select **Configuration**.
     :::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/expressroute-deprovisioned.png" alt-text="Screenshot of a deprovisioned circuit.":::
 
 > [!NOTE]
->* You must delete all associated [Virtual Network connections](expressroute-howto-linkvnet-portal-resource-manager.md#clean-up-resources), [Authorizations](expressroute-howto-linkvnet-portal-resource-manager.md#circuit-owner-operations), and [Global Reach](expressroute-howto-set-global-reach-portal.md#disable-connectivity) from the ExpressRoute circuit before deprovisioning. If deprovisioning fails, check whether any associated resources are still linked to the circuit.
+>* You must delete all associated [Virtual Network connections](expressroute-howto-linkvnet-portal-resource-manager.md#clean-up-resources), [Route Filter](how-to-routefilter-portal.md#clean-up-resources), [Authorizations](expressroute-howto-linkvnet-portal-resource-manager.md#circuit-owner-operations), and [Global Reach](expressroute-howto-set-global-reach-portal.md#disable-connectivity) from the ExpressRoute circuit before deprovisioning. If deprovisioning fails, check whether any associated resources are still linked to the circuit.
 >* If the circuit service provider has deprovisioned the circuit (The *Provider status* has updated to **Not provisioned**), you can delete the circuit. This stops billing for the circuit.
 
 ## Next steps

articles/expressroute/howto-circuit-cli.md

@@ -339,7 +339,7 @@ Review the instructions in [Move ExpressRoute circuits from the classic to the R
 
 To deprovision and delete an ExpressRoute circuit, make sure you understand the following criteria:
 
-* All virtual networks must be unlinked from the ExpressRoute circuit. If this operation fails, check to see if any virtual networks are linked to the circuit.
+* All virtual networks, route filters, authorizations, and global reach associations must be unlinked from the ExpressRoute circuit. If this operation fails, check to see if any virtual networks are linked to the circuit.
 * If the ExpressRoute circuit service provider provisioning state is **Provisioning** or **Provisioned** you must work with your service provider to deprovision the circuit on their side. We continue to reserve resources and bill you until the service provider completes deprovisioning the circuit and notifies us.
 * If the service provider has deprovisioned the circuit meaning the service provider provisioning state gets set to **Not provisioned**, you can delete the circuit. The billing for the circuit stop.