We are working on a solution that will publish messages on an Azure Service Bus topic but we don't know yet which other team or even third party might be interested in subscribing to those messages in the future.

What would be a secure but flexible approach to provide subscribers with the ability to create their own subscriptions and the published messages but not affect any other subscriber or compromise the publisher?

Alternatively, we could be creating the subscriptions for them using the owner issuer credentials but that becomes a manual process.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.