Create a function triggered by Azure Queue storage
Learn how to create a function that is triggered when messages are submitted to an Azure Storage queue.
- An Azure subscription. If you don't have one, create a free account before you begin.
Create an Azure Function app
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
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 Core for C# and F# functions. 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 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 (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, you create a function in the new function app.
Create a Queue triggered function
Select Functions, and then select + Add to add a new function.
Choose the Azure Queue Storage trigger template.
Use the settings as specified in the table below the image.
Setting Suggested value Description Name Unique in your function app Name of this queue triggered function. Queue name myqueue-items Name of the queue to connect to in your Storage account. Storage account connection AzureWebJobsStorage You can use the storage account connection already being used by your function app, or create a new one.
Select Create Function to create your function.
Next, you connect to your Azure storage account and create the myqueue-items storage queue.
Create the queue
In your function, on the Overview page, select your resource group.
Find and select your resource group's storage account.
Choose Queues, and then choose + Queue.
In the Name field, type
myqueue-items, and then select Create.
Now that you have a storage queue, you can test the function by adding a message to the queue.
Test the function
Back in the Azure portal, browse to your function expand the Logs at the bottom of the page and make sure that log streaming isn't paused.
In a separate browser window, go to your resource group in the Azure portal, and select the storage account.
Select Queues, and then select the myqueue-items container.
Select Add message, and type "Hello World!" in Message text. Select OK.
Wait for a few seconds, then go back to your function logs and verify that the new message has been read from the queue.
Back in your storage queue, select Refresh and verify that the message has been processed and is no longer in the queue.
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 quickstart.
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.
You have created a function that runs when a message is added to a storage queue. For more information about Queue storage triggers, see Azure Functions Storage queue bindings.
Now that you have a created your first function, let's add an output binding to the function that writes a message back to another queue.