如何在非Azure Functions环境下获取Azure Service Bus队列新消息通知？Azure Service Bus与Azure Functions触发器的通知机制是什么？

Great questions! Let's break this down for you:

1. How to get notifications for new Azure Service Bus queue messages in a non-Azure Functions app #

You have a couple of reliable approaches to detect new messages without tying your app to Azure Functions:

Long Polling with the Service Bus SDK #

This is the most direct method, using the official Azure Service Bus SDK to actively listen for messages with a long timeout (so you don't spam the service with frequent short polls). Here's a simplified C# example using the Azure.Messaging.ServiceBus package:

using Azure.Messaging.ServiceBus;

var connectionString = "<your-service-bus-connection-string>";
var queueName = "<your-queue-name>";

await using var client = new ServiceBusClient(connectionString);
ServiceBusProcessor processor = client.CreateProcessor(queueName, new ServiceBusProcessorOptions());

processor.ProcessMessageAsync += args =>
{
    var messageBody = args.Message.Body.ToString();
    Console.WriteLine($"Received new message: {messageBody}");
    // Process your message here
    return args.CompleteMessageAsync(args.Message);
};

processor.ProcessErrorAsync += args =>
{
    Console.WriteLine($"Error receiving message: {args.Exception.Message}");
    return Task.CompletedTask;
};

await processor.StartProcessingAsync();
Console.WriteLine("Listening for messages... Press any key to stop");
Console.ReadKey();
await processor.StopProcessingAsync();

The processor maintains an active connection and listens for messages efficiently—when new messages arrive, they're pushed to your handler immediately. You can configure options like batch size, concurrency, and lock duration to fit your needs.

Use Azure Event Grid for Push Notifications #

If you prefer a passive, event-driven approach (no polling), you can set up Azure Event Grid to send a push notification to your app's HTTP endpoint whenever a new message arrives in the queue:

• Create an Event Grid subscription targeting your Service Bus queue, selecting the Microsoft.ServiceBus.QueueMessageReceived event type.
• Configure your app to expose an HTTP endpoint that can receive Event Grid's POST requests (you'll need to validate the subscription handshake initially).
• When a message is added to the queue, Event Grid sends a payload to your endpoint with details about the message, allowing you to trigger processing.

This is ideal if you want your app to stay idle until a message arrives, reducing resource usage.

2. What protocol/mechanism powers the Azure Functions Service Bus Trigger #

Under the hood, the Azure Functions Service Bus Trigger relies on the AMQP (Advanced Message Queuing Protocol) and a persistent, efficient listening pattern built on the official Azure Service Bus SDK:

• The Functions host establishes a long-lived AMQP connection to the Service Bus namespace, maintaining an active receive link for the target queue/topic.
• Instead of short polling, the host uses a "long receive" pattern where it waits for messages to be pushed by Service Bus over the open AMQP connection—this ensures low latency when new messages arrive.
• The Functions host handles all the heavy lifting: managing connection lifecycle, message locks, retries, dead-lettering, batching, and concurrency controls. It automatically scales the number of listeners based on message volume (within your function's concurrency limits).
• At its core, it's a managed wrapper around the same SDK-based listening logic you'd implement in a custom app, but abstracted away so you don't have to handle the infrastructure and reliability details.

内容的提问来源于stack exchange，提问作者Allan Xu