Hi Linru_Hui , thanks for the guide. I have a couple of questions after trying this with Linux based Function app P1v2 (which failed):
Can you confirm that "custom DNS for Linux plans aren't supported" means that WEBSITE_DNS_SERVER must use 168.63.129.16?
Is WEBSITE_VNET_ROUTE_ALL still required after the latest vnet integration updates?
This process differs from the documented guide https://docs.microsoft.com/en-us/azure/azure-functions/configure-networking-how-to#restrict-your-storage-account-to-a-virtual-network, when I follow that guide it works but it is not something that will be easy to automate
.
As I said my own portal deployment following these steps failed. Function runtime not accessible/service unavailable when trying to access the scm. Any possibility of providing an example ARM/Bicep/Terraform template?
Thanks
Darrell