http://blogs.msdn.com/b/buckwoody/archive/2011/12/06/how-microsoft-helps-you-not-break-your-windows-azure-application-storage-services-versioning.aspxOne of the advantages of using Windows Azure to run your code is that you don’t have to constantly manage upgrades on your platform. While that’s a big advantage indeed, it immediately brings up the question - how do the upgrades happen? Microsoft upgradesen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/buckwoody/archive/2011/12/06/how-microsoft-helps-you-not-break-your-windows-azure-application-storage-services-versioning.aspx#10244674Tue, 06 Dec 2011 16:20:29 GMT91d46819-8472-40ad-a661-2c78acb4018c:10244674Neil Mackenzie<p>The following is documented on the Set Blob Service operation:</p> <p>-- The DefaultServiceVersion element can only be set for the Blob service and the request must be made using the 2011-08-18 version </p> <p><a rel="nofollow" target="_new" href="http://msdn.microsoft.com/en-us/library/windowsazure/hh452235.aspx">msdn.microsoft.com/.../hh452235.aspx</a></p> <p>The Blob service needs a default service version so it can support anonymous HTTP calls.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10244674" width="1" height="1">