Skip to content

Commit 248dfb5

Browse files
committed
route all only private
1 parent 1c6c8f5 commit 248dfb5

File tree

3 files changed

+3
-4
lines changed

3 files changed

+3
-4
lines changed

articles/azure-functions/configure-networking-how-to.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,6 @@ To set up a function with a storage account restricted to a private network:
4444
| `WEBSITE_CONTENTSHARE` | File share | The name of the file share created in the secured storage account where the project deployment files reside. |
4545
| `WEBSITE_CONTENTOVERVNET` | 1 | New setting |
4646
| `WEBSITE_VNET_ROUTE_ALL` | 1 | Forces all outbound traffic through the virtual network. Required when the storage account is using private endpoint connections. |
47-
| `WEBSITE_DNS_SERVER` | `168.63.129.16` | The DNS server used by the app. Required when the storage account is using private endpoint connections. |
4847

4948
1. Select **Save** to save the application settings. Changing app settings causes the app to restart.
5049

articles/azure-functions/functions-create-vnet.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -320,8 +320,7 @@ To use your function app with virtual networks, you need to join it to a subnet.
320320
| **WEBSITE_CONTENTSHARE** | files | The name of the file share you created in the storage account. Use this setting with WEBSITE_CONTENTAZUREFILECONNECTIONSTRING. |
321321
| **SERVICEBUS_CONNECTION** | myServiceBusConnectionString | Create this app setting for the connection string of your Service Bus. This storage connection string is from the [Get a Service Bus connection string](#get-a-service-bus-connection-string) section.|
322322
| **WEBSITE_CONTENTOVERVNET** | 1 | Create this app setting. A value of 1 enables your function app to scale when your storage account is restricted to a virtual network. |
323-
| **WEBSITE_DNS_SERVER** | 168.63.129.16 | Create this app setting. When your app integrates with a virtual network, it will use the same DNS server as the virtual network. Your function app needs this setting so it can work with Azure DNS private zones. It's required when you use private endpoints. This setting and WEBSITE_VNET_ROUTE_ALL will send all outbound calls from your app into your virtual network. |
324-
| **WEBSITE_VNET_ROUTE_ALL** | 1 | Create this app setting. When your app integrates with a virtual network, it uses the same DNS server as the virtual network. Your function app needs this setting so it can work with Azure DNS private zones. It's required when you use private endpoints. This setting and WEBSITE_DNS_SERVER will send all outbound calls from your app into your virtual network. |
323+
| **WEBSITE_VNET_ROUTE_ALL** | 1 | Create this app setting. When your app integrates with a virtual network, it uses the same DNS server as the virtual network. Your function app needs this setting so it can work with Azure DNS private zones. It's required when you use private endpoints. |
325324

326325
1. In the **Configuration** view, select the **Function runtime settings** tab.
327326

articles/azure-functions/functions-networking-options.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,8 @@ To learn how to set up virtual network integration, see [Enable Vnet Integration
8787

8888
During the integration, your app is restarted. When integration is finished, you'll see details on the VNet you're integrated with.
8989

90+
When initially integrated with a VNet, all traffic will be routed into your VNet. If you wish for only your private traffic ([RFC1918](https://datatracker.ietf.org/doc/html/rfc1918#section-3) traffic) to be routed, please follow the steps in the [app service documentation](../app-service/web-sites-integrate-with-vnet#application-routing)
91+
9092
## Regional virtual network integration
9193

9294
Using regional VNet Integration enables your app to access:
@@ -169,7 +171,6 @@ Border Gateway Protocol (BGP) routes also affect your app traffic. If you have B
169171

170172
After your app integrates with your VNet, it uses the same DNS server that your VNet is configured with. By default, your app won't work with Azure DNS private zones. To work with Azure DNS private zones, you need to add the following app settings:
171173

172-
1. `WEBSITE_DNS_SERVER` with value `168.63.129.16`
173174
1. `WEBSITE_VNET_ROUTE_ALL` with value `1`
174175

175176
These settings send all of your outbound calls from your app into your VNet and enables your app to access an Azure DNS private zone. With these settings, your app can use Azure DNS by querying the DNS private zone at the worker level.

0 commit comments

Comments
 (0)