Consuming Azure Service Bus Message Queue in Azure Function Application

In this tutorial, I will be consuming Azure Service Bus Message Queue in Azure Function Application using Visual Studio 2019 Project Template. Essentially we are trying to demonstrate the output created by Azure DevOps Web Hook event.

Introduction

What is Azure Service Bus?

According to Microsoft Documentation, Microsoft Azure Service Bus is a fully managed enterprise integration message broker. Service Bus can decouple applications and services. Service Bus offers a reliable and secure platform for asynchronous transfer of data and state.

Data is transferred between different applications and services using messages. A message is in binary format and can contain JSON, XML, or just text.

What is Azure Function?

According to Microsoft Documentation, Azure Functions allows you to run small pieces of code (called "functions") without worrying about application infrastructure. With Azure Functions, the cloud infrastructure provides all the up-to-date servers you need to keep your application running at scale.

A function is "triggered" by a specific type of event. Supported triggers include responding to changes in data, responding to messages, running on a schedule, or as the result of an HTTP request.

Prerequisites

• Microsoft Azure Subscription (You can subscribe for free, if you don't have one)
• Visual Studio 2019 Community (You can download it for free, if you don't have it installed)

Lets Get Started

Go ahead and create a new project in Visual Studio 2019 and Select Azure Function project template.

• Select "Service Bus Queue trigger"
• Select storage account (Login prompt may appear if not yet logged to Azure Services using Visual Studio)
• Fill-up Connection String Name and Queue Name

There are no customization yet to implement a business rule or any logical instruction. here I printed the myQueueItem parameter to see the value of Json received from the Service Bus Queue.

One thing that I'd like to note is the connection string trigger parameter which you need to add manually on local.settings.json while your are debugging in visual studio. You can get Connection string value in Azure Portal Namespace Shared Access policies.

Demo