App Service Regional VNet Integration

Question

Hi,

I am having trouble connecting an App Service to a VNet in the same region. I might not be understanding this correctly, but this article appears to say that you only need a Gateway if you're connecting to a VNet in a different region. Otherwise all you need is a dedicated Subnet for this to work: https://learn.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet

My App Service is running in East US and I have a VNet in East US as well, however when I pick the VNet to Add under VNet Integration, I get a message "This virtual network has no gateway".

When I pick a VNet that does have a Gateway, the message goes away and I seem to be able to connect to that VNet. What gives?

Thanks.

Answer 1

After much research, I came across these articles. "This virtual network has no gateway" was simply a random error the portal was showing, while in reality the issues is that not all hardware currently supports Regional VNet Integration. Even though the documentation above claims this feature is supported on Standard tier, it's a hit or miss depending on what scale unit you're provisioned on. The only reliable way to get this accomplished is by provisioning a PremiumV2 tier. I wish the documentation stated that clearly. Lots of time spent troubleshooting this. Here are the links that could help others:

https://github.com/MicrosoftDocs/azure-docs/issues/56945

https://github.com/MicrosoftDocs/azure-docs/issues/20348

EDIT: The correct error message is only available by using ARM templates. The portal doesn't show this error message. There are other nuances with the ARM templates as well that documentation does not cover. Look at either of those threads to know the correct "name" and "type" fields for the ARM template to use.

Answer 2

Thanks for the feedback! Yes, you are correct in case of Standard App Service Plan Regional VNet Integration is not working and when trying to add the VNet Integration to the App Service it shows “ The Virtual Network has no Gateway.” But incase of Premium V2 App service plan it works as expected.

We are internally working with content team on updating the UI and docs and will keep you posted here when we have more updates.

But in short, the old stamps don’t support the feature from Standard ASPs. Only from Premiumv2 support.

We apologize for the inconvenience that this issue caused. If you have further questions on this, please send an email to AzCommunity[at]Microsoft[dot]com

Answer 3

@PB Thanks a lot for sharing it was very helpful!!!

Answer 4

But if my App service is with older scale units and i have created a new app service plan in Premium V2, will it work.

As I am getting same error to create the gateway, kindly let me know.

Answer 5

Hi ,

I was trying to add VNET in the basic tier

I was referring the below article it says basic tier support vnet but when I try to add it throws error "This virtual network has no gateway"