Neeraj Makam

@mikermesh The client currently only exposes how "to use SASToken". Generating SASToken is a pending work item that needs to be done. Almost entire code is already present and just...

@DavidBerg-MSFT If you already have a SAS token, we do accept it. But this library still doesn't expose generating a SASToken. That's why this is an enhancement issue which is...

We will work on this issue shortly. Meanwhile, till the time the fix gets deployed across all data centers, please consider using authorization rule with `send` claims as well.

This is something that needs to be done. But there is no timeline for this as of now. This thread is open for discussion on what is the best way...

@SeanFeldman , do you expect the variance in machine clocks (for UTC) be considerably more than the variable in the latency of the send scheduled message request?

@SeanFeldman , Is this an issue you actually encountered?

Closing this issue as it is already opened the service side repo: Azure/azure-service-bus#40

Makes sense. I'll reopen the case. Will close it if required after the initial triage on the other repo.

`ManagementClient` and old client's `NamespaceManger` doesn't support MSI right now in preview phase. The service needs few more changes. Right not MSI can be used only with the ARM based...

What's the scenario? When you are creating a new Queue? This isn't supported in any nuget package as of now. Are you referring to the changes in the PR?