Skip to content

Azure Functions docs#8237

Draft
mattmercurio wants to merge 5 commits intocore-10.2from
azure-functions
Draft

Azure Functions docs#8237
mattmercurio wants to merge 5 commits intocore-10.2from
azure-functions

Conversation

@mattmercurio
Copy link
Copy Markdown
Contributor

No description provided.

@mattmercurio mattmercurio self-assigned this May 5, 2026
@mattmercurio mattmercurio changed the title Starting Azure Functions docs Azure Functions docs May 5, 2026
@mattmercurio mattmercurio force-pushed the azure-functions branch 2 times, most recently from 004f58a to 0e65bc1 Compare May 5, 2026 18:46
@mattmercurio mattmercurio requested a review from DavidBoike May 5, 2026 18:48
Copy link
Copy Markdown
Member

@andreasohlund andreasohlund left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did a first shallow pass


An endpoint is a partial class composed of three parts:

- The class is decorated with `[NServiceBusFunction]`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It can be on the trigger method as well so we need to decide which approach to lead with

snippet: azure-functions-program-builder

> [!NOTE]
> `AddNServiceBusFunctions` is a source-generated extension on `FunctionsApplicationBuilder` declared in the project's default namespace. Ensure `Program.cs` imports that namespace.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> `AddNServiceBusFunctions` is a source-generated extension on `FunctionsApplicationBuilder` declared in the project's default namespace. Ensure `Program.cs` imports that namespace.
> `AddNServiceBusFunctions` is a source-generated extension on `FunctionsApplicationBuilder` declared in the project's default namespace. Ensure `Program.cs` imports that namespace. At least one function needs to be defined for the method to be available.


## Send-only endpoints

A send-only endpoint can be registered for components that need to dispatch messages without listening for incoming traffic, for example a function fronting an HTTP API:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A send-only endpoint can be registered for components that need to dispatch messages without listening for incoming traffic, for example a function fronting an HTTP API:
A [send-only endpoint](/nservicebus/hosting#self-hosting-send-only-hosting) can be registered for components that need to dispatch messages without listening for incoming traffic, for example a function fronting an HTTP API:


## Connection configuration

The connection string for Azure Service Bus is read from the Functions configuration. The same setting name is referenced in two places:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The connection string for Azure Service Bus is read from the Functions configuration. The same setting name is referenced in two places:
The [connection for Azure Service Bus](https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus-trigger#connections) is read from the Functions configuration. The same setting name is referenced in two places:


NServiceBus log output is forwarded to the Azure Functions logging pipeline automatically. Configure log levels and providers through the standard Functions logging configuration; no additional NServiceBus log setup is required.

Startup diagnostics are written when the host starts. In Azure they appear in the Functions host log stream and in any configured destination such as Application Insights.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default behavior is a no-op; writing to the log can be opted into via the new API @danielmarbach added in v10.2. Not sure if we have documented that yet?

{
[Function(nameof(Orders))]
public partial Task Orders(
[ServiceBusTrigger("orders", Connection = "ServiceBusConnection", AutoCompleteMessages = false)]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the default is AzureWebJobsServiceBus, I wonder if this can be leading users to use this one instead and get tripped up? (ie should we omit it since this shows basic usage)

{
var transport = new AzureServiceBusServerlessTransport(TopicTopology.Default)
{
ConnectionName = "ServiceBusConnection"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above, should we go with the default or not set this as all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants