In this video I want us to take a look at the actual configurations for implementing the VNET integration inside of an Azure App Service.

To do that, let's go ahead and jump into the portal and see how you would do it in there, and then you can take that and leverage it inside of a script or continue to do it in the portal.

Here we are at the overview page for my App Service. It is a standard App Service that is running within a standard tier, as you can see right here through the App Service plan tab.

As we talked about, this is one of the requirements for even allowing VNet integration to be possible.

In order to actually configure VNet integration, you're going to go through the networking tab or networking navigation bar item and just go ahead and click on it.

You're going to have a number of different options here that will allow you to, set up access restrictions, assign addresses, maybe connect a CDN, but the key point is VNet integration.

As you can see right now it's currently set to off. 

We click on that.

We bring up the page to show us that right now no VNets have been currently integrated. 

I have two Vnets in my subscription. One in this region where this App Service lives, which is South Central, and then I have one that sits inside of North Central.

The process for configuring your App Service is going to be the same no matter whether it's regional or global. The difference is on the VNet side, and we'll take a look at the VNet configuration options in the next video.

All we're going to do here is click on the add VNet button. 

It's going to give us an option to choose our subscription.

Then we’re going to choose the virtual network.

Here is the one that's currently sitting in the same region, South Central, and then we're going to specify do we want to go ahead and create a new subnet that's going to be dedicated for this App Service or do we want to use one that's existing?

I already have an empty one and it's called Subnet App Services, so we're going to choose that one.

Click OK and now all we have to do is wait for the configuration to finish and there it is.

We've got it up and running and now the VNet integration has been enabled, which you can see right here.

We can also see the address space which should correspond to the address space of the subnet that we chose and can validate that we are in fact connected to VNet integrations.

It's that simple. You can do this via the Azure CLI. You can also do it via Azure PowerShell, but it is usually a one-time action, so I can't imagine that you're going to need to do this all that often.

In the next video, we'll take a look at how to configure the actual virtual network so that it can receive an App Service integration.