App Connect

 View Only

 Unable to connect to Azure Service Bus using the Azure Service Bus Request node

Jump to  Best Answer
Francis Cocx's profile image
Francis Cocx posted Mon June 23, 2025 07:45 AM

I am trying to connect to an azure sb message object using Connector Discovery. To do this I am using the connection URL that was provided by our azure service bus team for that specific object in the following format:

Endpoint=sb:/<namespace>.servicebus.windows.net/;SharedAccessKeyName=<SharedAccessKeyName>;SharedAccessKey=<SharedAccessKey>;EntityPath=<queueName>

Using that connectionstring in Azure ServiceBus explorer the connection is setup with no issue:

However entering the same connectionstring via Connector Discovery immidately triggers an error:



In ibmtkelectronapp.log in .metadata of the workspace I can also see the following Errors:
"msg":"Invaid Permission/Credentials","v":0}   

{\"message\":\"Validate connection for authType BASIC_MESSAGE WAS REDACTED AS IT CONTAINED SECRETS (API_KEY)\",\"statusCode\":500,\"error\":{\"errorName\":\"error_ping_failed\",\"statusCode\":500,\"inserts\":[\"azureservicebus\",\"BASIC_API_KEY\",\"[object Object]\"],\"errorBag\":{\"errorDetails\":\"[object Object]\"},\"message\":\"Validate connection for authType BASIC_MESSAGE WAS REDACTED AS IT CONTAINED SECRETS (API_KEY)\",\"status\":500}}",

Kim Meynendonckx's profile image
Kim Meynendonckx IBM Champion  Best Answer

Hi Francis,

I just tested it and for me it works. My guess is that your connection string in incorrect. Try to remove the "EntityPath".

The connection string I used:

Endpoint=sb://-------------------------;SharedAccessKeyName=--------------------------;SharedAccessKey=-------------------------------

mvg

Kim

Francis Cocx's profile image
Francis Cocx

Hi Kim,

Looks like it was indeed a permission issue on the azure queue on azure serviceBus. Thanks for checking.

KAPISH MALHOTRA's profile image
KAPISH MALHOTRA

The connection string should be in the format as mentioned by Kim.

@Francis Cocx can you confirm if just adjusting the connection string worked for you?

Endpoint=sb://<NAMESPACE>.servicebus.windows.net/;SharedAccessKeyName=<KEY_NAME>;SharedAccessKey=<KEY_VALUE>
Francis Cocx's profile image
Francis Cocx

@KAPISH MALHOTRA Yes indeed. I can confirm that it works with the ConnectionString Kim provided. Once I removed the EntityPath and resolved the Permission Issues it worked.