This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 7.000000000000001%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPC%3C/text%3E%3C/svg%3E)
I would like to use VNET integration for my Web App. My Web App is talking to Azure SQL DB at the moment and i am going to use Private Link for Azure SQL. So for that it is essential to enable VNET integration for my web app as per the URL :
https://video2.skills-academy.com/en-us/azure/app-service/web-sites-integrate-with-vnet
I am currently on Standard S1 SKU. I would like to know will my SKU support VNET integration or i have to upgrade my Web App to premium?
In the link that i have pasted it says :
"The VNet Integration features:
Require a Standard, Premium, PremiumV2, PremiumV3, or Elastic Premium pricing plan.
Support TCP and UDP.
Work with Azure App Service apps and function apps."
So whatever SKU i am on, is it supported for VNET integration?
Also, when i try to scale up to Premium P2v2 i get the message that "Premium V2 is not supported for this scale unit".
Please suggest
Hello @Anonymous
Just checking to see Ryan's response helped answer your question. please don't forget to Accept an answer if the below reply is helpful.
Thanks,
Grace
Hi @Anonymous ,
VNet integration is supported on newer scale units. If you're getting "not supported" it is because your app service plan is on an older scale unit. To get around this, you can create a new Standard SKU app service plan in a different/new resource group and move (or clone) your app to the new plan.
@Ryan Hill You said that VNET integration is supported in newer scale units, so how will i know whether my scale unit is old or new? Is there anyway i can know from the portal or from the JSON view? Also, i was able to do VNET integration for my Web Apps hosted in Central US . My web apps are using S1 SKU and i was able to enable VNET integration using Terraform.
So does that mean my Web Apps were in a newer scale unit? I also tried upgrading my Web Apps in the Dev Subscription from S1 to P2v2. I was able to do it successfully in Dev, but i didn't get the option to upgrade to a higher SKU in QA and STG subscriptions. All these subscriptions are sitting in one region which is Central US.
So does that mean hardware wasn't available for the others to upgrade and it was available for only one Subscription?
Could you please let me know this.
Thanks
You should see a warning @Anonymous , with regards to scaling back down to a standard and VNET not being available on the scale unit. The sure-fire way is to scale you plan up to a Pv3 plan and scale back down as they are only on the newer scale units. The downside to that is that SKU is not available in all regions. If your target region doesn't have that SKU available, the next best option is creating a new Pv2 plan in a new resource group. The platform will use the new hardware, but this option isn't 100% guaranteed. You will need to scale it down to a standard plan and see if the VNET option is available.
Even though the resource group is metadata container for the resources inside the group, there is an affinity of the resource group that gets used to optimize deployed resources. That's why it's best to use a different resource group if you're trying to get on the newer hardware and it isn't working. Fresh out the gate, you should get the newer hardware.
Well i understand what you said, but the problem is i have resources running inside those app services and i have everything in one Resource Group. I have enabled VNET integration now also for the app services.
I have to now make these App Services talk to a SQL FO Group which i will be enabling to be used behind a Private Link. So if i have been able to successfully enable VNET integration with a Standard Plan, do you think it will be any issue going forward if i move this way forward without changing the app service SKUs to a PV2 plan?
No. If you already have VNET integration on the Standard plan, you're all set. It's only if you're on Standard plan that doesn't already have VNET integration in which you'll need to scale up/back down to get that feature.
Since you are connecting a SQL FOG through a private link, make sure you on your app service you enable Azure DNS Private Zones on your app service.
@Ryan Hill
I didn't have initially VNET integration in my Standard Plan. I enabled it yesterday and it seems to have gone fine. So right now i can see my Web Apps sitting inside that dedicated Subnet on my VNET . As far as your last statement "Enable Azure DNS Private Zones" did you mean applying these settings to my Web App :
"WEBSITE_DNS_SERVER" = "168.63.129.16"
"WEBSITE_VNET_ROUTE_ALL" = "1"
I have already applied these two settings to my Web App, becz i read that if my Web Apps need to talk to any resource that is sitting behind a Private Link, which in my case is SQL FO Group, i have to enable these two settings.
Is this correct what i have done or i am missing anything else.
That is correct. I just wanted to make sure you didn't omit that step 😊