C# Function Application with Azure Service Bus

This template includes everything you need to build, deploy, and monitor an Azure solution that both adds messages to and reacts to messages on an Azure Service Bus queue using Azure Function Apps and the native bindings for Service Bus. It includes application code, that serve as a foundation from which you can build upon and customize when creating your own solution.

Let's jump in and get the apps up and running in Azure. When you are finished, you will have a fully functional Service Bus queue with accompanying Function apps deployed on Azure.

Prerequisites

The following prerequisites are required to use this application. Please ensure that you have them all installed locally.

• Azure Developer CLI
  • Windows:

    powershell -c "Set-ExecutionPolicy Bypass Process -Force; irm 'https://aka.ms/install-azd.ps1' | iex"

  • Linux/MacOS:

    curl -fsSL https://aka.ms/install-azd.sh | bash 
    

• Azure CLI (2.37.0+)
• DotNet 6
• VSCode
• Functions Runtime
• Git (2.36.1+)

Architecture

graph TB
    subgraph Function Apps
    timer(Timer Trigger)
    sbTrigger
    
    end

    subgraph ServiceBus
    sb(Queue)
    timer-->|Every minute, write message|sb
    sb-->|On message add|sbTrigger(Queue Trigger)

    end

    subgraph Logging
    ai(App Insights)
    la(Log Analytics workspace)
    ai-->la   
    timer-->ai
        sbTrigger-->ai
    end

Loading

Quickstart

The fastest way for you to get this application up and running on Azure is to use the azd up command. This single command will create and configure all necessary Azure resources.

Run the following commands to initialize the project, provision Azure resources, and deploy the application code.

#download the repo assets from GitHub and initialize azd locally
azd init -t Gordonby/servicebus-dotnet-functionapp

#login to azure
azd auth login

#create the app in azure
azd up

You will be prompted for the following information:

• Environment Name: This will be used as a prefix for all your Azure resources, make sure it is globally unique and under 15 characters.
• Azure Subscription: The Azure Subscription where your resources will be deployed.
• Azure Location: The Azure location where your resources will be deployed