Share via

Enabling 'Outbound internet traffic' feature is not taking effect in FunctionApp - VNet integration.

Mohammad Irfan Liaqat 25 Reputation points
2024-04-29T12:08:51.8533333+00:00

Hi,

We have a number of Web and Function Apps which are VNet Integrated. The subnets associated with each of these Web/Function Apps have Route Table and NSG configured. We have a central Azure Firewall which is configured to handle all outbound internet traffic. For this to work we have to enable an option called 'Outbound internet traffic' in VNet integration under Networking.
User's image

However, we have noticed that from 25th April this setting is set to false/unchecked. When we try to manually configure via Portal, although activity notification will say site config successful. The 'Outbound internet traffic' never get enabled.
User's image

Anyone else have faced this particular issue. We are running all apps on App Service Plan is S1.

We use Terraform to manage our infrastructure and from 25th Apr are seeing following change against all FunctionApps, where TF is trying to enable the feature.
User's image

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,366 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,196 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lem 2 Reputation points Microsoft Employee
    2024-05-02T21:19:49.41+00:00

    Hi Mohammad, Yes I've observed this behavior across multiple subscriptions lately. Users can check the application routing checkbox, but the change doesn't save; it reverts to unchecked after saving.

    While the routing feature itself functions properly, the portal UI doesn't reflect the change accurately, leading to confusion among users.

    I've seen comments that using a new subnet or manually adding the appsetting WEBSITE_VNET_ROUTE_ALL=1, may help mitigate the issue.

    0 comments