Skip to content

Commit ea02d4f

Browse files
committed
Routing app settings
1 parent 5a91110 commit ea02d4f

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

articles/app-service/overview-vnet-integration.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Integrate your app with an Azure virtual network
33
description: Integrate your app in Azure App Service with Azure virtual networks.
44
author: madsd
55
ms.topic: conceptual
6-
ms.date: 07/21/2023
6+
ms.date: 02/06/2024
77
ms.author: madsd
88
ms.custom: UpdateFrequency3
99

@@ -147,6 +147,14 @@ App settings using Key Vault references attempt to get secrets over the public r
147147
> * Configure SSL/TLS certificates from private Key Vaults is currently not supported.
148148
> * App Service Logs to private storage accounts is currently not supported. We recommend using Diagnostics Logging and allowing Trusted Services for the storage account.
149149
150+
## Routing app settings
151+
152+
App Service has existing app settings to configure application and configuration routing. Site properties override the app settings if both exist. Site properties have the advantage of being auditable with Azure Policy and validated at the time of configuration. We recommend you to use site properties.
153+
154+
You can still use the existing `WEBSITE_VNET_ROUTE_ALL` app setting to configure application routing.
155+
156+
App settings also exist for some configuration routing options. These app settings are named `WEBSITE_CONTENTOVERVNET` and `WEBSITE_PULL_IMAGE_OVER_VNET`.
157+
150158
### Network routing
151159

152160
You can use route tables to route outbound traffic from your app without restriction. Common destinations can include firewall devices or gateways. You can also use a [network security group](../virtual-network/network-security-groups-overview.md) (NSG) to block outbound traffic to resources in your virtual network or the internet. An NSG that's applied to your integration subnet is in effect regardless of any route tables applied to your integration subnet.

0 commit comments

Comments
 (0)