Create your first function in the Azure portal
Azure Functions lets you execute your code in a serverless environment without having to first create a VM or publish a web application. In this article, learn how to use Functions to create a "hello world" function in the Azure portal.
C# developers should consider creating your first function in Visual Studio 2019 instead of in the portal.
Log in to Azure
Sign in to the Azure portal at https://portal.azure.com with your Azure account.
Create a function app
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.
From the Azure portal menu, select Create a resource.
In the New page, select Compute > Function App.
Use the function app settings as specified in the table below the image.
Setting Suggested value Description Subscription Your subscription The subscription under which this new function app is created. Resource Group myResourceGroup Name for the new resource group in which to create your function app. Function App name Globally unique name Name that identifies your new function app. Valid characters are
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. Choose .NET for C# and F# functions. Region Preferred region Choose a region near you or near other services your functions access.
Select the Next : Hosting > button.
Enter the following settings for hosting.
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 may contain numbers and lowercase letters only. You can also use an existing account, which must meet the storage account requirements. Operating system Preferred operating system An operating system is pre-selected for you based on your runtime stack selection, but you can change the setting if necessary. Plan Consumption plan 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 only pay for the time your functions run. When you run in an App Service plan, you must manage the scaling of your function app.
Select the Next : Monitoring > button.
Enter the following settings for monitoring.
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, you can change the New resource name or choose a different Location in an Azure geography where you want to store your data.
Select Review + Create to review the app configuration selections.
Select Create to provision and deploy the function app.
Select the Notification icon in the upper-right corner of the portal and watch for the Deployment succeeded message.
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, you create a function in the new function app.
Create an HTTP triggered function
Expand your new function app, then select the + button next to Functions, choose In-portal, and select Continue.
Choose WebHook + API and then select Create.
A function is created using a language-specific template for an HTTP triggered function.
Now, you can run the new function by sending an HTTP request.
Test the function
In your new function, click </> Get function URL at the top right, select default (Function key), and then click Copy.
Paste the function URL into your browser's address bar. Add the query string value
&name=<yourname>to the end of this URL and press the
Enterkey on your keyboard to execute the request. You should see the response returned by the function displayed in the browser.
The following example shows the response in the browser:
The request URL includes a key that is required, by default, to access your function over HTTP.
When your function runs, trace information is written to the logs. To see the trace output from the previous execution, return to your function in the portal and click the arrow at the bottom of the screen to expand the Logs.
Clean up resources
Other quick starts in this collection build upon this quick start. If you plan to work with subsequent quick starts, tutorials, or with any of the services you have created in this quick start, do not clean up the resources.
Resources in Azure refers to function apps, functions, storage accounts, and so forth. They are grouped into resource groups, and you can delete everything in a group by deleting the group.
You created resources to complete these quickstarts. You may 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:
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 quickstart.
In the Resource group page, review the list of included resources, and verify that they are the ones you want to delete.
Select Delete resource group, and follow the instructions.
Deletion may 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.
You've created a function app with a simple HTTP triggered function.
Now that you have created your first function, let's add an output binding to the function that writes a message to a Storage queue.
For more information, see Azure Functions HTTP bindings.