Azure Service Bus message flow node for ACE

Thank you for taking the time to raise this enhancement request, and in particular for the links which you included to the blogs. These were helpful for us in clarifying the difference between what you have already managed to get to work in the ACE product in its current form, and the vision you have painted for a future Azure Service Bus Toolkit message flow node. As noted, the Toolkit's JMS node is intended to work with any JMS compliant provider, but comes with the disadvantage that a user must provide the JMS driver themselves, and for those not familiar with the transport they might find the configuration complex. A discovery connector, which presents a graphical dialog for connecting to the Azure Service Bus which already has built into it all the drivers it needs, would make the product more useable. Typically discovery connectors do not necessarily expose the protocol by which they connect to the endpoint application, so it could be that AMQPS is not necessarily the means by which such a connector would gather back metatdata / connect at runtime. Also noted, the ability to address the queue/topic definition seems a of key importance to the requirement. Status is updated to Future Consideration. We will also pass this requirement on to our Product Manager for connectors ( @Varun Jain ) as we would likely want to implement this as a Discovery Connector that could be used both within a Toolkit message flow and also a Designer message flow.