You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/overview-vnet-integration.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ If the virtual network is in a different subscription than the app, you must ens
76
76
77
77
### Routes
78
78
79
-
There are two types of routing to consider when you configure regional virtual network integration. [Application routing](#application-routing) defines what traffic is routed from your app and into the virtual network. [Configuration routing](#configuration-routing) affects operations that happen before or during startup of you app. Examples are container image pull and app settings with Key Vault reference. [Network routing](#network-routing) is the ability to control how both app and configuration traffic is routed from your virtual network and out.
79
+
There are three types of routing to consider when you configure regional virtual network integration. [Application routing](#application-routing) defines what traffic is routed from your app and into the virtual network. [Configuration routing](#configuration-routing) affects operations that happen before or during startup of you app. Examples are container image pull and app settings with Key Vault reference. [Network routing](#network-routing) is the ability to handle how both app and configuration traffic is routed from your virtual network and out.
80
80
81
81
#### Application routing
82
82
@@ -92,12 +92,12 @@ We recommend that you use the **Route All** configuration setting to enable rout
92
92
93
93
#### Configuration routing
94
94
95
-
When you are using virtual network integration, you can configure how parts of the configuration traffic is managed. By default, the mentioned configurations will go directly to the internet unless you actively configure it to be routed through the virtual network integration.
95
+
When you are using virtual network integration, you can configure how parts of the configuration traffic is managed. By default, configuration traffic will go directly over the public route, but individual components you actively configure it to be routed through the virtual network integration.
96
96
97
97
> [!NOTE]
98
98
> * Windows containers don't support routing App Service Key Vault references or pulling custom container images over virtual network integration.
99
99
> * Backup/restore to private storage accounts is currently not supported.
100
-
> *Get certificates from private Key Vaults is currently not supported.
100
+
> *Configure SSL/TLS certificates from private Key Vaults is currently not supported.
101
101
> * Diagnostics logs to private storage accounts is currently not supported.
102
102
103
103
##### Content storage
@@ -112,7 +112,7 @@ When using custom containers for Linux, you can pull the container over the virt
112
112
113
113
##### App settings using Key Vault references
114
114
115
-
App settings using Key Vault references will attempt to get the secrets over public internet. If the Key Vualt is blocking public traffic and the app is using virtual network integration, an attempt will then be made to get the secrets through the virtual network integration.
115
+
App settings using Key Vault references will attempt to get secrets over the public route. If the Key Vault is blocking public traffic and the app is using virtual network integration, an attempt will then be made to get the secrets through the virtual network integration.
0 commit comments