we are using the nsb with azure functions (httptrigger) along with managed identity (DefaultAzureCredentials)
when running locally using managed identity connection string we are able send messages but the handler is not able receive messages, the message is just sitting in the queue. however if we use a shared access key in the connection string, the handler is able to receive messages.
when running in cloud, using managed identity connection string, nsb is able to send and receive message without any issues.
to rule out any security issues locally we granted the developer a owner access to azure service bus, nsb does not throw any errors, from what i understand about handler if there is no matching handler an exception is thrown by nsb, i dont see any exception the message is just sitting in the quque.
any diagnostics that i can enable here ?