Skip to content

Commit

Permalink
Merge pull request MicrosoftDocs#73335 from ShawnJackson/functions-cr…
Browse files Browse the repository at this point in the history 
…eate-vnet

edit pass: functions-create-vnet
  • Loading branch information
@Ja-Dunn
Ja-Dunn authored Apr 18, 2019
2 parents 2327e53 + aac5d6d commit 91ad99b
Show file tree
Hide file tree
Showing 2 changed files with 61 additions and 58 deletions.
107 changes: 55 additions & 52 deletions articles/azure-functions/functions-create-vnet.md
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Integrate Azure Functions with an Azure Virtual Network
description: A step by step tutorial showing you how to connect a Function to an Azure virtual network
title: Integrate Azure Functions with an Azure virtual network
description: A step-by-step tutorial that shows you how to connect a function to an Azure virtual network
services: functions
author: alexkarcher-msft
manager: jehollan
Expand All @@ -12,108 +12,111 @@ ms.author: alkarche
---
# Integrate a function app with an Azure virtual network

This tutorial shows you how to use Azure Functions to connect to resources in an Azure VNET.
This tutorial shows you how to use Azure Functions to connect to resources in an Azure virtual network.

For this tutorial we will be deploying a WordPress site on a VM in a private, non-internet accessible, VNET. We will then deploy a Function with access to both the internet and the VNET. We will use that Function to access resources from the WordPress site deployed inside the VNET.
For this tutorial, we'll deploy a WordPress site on a VM in a virtual network that's not accessible from the internet. We'll then deploy a function with access to both the internet and the virtual network. We'll use that function to access resources from the WordPress site deployed inside the virtual network.

For more information on how the system works, troubleshooting, and advanced configuration, see the document [Integrate your app with an Azure Virtual Network](https://docs.microsoft.com/azure/app-service/web-sites-integrate-with-vnet). Azure Functions in the Premium plan have the same hosting capabilities as web apps, so all the functionality and limitations in that document apply to Functions as well.
For more information on how the system works, troubleshooting, and advanced configuration, see [Integrate your app with an Azure virtual network](https://docs.microsoft.com/azure/app-service/web-sites-integrate-with-vnet). Azure functions in the Premium plan have the same hosting capabilities as web apps, so all the functionality and limitations in that article apply to functions.

## Topology

![VNet Integration UI][1]
![UI for virtual network integration][1]

## Creating a VM inside of a VNET
## Create a VM inside a virtual network

To start off, we will create a pre-configured VM running Wordpress inside of a VNET.
To start, we'll create a preconfigured VM that runs WordPress inside a virtual network.

Wordpress on a VM was chosen because it is one of the least expensive resources that can be deployed inside of a VNET. Note that this scenario can also work with any resource in a VNET, such as REST APIs, App Service environments, and other Azure services.
We chose WordPress on a VM because it's one of the least expensive resources that can be deployed inside a virtual network. Note that this scenario can also work with any resource in a virtual network, such as REST APIs, App Service Environments, and other Azure services.

1. Go to the Azure portal
2. Add a new resource by opening the “Create a resource” blade
3. Search for “[WordPress LEMP7 Max Performance on CentOS](https://jetware.io/appliances/jetware/wordpress4_lemp7-170526/profile?us=azure)” and open its creation blade
4. In the creation blade configure the VM with the following information:
1. Create a new resource group for this VM to make cleaning up the resources easier at the end of the tutorial. I named my Resource Group “Function-VNET-Tutorial”
1. Give the virtual machine a unique name. I named mine “VNET-Wordpress”
1. Select the region closest to you
1. Select the size as B1s (1 vcpu, 1 GB memory)
1. For the administrator account, choose password authentication and enter a unique username and password. For this tutorial, you will not need to sign in to the VM unless you need to troubleshoot.
1. Go to the Azure portal.
2. Add a new resource by opening the **Create a resource** blade.
3. Search for “[WordPress LEMP7 Max Performance on CentOS](https://jetware.io/appliances/jetware/wordpress4_lemp7-170526/profile?us=azure)” and open its creation blade.
4. On the **Basics** tab, configure the VM with the following information:
1. Create a new resource group for this VM to make cleaning up the resources easier at the end of the tutorial. Here, we're using “Function-VNET-Tutorial” as an example.
1. Give the virtual machine a unique name. We're using “VNET-Wordpress” as an example.
1. Select the region closest to you.
1. Select the size as B1s (1 vCPU, 1 GB of memory).
1. For the administrator account, choose password authentication and enter a unique username and password. For this tutorial, you won't need to sign in to the VM unless you need to troubleshoot.

![Create VM Basics tab](./media/functions-create-vnet/create-vm-1.png)
![Basics tab for creating a VM](./media/functions-create-vnet/create-vm-1.png)

1. Move to the networking tab and enter the following information:
1. Create a new virtual network
1. Enter in your desired private address range and subnet within that address range. The subnet size will determine how many VMs you can use in the App Service plan. If IP addressing and subnetting are new to you, there is a [document covering the basics](https://support.microsoft.com/en-us/help/164015/understanding-tcp-ip-addressing-and-subnetting-basics). IP addressing and subnetting are important in this scenario, so I'd recommend reading a few articles and watching a few videos online until it makes sense.
1. For this example, I opted to use the 10.10.0.0/16 network with a subnet of 10.10.1.0/24. I chose to overprovision and use a /16 subnet because it is easy to calculate which subnets are available in the 10.10.0.0/16 network.
1. Move to the **Networking** tab and enter the following information:
1. Create a new virtual network.
1. Enter a private address range and a subnet within that address range. The subnet size will determine how many VMs you can use in the App Service plan. If IP addressing and subnetting are new to you, there's a [document that covers the basics](https://support.microsoft.com/en-us/help/164015/understanding-tcp-ip-addressing-and-subnetting-basics). IP addressing and subnetting are important in this scenario, so we recommend that you read a few articles and watch a few videos online until it makes sense.

For this example, we're opting to use the 10.10.0.0/16 network with a subnet of 10.10.1.0/24. We're overprovisioning and using a /16 subnet because it's easy to calculate which subnets are available in the 10.10.0.0/16 network.

<img src="./media/functions-create-vnet/create-vm-2.png" width="700">

1. Back in the Networking tab, set the Public IP to "None." This will deploy the VM with access to only the VNET.
1. Back on the **Networking** tab, set the public IP to **None**. This step will deploy the VM with access to only the virtual network.

<img src="./media/functions-create-vnet/create-vm-2-1.png" width="700">

7. Create the VM. This will take approximately 5 minutes.
8. Once the VM is created, visit its networking tab and note the Private IP address for later. The VM should not have a public IP.
7. Create the VM. The process will take about 5 minutes.
8. After the VM is created, go to its **Networking** tab and note the private IP address for later. The VM should not have a public IP.

![14]

You will now have a wordpress site deployed entirely within your virtual network. This site is not accessible from the public internet.
You now have a WordPress site deployed entirely within your virtual network. This site is not accessible from the public internet.

## Create a Premium plan Function App
## Create a function app in a Premium plan

The next step is to create a function app in a premium plan. The premium plan is a new offering that brings serverless scale with all of the benefits of a dedicated App Service Plan. Consumption plan function apps do not support VNet integration.
The next step is to create a function app in a Premium plan. A Premium plan brings serverless scale with all the benefits of a dedicated App Service plan. Function apps created through the Consumption plan don't support virtual network integration.

[!INCLUDE [functions-premium-create](../../includes/functions-premium-create.md)]

## Connect your Function App to your VNET
## Connect your function app to your virtual network

With a WordPress site hosing files from within your VNET, you can now connect the function app to the VNET.
With a WordPress site hosting files from within your virtual network, you can now connect the function app to the virtual network.

1. In the portal for the Function App from the previous step select **Platform features**, then select **Networking**
1. In the portal for the function app from the previous step, select **Platform features**. Then select **Networking**.

<img src="./media/functions-create-vnet/networking-0.png" width="850">

1. Select **Click to configure** under VNet Integration
1. Select **Click here to configure** under **VNet Integration**.

![Configure network feature status](./media/functions-create-vnet/Networking-1.png)
![Status for configuring a network feature](./media/functions-create-vnet/Networking-1.png)

1. In the VNET integration page, select **Add VNet (preview)**
1. On the virtual network integration page, select **Add VNet (preview)**.

<img src="./media/functions-create-vnet/networking-2.png" width="600">

1. Create a new subnet for your Function and App Service plan to use. Note that the subnet size will restrict the total number of VMs you can add to your app service plan. Your VNET will automatically route traffic between the subnets in your VNET, so it does not matter that your Function is in a different subnet from your VM.
1. Create a new subnet for your function and App Service plan to use. Note that the subnet size will restrict the total number of VMs that you can add to your App Service plan. Your virtual network will automatically route traffic between the subnets in your virtual network, so it doesn't matter that your function is in a different subnet from your VM.

<img src="./media/functions-create-vnet/networking-3.png" width="600">

## Create a Function that accesses a resource in your VNET
## Create a function that accesses a resource in your virtual network

The function app can now access the virtual network with our WordPress site. So we're going to use the function to access that file and serve it back to the user. For this example, we'll use a WordPress site as the API and a proxy as the calling function because they're both easy to set up and visualize.

The Function App can now access the VNET with our wordpress site, so we're going to use the function to access that file and serve it back to the user. For this example we'll use a wordpress site as the API, and a Function Proxy as the calling Functions because they are both easy to set up and visualize. You could just as easily use any other API deployed within a VNET, and another Function with code making API calls to that API deployed within your VNET. A SQL server deployed within your VNET is a perfect example.
You can just as easily use any other API deployed within a virtual network. You can also use another function with code that makes API calls to the API deployed within your virtual network. A SQL Server instance deployed within your virtual network is a perfect example.

1. In the portal, open the Function App from the previous step
1. Create a Proxy by selecting **Proxies** > **+**
1. In the portal, open the function app from the previous step.
1. Create a proxy by selecting **Proxies** > **+**.

<img src="./media/functions-create-vnet/new-proxy.png" width="250">

1. Configure the Proxy name and route. I chose /plant as my route.
1. Fill in your wordpress site's IP from earlier and set the Backend URL to `http://{YOUR VM IP}/wp-content/themes/twentyseventeen/assets/images/header.jpg`
1. Configure the proxy name and route. This example uses "/plant" as a route.
1. Fill in your WordPress site's IP from earlier and set **Backend URL** to `http://{YOUR VM IP}/wp-content/themes/twentyseventeen/assets/images/header.jpg`

<img src="./media/functions-create-vnet/create-proxy.png" width="900">

Now, if you attempt to visit your backend URL directly by pasting it into a new browser tab, the page should time out. This is to be expected, as your wordpress site is connected to only your VNET and not the internet. If you paste your Proxy URL into the browser you should see a beautiful plant picture, pulled from your Wordpress site inside your VNET.
Now, if you try to visit your back-end URL directly by pasting it into a new browser tab, the page should time out. This is because your WordPress site is connected to only your virtual network and not the internet. If you paste your proxy URL into the browser, you should see a plant picture (pulled from your WordPress site) inside your virtual network.

Your Function App is connected to both the Internet and your VNET. The proxy is receiving a request over the public internet, and then acting as a simple HTTP proxy to forward that request along into the virtual network. The proxy then relays the response back to you over the public internet.
Your function app is connected to both the internet and your virtual network. The proxy is receiving a request over the public internet, and then acting as a simple HTTP proxy to forward that request along into the virtual network. The proxy then relays the response back to you over the public internet.

<img src="./media/functions-create-vnet/plant.png" width="900">

## Next Steps
## Next steps

Functions running in a Premium plan share the same underlying App Service infrastructure as Web Apps on PV2 plans. This means that all of the documentation for Web Apps applies to your Premium plan functions.
Functions running in a Premium plan share the same underlying App Service infrastructure as web apps on PremiumV2 plans. All the documentation for web apps applies to your Premium plan functions.

1. [Learn more about the networking options in functions here](./functions-networking-options.md)
1. [Read the Functions networking FAQ here](./functions-networking-faq.md)
1. [Learn more about VNETs in Azure](../virtual-network/virtual-networks-overview.md)
1. [Enable more networking features and control with App Service Environments](../app-service/environment/intro.md)
1. [Connect to individual on-premises resources without firewall changes using Hybrid Connections](../app-service/app-service-hybrid-connections.md)
1. [Learn more about Function Proxies](./functions-proxies.md)
* [Learn more about the networking options in Functions](./functions-networking-options.md)
* [Read the Functions networking FAQ](./functions-networking-faq.md)
* [Learn more about virtual networks in Azure](../virtual-network/virtual-networks-overview.md)
* [Enable more networking features and control with App Service Environments](../app-service/environment/intro.md)
* [Connect to individual on-premises resources without firewall changes by using Hybrid Connections](../app-service/app-service-hybrid-connections.md)
* [Learn more about Functions Proxies](./functions-proxies.md)

<!--Image references-->
[1]: ./media/functions-create-vnet/topology.png
Expand Down
12 changes: 6 additions & 6 deletions includes/functions-premium-create.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,19 +11,19 @@ ms.custom: include file
---


1. Go to the Azure portal
2. Add a new resource by clicking the **Create a resource** button in the Azure portal
3. Select **Serverless Function App**
4. Enter all of your information into the creation settings and set your **Hosting plan** to **App Service Plan**:
1. Go to the Azure portal.
2. Add a new resource by selecting the **Create a resource** button in the Azure portal.
3. Select **Serverless Function App**.
4. Enter all of your information into the creation settings and set your **Hosting Plan** to **App Service Plan**:

![Create function app plan](./media/functions-premium-create/create-function-app-plan.png)

1. Select a Premium Plan (EP) Service Plan level.
1. Select a Premium plan (EP) level for the service plan.
![Select premium plan](./media/functions-premium-create/hosting-plan.png)

1. Validate your completed plan settings.
![Finished app service plan](./media/functions-premium-create/create-app-service-plan.png)

1. Validate your app and plan settings and click **Create**
1. Validate your app and plan settings, and select **Create**.

![Finished app service plan](./media/functions-premium-create/create-function-app.png)

0 comments on commit 91ad99b

Please sign in to comment.