Skip to content

Azure Functions docs#8237

Draft
mattmercurio wants to merge 21 commits into
masterfrom
azure-functions
Draft

Azure Functions docs#8237
mattmercurio wants to merge 21 commits into
masterfrom
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
DavidBoike and others added 15 commits May 5, 2026 16:00
* Convention-based handlers

* Apply suggestions from code review

Co-authored-by: Daniel Marbach <daniel.marbach@openplace.net>
Co-authored-by: Andreas Öhlund <andreas.ohlund@particular.net>

* Make a TLDR snippet

* Whoopsie

---------

Co-authored-by: Daniel Marbach <daniel.marbach@openplace.net>
Co-authored-by: Andreas Öhlund <andreas.ohlund@particular.net>
* Registration page first version while keeping some redundancy

* Fix missing index problem

* Better page split and wording tweaks

* Refactor handler registration example in documentation

Updated the registration code example to reflect new API usage.

* Small tweaks

* Fix version boundary to use integer majors

* Apply suggestions from code review

Co-authored-by: Andreas Öhlund <andreas.ohlund@particular.net>

* Switch order

* Better documentation around the conventions

* Explain better the conventions

---------

Co-authored-by: Daniel Marbach <danielmarbach@users.noreply.github.com>
Co-authored-by: Andreas Öhlund <andreas.ohlund@particular.net>
* 2 projects needed a Core reference

* Change affected samples to Core 10 alphas

* Easy NSB.Extensions.Hosting removals

* Rest of NSB.Extensions.Hosting

* Delete "Passing user identity between endpoints using a custom header" sample that uses mutators

* Remove "Startup and Shutdown Sequence" sample

* Fix deprecated APIs in 4 samples

* Updated more samples

* Bunch more samples

* Fix bad cancellation token usage

* Couple more

* Need to review this Kafka-Functions sample separately

* Kinda big SqlP sample

* Bunch more

* Version-scope the externally managed mode sample and add a warning

* Remaining samples

* Fix links and related

* Another fix
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

Comment thread nservicebus/hosting/azure/functions/index.md Outdated
Comment thread nservicebus/hosting/azure/functions/index.md Outdated
Comment thread nservicebus/hosting/azure/functions/index.md Outdated

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?

@mattmercurio mattmercurio force-pushed the azure-functions branch 2 times, most recently from 56fc1c8 to 2c3ae96 Compare May 18, 2026 19:46
Base automatically changed from core-10.2 to master May 21, 2026 15:20
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.

4 participants