How to fix deployment timeout for Container Apps connected to VNet

Andrés Felipe Quintero 0 Reputation points

We've been trying to deploy Azure Container Apps connected to a VNet. So far we have not been successful. We have tried through the Web Portal and the Azure CLI with no success.

  • Microsoft.ContainerService and Microsoft.OperationalInsights are already registered for the subscription.
  • Error persists even after multiple deployment attempts with different configurations.
  • Error does not occur when no VNet is selected (either new or existing).
  • We have a VPN (Virtual Network Gateway) deployed with no BGP
  • This GitHub issue seems similar to the issue we have


  • Create a new Container App
    • Create a new Container App Environment
      • Under networking: Use your own virtual network (yes)
      • Use an existing or create a new virtual network (both failed for us with the same status)
  • Once deployment starts the status message under the provisioning of the container env states:
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The deployment operation status is unknown."

The deployment stays as running until it timesout after a couple of hours.

Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
222 questions
{count} votes

1 answer

Sort by: Most helpful
  1. MayankBargali-MSFT 66,671 Reputation points

    @Andrés Felipe Quintero Thanks for reaching out. Can you please confirm that the subnet does not delegate any service? Azure container apps subnet does require delegation.

    In case if you have verified the above then please share the correlationid for the failed deployment operation along with the timeframe in UTC so I can further verify it at my end.

    1 person found this answer helpful.