Issue:
The Attributes section describes both in-process and isolated model in a single sentence, but the ServiceBusTriggerAttribute link there leads to the Microsoft.Azure.WebJobs.Extensions.ServiceBus libraries source code that is meant for use with in-process model only.
According to Examples section in the same article, isolated model should use Microsoft.Azure.Functions.Worker.Extensions. and not Microsoft.Azure.WebJobs.Extensions.
Suggested fix:
Rewrite the sentence to have separate links to the correct ServiceBusTriggerAttribute for each model, or move the sentence inside the tabs below it for each model with the correct link.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 1d50399c-0873-e903-35ca-1845c84b6c6c
Version Independent ID: 1a3150b4-5eb9-0ac5-ee2b-d1bb6b6fd63e
Issue: The Attributes section describes both in-process and isolated model in a single sentence, but the ServiceBusTriggerAttribute link there leads to the Microsoft.Azure.WebJobs.Extensions.ServiceBus libraries source code that is meant for use with in-process model only.
According to Examples section in the same article, isolated model should use Microsoft.Azure.Functions.Worker.Extensions. and not Microsoft.Azure.WebJobs.Extensions.
Suggested fix: Rewrite the sentence to have separate links to the correct ServiceBusTriggerAttribute for each model, or move the sentence inside the tabs below it for each model with the correct link.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.