Cannot uses connection strings with SharedAccessSignature

[LuKePicci]

This format of connection string is getting refused as invalid (those ... are urlencoded values):

Endpoint=sb://<your-namespace>.servicebus.windows.net/;SharedAccessSignature=SharedAccessSignature sr=...&sig=...&se=...&skn=...

[SeanFeldman]

@LuKePicci, the connection string requires not a SAS token, but the key. The key is used to create the token, which you're trying to use in your example.

Connection string example:

Endpoint=sb://<your-namespace>.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=<redacted>

Note that the RootManageSharedAccessKey key is required as the tool has to perform management operations.

[LuKePicci]

I know about the KeyName/Key combo but I was trying to test a connection string we currently use in production which has the format I described.

I didn't know the tool only works with root management connection strings, mine is signed by a different policy on a topic and it only has receiver access.

[SeanFeldman]

I didn't know the tool only works with root management connection strings, mine is signed by a different policy on a topic and it only has receiver access.

Yeah, that won't work. And using a policy that is not root or doesn't have manage permission won't work.
Hopefully, this clarifies it and answers your question.