为什么要为应用程序服务的VNET集成提供额外的子网 [英] why Extra subnet for VNET integration for app services
问题描述
为什么我们必须创建一个新子网或将应用程序服务添加到vnet中的空子网中?我不明白原因，因为我试图使用我的应用程序服务(功能应用程序)作为反向代理来访问vnet中的资源.
默认情况下，Azure功能是
有关更多信息，您可以阅读 解决方案
By default, the Azure function is a PaaS as the other Azure Platform-as-a-Services that have inbound and outbound traffic over the Internet. We can host our applications without the need to worry about the maintenance of the servers and their operating systems.
To use Azure Functions to connect to resources in an Azure virtual network, we can use the VNet integration feature. To use this feature, we need to create a subnet in the virtual network for your function app to use. VNet Integration must be configured to use an empty subnet. It doesn't matter that your functions use a different subnet than your VM. The virtual network automatically routes traffic between the two subnets. Read Connect your function app to the virtual network
The extra empty subnet is used to hosting your app instance. To let the app instance outbound traffic work like from a VNet, Azure mounts NICs with assigned private IP addresses in that subnet. With VNet integration, your function app is connected to both the internet and your virtual network.
For more information, you may read How regional VNet Integration works and How gateway-required VNet Integration works
这篇关于为什么要为应用程序服务的VNET集成提供额外的子网的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
