While working on a new project which is based on a SharePoint provider hosted app we decided to put some of the functionality in Windows Azure. During the development phase of the project we wanted to debug some of the components locally.
The Windows Azure services which we used were the Azure Tables storage service and the Azure Queue storage service, eventually the Azure Worker role would be added to the set.
To debug the first two locally you can make use of the Windows Azure Storage emulator, by the time of writing this was installed on our development machines via the Windows Azure 2.2 SDK.
While running the project against the local development storage we run into a “400 – Bad Request” error when connecting to the tables or the queues. Digging into this error we found that the Windows Azure Storage Client installed via a NuGet package was of version 3.1.0.0 and the emulator did not support this yet.
On the Microsoft download site there is a preview version of the Windows Azure storage emulator available, version 2.2.1. While looking at the details of this package it described the problem we were experiencing: “Updated DLL's for Storage Emulator included in SDK 2.2, which add support for REST version "2013-08-15" to the Storage Emulator. This allows Storage Emulator to be used by version 3.0 and later of Windows Azure Storage Client Library for .NET.” After installing this update we could successfully connect to the local development storage.