Create your first function in the Azure portal

Članak
02/09/2022
7 min. za čitanje

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.

Note

In-portal editing is only supported for JavaScript, PowerShell, TypeScript, and C# Script functions.

For C# class library, Java, and Python functions, you can create the function app in the portal, but you must also create the functions locally and then publish them to Azure.

We instead recommend that you develop your functions locally and publish to a function app in Azure.
Use one of the following links to get started with your chosen local development environment and language:

Visual Studio Code	Terminal/command prompt	Visual Studio
• Get started with C# • Get started with Java • Get started with JavaScript • Get started with PowerShell • Get started with Python	• Get started with C# • Get started with Java • Get started with JavaScript • Get started with PowerShell • Get started with Python	Get started with C#

Language support details

The following table shows which languages supported by Functions can run on Linux or Windows. It also indicates whether your language supports editing in the Azure portal. The language is based on the Runtime stack option you choose when creating your function app in the Azure portal. This is the same as the --worker-runtime option when using the func init command in Azure Functions Core Tools.

Language	Runtime stack	Linux	Windows	In-portal editing¹
C# class library²	.NET	✓	✓
C# script	.NET	✓	✓	✓
JavaScript	Node.js	✓	✓	✓
Python	Python	✓
Java	Java	✓	✓
PowerShell	PowerShell Core	✓	✓	✓
TypeScript	Node.js	✓	✓
Go/Rust/other	Custom Handlers	✓	✓

¹ When running on Linux, in-portal editing is only supported in a Dedicated (App Service) plan.
² In the portal, you can't currently create function apps that run on .NET 5.0. To learn more, see Develop and publish .NET 5 functions using Azure Functions.

For more details, see Operating system/runtime support.

When in-portal editing isn't available, you must instead develop your functions locally.

Prerequisites

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

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 or the Home page, select Create a resource.
In the New page, select Compute > Function App.

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

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 `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	Choose a region near you or near other services your functions access.

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

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.

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

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 choose a different region in an Azure geography where you want to store your data.

Select Review + create to review the app configuration selections.
On the Review + create page, review your settings, and then select Create to provision and deploy the function app.
Select the Notifications 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, create a function in the new function app.

Create an HTTP trigger function

From the left menu of the Function App window, select Functions, then select Create from the top menu.
From the Create Function window, leave the Development environment property has Develop in portal and select the HTTP trigger template.
Under Template details use HttpExample for New Function, choose Anonymous from the Authorization level drop-down list, and then select Create.

Azure creates the HTTP trigger function. Now, you can run the new function by sending an HTTP request.

Test the function

In your new HTTP trigger function, select Code + Test from the left menu, then select Get function URL from the top menu.
In the Get function URL dialog box, select default from the drop-down list, and then select the Copy to clipboard icon.
Paste the function URL into your browser's address bar. Add the query string value ?name=<your_name> to the end of this URL and press Enter to run the request. The browser should display a response message that echoes back your query string value.

If the request URL included an access key (?code=...), it means you choose Function instead of Anonymous access level when creating the function. In this case, you should instead append &name=<your_name>.
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 trace output written to the logs.

Clean up resources

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 have created in this quickstart, do not 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 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 article.
In the Resource group page, review the list of included resources, and verify that they're 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.

Next steps

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.

Add messages to an Azure Storage queue using Functions