Check These Out

Gurus

Microsoft has decided to separate the queue/topic send/receive functionality from the queue/topic management functionality. Some of these separations make sense, while others, like the inability to auto-provision new queues/topics does not.

In any event, we can still create these objects using the service bus REST API, but it requires some special handling, especially for authorization.

The send/receive client library uses a connection string for authentication. This is great. Its easy to use, and can be stored as a secret. No fuss, no muss. The REST API endpoints require a SAS token for authorization. You would think there would be a provider to produce a SAS token for a resource, given the resource path and connection string. You would be wrong. Finding working samples of the token generation using .net core 2.x was surprisingly difficult. In any event, after (too) much researching, I’ve come up with this: