This is example of producing and receiving messages in ServiceBus using Azure Functions.

Architecture consist of:

• ServiceBus
• Azure Function to produce messages and write them to ServiceBus queue
• Azure Function to receive messages from ServiceBus queue
• CosmosDB to store received messages

To deploy required Azure Resources, go to bicep directory and execute following Azure CLI command:

az deployment group create \
    --resource-group {{resourceGroupName}} \
    --name {{deploymentName}} \
    --template-file main.bicep

Configure provisioned Azure Functions:

1. Add ServiceBus connection string to Azure Portal > function-app-1 > Configuration > Application settings > Connection Strings.
2. Add ServiceBus connection string to Azure Portal > function-app-2 > Configuration > Application settings > Connection Strings.
3. Add CosmosDB connection string to Azure Portal > function-app-2 > Configuration > Application settings > Connection Strings.

After Azure resources were provisioned and configured, both Azure functions needs to be deployed for example from Visual Studio Code.

After successful deployment go to Azure Portal > function-app-1 > GenerateMessage function and select Get Function Url. Add query parameter message with some message to the function URL and execute GET HTTP request by opening this URL in browser. Alternatively, you can use POST request with HTTP body:

{
	"message": "your message"
}

After successful execution, message is sent to ServiceBus queue.

After message was generated, second Azure Function is listening for messages in ServiceBus queue. After a message was received, it is written as a new record into CosmosDB database.

Distributed under MIT License. See LICENSE for more details.