Azure Release Notes (June 2012)
Updated: July 29, 2014
This document contains the release notes for the Azure - June 2012 CTP release. It covers the following information:
Management Certificates can only be managed in the older Azure Management Portal
Unable to use Remote Desktop Connection to connect to a load balanced Azure virtual machine
Cannot use the NET Framework 3.5 on Windows 8 when you target the IIS Hosted Web Core
Updates to the Azure Plugin for Eclipse with Java (by Microsoft Open Technologies)
Side-by-side installation of the Azure SDK for .NET (November 2011 and June 2012)
Unable to upgrade a single role on a multi-role tenant
Storage access key regeneration for virtual machines
Change in the behavior of the Lease Blob Storage API operation
Release Notes for Service Bus
Release Notes for SQL Database
For more information related to this release, see the following resources:
Latest updates in Azure- Service Updates
New features in the Azure Tools for Microsoft Visual Studio - What's New in the Azure Tools
You cannot use the new portal to manipulate management certificates. The topic Creating and Uploading a Virtual Hard Disk that Contains the Windows Server Operating System shows an example of how to start a task in the new portal and then use older portal to manipulate management certificates and complete the task.
A registry key setting can cause this error. Check the registry in your virtual machine for the following key and value. If it exists, delete it. Because you cannot connect remotely to the virtual machine, you will have to check the virtual hard disk (VHD) you uploaded to create the virtual machine.
If you are developing an Azure application on Windows 8, and you are targeting the Hosted Web Core, you must use the .NET Framework 4.0. You cannot target the .NET Framework 3.5. Because the Hosted Web Core is being deprecated, this issue will not be fixed.
For details on the updates, see What’s New in the Azure Plugin for Eclipse with Java (by Microsoft Open Technologies)
You can simultaneously install both SDKs on a single computer. Note the following details:
Installing both of these releases is the only side-by-side scenario. You cannot install other Azure SDKs side-by-side.
To avoid confusion when you install both versions, the public versions of the .NET assemblies have been changed. Assemblies from November 2011 are typically marked with version 1.0 or 1.1. The June 2012 release assemblies are labeled with version 1.7. This change will require you to recompile applications or to use assembly binding redirects to pick up the new June 2012 assemblies. For more information, see Assembly Binding Redirection.
When both releases are installed, they share the compute emulator.
The November 2011 release is not officially supported for Windows 8. If you install Windows 8, you must upgrade any November 2011 project to June 2012.
For compatibility purposes, the June 2012 release uses a publisher policy file for the Microsoft.ServiceRuntime.dll so that clients that bind to version 1.0 are automatically redirected to the 1.7 version. This publisher policy file is installed in the local development environment and on Azure.
This issue occurs in the following situation. You have a multi-role tenant that is running with the November 2011 SDK release. You upgrade your development machine to the June 2012 SDK. You then attempt to upgrade only a single role in Azure using the June 2012 release. The other roles are still running the November 2011 release. Azure will block this upgrade. To resolve this issue, upgrade all the roles to the June 2012 release.
Do not regenerate the storage access keys for the storage account that holds the VHDs you are using to run Azure Virtual Machines while the virtual machine is running. If the keys are regenerated under these conditions, the virtual machines will stop working. This is because the VHDs are stored as blobs in storage accounts. The blob is updated as the state of the Virtual Machine changes.
In the new 2012-02-12 REST API version of Azure Table service, we’ve fixed the issue discussed in our blog post PartitionKey or RowKey containing the percent ‘%’ character causes some Azure Tables APIs to fail. We now no longer double-decode in the Table service. If you had previously encountered this issue and worked around it by double encoding before sending to the service, this will be a breaking change when you update to the new REST API version.
The release notes for Service Bus are available at Service Bus Release Notes.
The release notes for SQL Database are available at Known Issues in SQL Database.
The release notes for the Management Portal for SQL Database are available at Known Issues in the Management Portal for SQL Database.
Other ResourcesIntroducing Azure