Azure Service Bus trigger with connection=SB fully Qualified Name in binding file, is not working

Question

Azure Service Bus trigger with connection=SB fully Qualified Name in binding file, is not working

Abhishake Jaiswal 160

I am trying to implement to a Service Bus Queue Trigger in nodejs.

my binding file looks similar to below (just values of queue name and connection are updated to function app properties as in attached image)

{
"bindings": [
    {
    "queueName": "testqueue",
    "connection": "MyServiceBusConnection",
    "name": "mySBQItem",
    "type": "serviceBusTrigger",
    "direction": "in"
    }
],
"disabled": false
}

i have 2 doubts

If i put connection property (MyServiceBusConnection) as service bus connection string, it works fine. But if i put connection string as fully qualified name space, the trigger is not consuming messages from queue.

"connection": "SBConnection__fullyQualifiedNamespace"

I have given all required permissions to function to consume messages from queue. (Azure Service Bus Data Receiver, Azure Service Bus Data Owner)

I went through the documentation which says queue triggers work with managed identities and did steps as mentioned in below link.

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus-trigger?tabs=python-v2%2Cisolated-process%2Cnodejs-v3%2Cextensionv5&pivots=programming-language-javascript#connections

i tried to pass the queue name from function app properties in function.json
"queueName" : "%SB_MainQueue%"
but its not working. I need to keep Env specific Queue Names. Please advise

Both properties are set in function app configurations as shown in screenshot.

Any feedback is highly appreciated.

MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-08T15:51:30.86+00:00

Abhishake Jaiswal Thanks for posting your question in Microsoft Q&A. I assume you are using this test after deploying it to Azure since identity connections use Managed identity.

#1 When setting the connection to SBConnection__fullyQualifiedNamespace in the binding, have you validated that SBConnection__fullyQualifiedNamespace is defined in the Application setting and it resolved to fully qualified namespace like service_bus_namespace>.servicebus.windows.net? If so, for the trigger the managed identity requires RBAC roles such as Azure Service Bus Data Receiver, Azure Service Bus Data Owner and it appears that you had already validated that. Another thing to validate is to you use version 5.x or higher of the extension meaning ExtensionBundle [3.3.0, 4.0.0) or higher like described here.

#2 From the description, you are looking to use binding expression for queueName and this should work if you define the corresponding app setting matching the expression. Check out https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-expressions-patterns#binding-expressions---app-settings and validate the settings match correctly.

If you face the issue, suggest you enable logging in Application Insights and review the cause of the failure. Please let me know if you have any questions.

Abhishake Jaiswal 160

hi Muthu, Thanks for your inputs.

yes the application setting is defined with proper name space as in attached screenshot
Azure function extension bundle and service bus extension is defined in host.json file is

 "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[3.*, 4.0.0)"
  },
  "extensions": {
    "serviceBus": {
      "clientRetryOptions":{
        "mode": "exponential",
        "tryTimeout": "00:01:00",
        "delay": "00:00:00.80",
        "maxDelay": "00:01:00",
        "maxRetries": 3
      },
      "prefetchCount": 0,
      "transportType": "amqpTcp",
      "autoCompleteMessages": true,
      "maxAutoLockRenewalDuration": "00:05:00",
      "maxConcurrentCalls": 16,
      "maxConcurrentSessions": 8,
      "maxMessageBatchSize": 1000,
      "minMessageBatchSize": 1,
      "maxBatchWaitTime": "00:00:30",
      "sessionIdleTimeout": "00:01:00",
      "enableCrossEntityTransactions": false
    }
  }

Managed Identity for function app has all required Access, i have cross validated that.
All I can see in App Insight logs under Traces table is below message but not much details on what is wrong.
"The listener for function 'Functions.ServiceBusQueueTrigger' was unable to start."

Please let me know if some config is incorrect.

Abhishake Jaiswal 160 Reputation points

2024-01-09T01:05:12.87+00:00
hi Muthu, on further investigation in insights, i found below message in exceptions table in app insights:

Service Bus account connection string 'serviceBus__fullyQualifiedNamespace' does not exist. Make sure that it is a defined App Setting.

but i can see property correctly defined in function app Settings. (note : i updated name of property in function.json and function app properties)

function.json

{ "bindings": [ { "name": "mySbMsg", "type": "serviceBusTrigger", "direction": "in", "queueName": "%SB_MainQueue%", "connection": "serviceBus__fullyQualifiedNamespace", "autoComplete": true } ], "disabled": false }

I still cannot figure out where is the issue?
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-09T15:47:25.64+00:00

Abhishake Jaiswal This requires little more investigation on the backend. Can you send an email to azcommunity@microsoft.com referencing this thread with your subscription ID (not name), function app details along with subject as "Attn: Muthu". I can assist you offline.
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-10T14:34:22.7266667+00:00

Abhishake Jaiswal Just a follow up if you were able to resolve the issue or still need assistance.
Abhishake Jaiswal 160 Reputation points

2024-01-16T05:57:44.24+00:00
hi Muthu, the issue is resolved solution binding file should be like

{ "bindings": [ { "name": "mySbMsg", "type": "serviceBusTrigger", "direction": "in", "queueName": "%SB_MainQueue%", "connection": "serviceBus", "autoComplete": true } ], "disabled": false }

"__fullyQualifiedNamespace" only needs to be present in application config property. the documentation is not very clear regarding this.
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-16T14:35:07.5866667+00:00

Abhishake Jaiswal Thanks for sharing it with us. As I mentioned in the answer, will share feedback internally with the team to update.

Accepted answer

0 additional answers

Your answer

MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-08T15:51:30.86+00:00

Abhishake Jaiswal Thanks for posting your question in Microsoft Q&A. I assume you are using this test after deploying it to Azure since identity connections use Managed identity.

#1 When setting the connection to SBConnection__fullyQualifiedNamespace in the binding, have you validated that SBConnection__fullyQualifiedNamespace is defined in the Application setting and it resolved to fully qualified namespace like service_bus_namespace>.servicebus.windows.net? If so, for the trigger the managed identity requires RBAC roles such as Azure Service Bus Data Receiver, Azure Service Bus Data Owner and it appears that you had already validated that. Another thing to validate is to you use version 5.x or higher of the extension meaning ExtensionBundle [3.3.0, 4.0.0) or higher like described here.

#2 From the description, you are looking to use binding expression for queueName and this should work if you define the corresponding app setting matching the expression. Check out https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-expressions-patterns#binding-expressions---app-settings and validate the settings match correctly.

If you face the issue, suggest you enable logging in Application Insights and review the cause of the failure. Please let me know if you have any questions.
Abhishake Jaiswal 160 Reputation points

2024-01-09T00:29:52.09+00:00

hi Muthu, Thanks for your inputs.

yes the application setting is defined with proper name space as in attached screenshot

Azure function extension bundle and service bus extension is defined in host.json file is

"extensionBundle": { "id": "Microsoft.Azure.Functions.ExtensionBundle", "version": "[3.*, 4.0.0)" }, "extensions": { "serviceBus": { "clientRetryOptions":{ "mode": "exponential", "tryTimeout": "00:01:00", "delay": "00:00:00.80", "maxDelay": "00:01:00", "maxRetries": 3 }, "prefetchCount": 0, "transportType": "amqpTcp", "autoCompleteMessages": true, "maxAutoLockRenewalDuration": "00:05:00", "maxConcurrentCalls": 16, "maxConcurrentSessions": 8, "maxMessageBatchSize": 1000, "minMessageBatchSize": 1, "maxBatchWaitTime": "00:00:30", "sessionIdleTimeout": "00:01:00", "enableCrossEntityTransactions": false } }

Managed Identity for function app has all required Access, i have cross validated that.

All I can see in App Insight logs under Traces table is below message but not much details on what is wrong.
"The listener for function 'Functions.ServiceBusQueueTrigger' was unable to start."

Please let me know if some config is incorrect.
Abhishake Jaiswal 160 Reputation points

2024-01-09T01:05:12.87+00:00

hi Muthu, on further investigation in insights, i found below message in exceptions table in app insights:

Service Bus account connection string 'serviceBus__fullyQualifiedNamespace' does not exist. Make sure that it is a defined App Setting.

but i can see property correctly defined in function app Settings. (note : i updated name of property in function.json and function app properties)

function.json

{ "bindings": [ { "name": "mySbMsg", "type": "serviceBusTrigger", "direction": "in", "queueName": "%SB_MainQueue%", "connection": "serviceBus__fullyQualifiedNamespace", "autoComplete": true } ], "disabled": false }

I still cannot figure out where is the issue?
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-09T15:47:25.64+00:00

Abhishake Jaiswal This requires little more investigation on the backend. Can you send an email to azcommunity@microsoft.com referencing this thread with your subscription ID (not name), function app details along with subject as "Attn: Muthu". I can assist you offline.
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-10T14:34:22.7266667+00:00

Abhishake Jaiswal Just a follow up if you were able to resolve the issue or still need assistance.
Abhishake Jaiswal 160 Reputation points

2024-01-16T05:57:44.24+00:00

hi Muthu, the issue is resolved solution binding file should be like

{ "bindings": [ { "name": "mySbMsg", "type": "serviceBusTrigger", "direction": "in", "queueName": "%SB_MainQueue%", "connection": "serviceBus", "autoComplete": true } ], "disabled": false }

"__fullyQualifiedNamespace" only needs to be present in application config property. the documentation is not very clear regarding this.
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2024-01-16T14:35:07.5866667+00:00

Abhishake Jaiswal Thanks for sharing it with us. As I mentioned in the answer, will share feedback internally with the team to update.

Answer 1

Abhishake Jaiswal Glad to hear that you resolved the issue and thanks for sharing it with the community which will greatly help others with similar issues. As per Microsoft Q&A community policy: "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer. Resolution: Abhishake Jaiswal resolved the issue after changing binding configuration like below:

{
  "bindings": [
    {
      "name": "mySbMsg",
      "type": "serviceBusTrigger",
      "direction": "in",
      "queueName": "%SB_MainQueue%",
      "connection": "serviceBus",
      "autoComplete": true
    }
  ],
  "disabled": false
}

I will pass feedback to our doc team to add a description note regarding this. Let us know if you have any other questions.

Share via

Azure Service Bus trigger with connection=SB fully Qualified Name in binding file, is not working

0 additional answers

Your answer