Thanks for bringing this into our attention. I will file a bug for CMS team

This is already on our radar. Unfortunately Microsoft hasn't released a package for Service Bus yet, it's still in pre-release https://azure.github.io/azure-sdk/releases/latest/dotnet.html.

Original question is around Azure Storage (not ServiceBus). Old package has been split into multiple smaller packages (Microsoft.Azure.Storage.* and for tables you have to use CosmosDB client SDK). Wew have been through this migration process - and it's not super painful for super small project :) 99% are namespace changes.

For the ServiceBus case is not better - best bet for now is Microsoft.Azure.ServiceBus (https://www.nuget.org/packages/Microsoft.Azure.ServiceBus/). But I agree - it's really bad business from Microsoft side to name and release packages propery.

We have "Azure.Messaging.*", "Microsoft.Azure.ServiceBus.*" and "Microsoft.ServiceBus.*" namespaces :)

https://docs.microsoft.com/en-us/dotnet/api/overview/azure/servicebus/client?view=azure-dotnet-preview

Adding here as just was having interesting times with the fact that Episerver is using WindowsAzure.Storage when another 3rd party package version x.y was using the NuGet packages Microsoft.Azure.Storage.* WHICH ARE ALSO DEPRECATED and latest version of this 3rd party package is using the latest NuGet packages Azure.Storage.* packages so the nightmare "NuGet package hell is ready" cry 

I think we can thank you Microsoft for messing up the packages using old namespaces in new packages and changing where the implementation are (for example the two old NuGet packages have functionality to parse blob connection string and the latest doesn't OR I just didn't find where it was). But anyways understandable that MS wanted to separate/modularize the latest version of the packages but it has created a mess if something is using the older corresponding NuGet packages.

Also bear in mind that you could potentially hit a behavior where ServiceBus messages sent by older SDk is not reable by newer SDK :) And vice versa

Are there any news here?

I have just recently created a new production environment for a customer, but I suspect that support for Microsoft.WindowsAzure.Storage v9.3.3 is broken in newly created storage accounts. It works fine in the Preprod environment that is quite old (> 1 year since creation), but whenever I create a new Storage Account now (in the portal), I get (400) Bad Request

Accounts created through the portal are using API version 2019-06-01 - Im now trying to iterate through older versions to find the latest one that works.

EDIT Follow-up: "apiVersion": "2018-11-01" works fine. 

Hi. 

The latest comment on this post is a year old. Is there a solution for this?

I'm curious if I load the Azure.Storage.Blobs package, will it conflict with the existing, deprecated, WindowsAzure.Storage package?

Hi Nick,

The answer is simple, you have to test it ;)

But in one of our DXP projects we have both of these NuGet packages installed:

• Azure.Storage.Blobs v12.10.0
• WindowsAzure.Storage v9.3.3

..and they play nicely together.