Create your first function in the Azure portal

Azure Functions lets you run your code in a serverless environment without having to first create a virtual machine (VM) or publish a web application. In this article, you learn how to use Azure Functions to create a "hello world" HTTP trigger function in the Azure portal.

Choose your preferred programming language at the top of the article.

Please review the known issues for development of Azure Functions using Python in the Azure portal.

If you don't have an Azure subscription, create a trial account before you begin.

Sign in to the Azure portal with your Azure account.

You must have a function app to host the execution of your functions. A function app lets you group functions as a logical unit for easier management, deployment, scaling, and sharing of resources.

Use these steps to create your function app and related Azure resources, whether or not you're able to edit your code in the Azure portal.

1. From the Azure portal menu or the Home page, select Create a resource.

2. In the New page, select Compute > Function App.

3. On the Basics page, use the function app settings as specified in the following table:

   Expand table

   Setting	Suggested value	Description
   Subscription	Your subscription	The subscription under which you'll create your new function app.
   Resource Group	myResourceGroup	Name for the new resource group in which you'll create your function app. You should create a new resource group because there are known limitations when creating new function apps in an existing resource group.
   Function App name	Globally unique name	Name that identifies your new function app. Valid characters are a-z (case insensitive), 0-9, and -.
   Publish	Code	Option to publish code files or a Docker container.
   Runtime stack	Preferred language	Choose a runtime that supports your favorite function programming language. In-portal editing is only available for JavaScript, PowerShell, TypeScript, and C# script. C# class library, Java, and Python functions must be developed locally.
   Version	Version number	Choose the version of your installed runtime.
   Region	Preferred region	Select a region that's near you or near other services that your functions can access.

4. Select Next : Hosting. On the Hosting page, enter the following settings:

   Expand table

   Setting	Suggested value	Description
   Storage account	Globally unique name	Create a storage account used by your function app. Storage account names must be between 3 and 24 characters in length and can contain numbers and lowercase letters only. You can also use an existing account, which must meet the storage account requirements.
   Operating system	Windows	An operating system is pre-selected for you based on your runtime stack selection, but you can change the setting if necessary. In-portal editing is only supported on Windows.
   Plan	Consumption (Serverless)	Hosting plan that defines how resources are allocated to your function app. In the default Consumption plan, resources are added dynamically as required by your functions. In this serverless hosting, you pay only for the time your functions run. When you run in an App Service plan, you must manage the scaling of your function app.

5. Select Next : Monitoring. On the Monitoring page, enter the following settings:

   Expand table

   Setting	Suggested value	Description
   Application Insights	Default	Creates an Application Insights resource of the same App name in the nearest supported region. By expanding this setting or selecting Create new, you can change the Application Insights name or select a different region in an Azure geography where you want to store your data.

6. Select Review + create to review the app configuration selections.

7. On the Review + create page, review your settings, and then select Create to provision and deploy the function app.

8. Select the Notifications icon in the upper-right corner of the portal and watch for the Deployment succeeded message.

9. Select Go to resource to view your new function app. You can also select Pin to dashboard. Pinning makes it easier to return to this function app resource from your dashboard.

   

Next, create a function in the new function app.

1. On the Overview page for your new function app, select your new HTTP triggered function in the Functions tab.

2. In the left menu, expand Developer, select Code + Test, and then select Test/Run.

3. In the Test/Run dialog, select Run.

   An HTTP POST request is sent to your new function with a payload that contains the name value of Azure. You can also test the function by selecting GET for HTTP method and adding a name parameter with a value of YOUR_NAME.

   Tip

   To test in an external browser, instead select Get function URL, copy the default (Function key) value, add the query string value &name=<YOUR_NAME> to the end of this URL, and then submit the URL in the address bar of your web browser.

4. When your function runs, trace information is written to the logs. To see the trace output, return to the Code + Test page in the portal and expand the Logs arrow at the bottom of the page. Call your function again to see the trace output written to the logs.

Other quickstarts in this collection build upon this quickstart. If you plan to work with subsequent quickstarts, tutorials, or with any of the services you've created in this quickstart, don't clean up the resources.

Resources in Azure refer to function apps, functions, storage accounts, and so forth. They're grouped into resource groups, and you can delete everything in a group by deleting the group.

You've created resources to complete these quickstarts. You might be billed for these resources, depending on your account status and service pricing. If you don't need the resources anymore, here's how to delete them:

1. In the Azure portal, go to the Resource group page.

   To get to that page from the function app page, select the Overview tab, and then select the link under Resource group.

   

   To get to that page from the dashboard, select Resource groups, and then select the resource group that you used for this article.

2. In the Resource group page, review the list of included resources, and verify that they're the ones you want to delete.

3. Select Delete resource group and follow the instructions.

   Deletion might take a couple of minutes. When it's done, a notification appears for a few seconds. You can also select the bell icon at the top of the page to view the notification.

Now that you've created your first function, let's add an output binding to the function that writes a message to a Storage queue.