Question 104628 in Azure Question posted in
The official documentation to get you started can be found here.

Why Azure app service VNET integration failing with new subnet?

I’m trying to connect my app service plan in to VNET. But always failed. I have red threads and everywhere saying App service plan should be Standard or higher.

  1. My App service Plan is S1.
  2. It’s just an empty app.
  3. I’m creating new subnet (not select existing one) when configuring VNET.
  4. I have run the trouble-shooter and no issue found with connectivity

Can someone help on this?

enter image description here
enter image description here

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    Issue was my VNET and App service in different subscription . But in same region. move app service in to other subscription which contains VNET. Problem solved.

    Seems to be VNET integration not working between Resorces in multipole subscriptions .Cheers


  2. 0

    There are some limitations with using regional virtual network integration:

    Refer MsDoc

    1. If you have already one VNet associated with an app service plan, it would be better if you create a new app service plan and then configure the VNet. I found the same fix here by @Asish Punnose.
    2. "App service plan, VNet as well as App" should be in the same region.
    3. The integration subnet can only use one App Service plan

    After considering all the above limitations, I was able to configure VNet successfully.

    By adding a new subnet, enabling inbound & outbound traffic addresses with a new virtual network as well as new app service plan I could create an app with standard s1 plan.

    enter image description here

    Added subnets under VNet integration:

    enter image description here

    Configured VNet with an app service plan without any error:

    enter image description here

    enter image description here

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search