For different situations, at times, you may want a different DNS name for your service than the service name. In the old Portal you could do this. The new one automatically makes them the same. Requests this feature be added back.

When running a reserved instance of Azure websites I would like to see the metrics for memory usage.
This would allow me to see if I need to increase my instance size due to low memory before I start getting warnings.

SRS allows scheduling of reports to run every hour or such and a history of the report runs are available, allow this in the Azure reporting services as well. Also charge for CPU usage not hour, having a Reporting service should be an incredibly small footprint.

Every month I get an email telling me my invoice for Azure usage is ready, but it usually takes weeks before it actually is. According to support this is because my end of period date is out of sync with my "anniversary date". This is very annoying and tune consuming, having to check back every so often.

I want to avoid putting my production username/password for the Azure DB in source control where all other developers can see it and thereby have read/write access. This is not easy today. Couldn't it work similar to the way Azure credentials are transmitted during a deploy? Or maybe we could store this data in Azure tied to the account, and copied into new instances as they are spun up?

At this time, Azure sells several services to host blogs and other CMS systems. As a personal consumer of these services, my only option is "Pay-As-You-Go", which does not allow any limit on spending. Imagine what might happen if a personal consumer's blog is hit with a DOS attack? It would be pretty easy to ruin someone's bank account with no limit to the charges. Perhaps a business would not consider this a problem, but as a personal consumer, this is an incredibly scary line of thinking!

There is function in Service Management API that is called DeleteRole but that is not what this function do. Function requests deletion of entire deployment. New functionality could be that just role (virtual machine) could be deleted.

Enable storage analytics so during development the program can be further optimzed for the cloud

Add support for TimeZoneInfo class or .Net 4 to Azure Reporting so reports can adjust time zones for dates/times correctly for end users.

Currently there is only windows server images.

Allow possibility to drop existing cluster index on table to create another one.

At this time :
Impossible to create new one because it already have a cluster index on table.

Impossible to drop existing one because, Tables without a clustered index are not supported in SQL Azure

Allow Multicast operations within the virtual networks for IaaS

Now we just can create a VM with a 30G hard drive for drive C. But for some specific scenarios，the free space of drive C will reduce to zero very quickly. So we need to customize our drive C in order to deploy our own applications

I'd love to show my customers that we are currently in the process of offering them a set of great new features while my new cloud service is being deployed or is in the swapping period, rather then showing them a generic error they can't understand anything from.
What do you think?

Support exposing data through stored procedures on Azure

Restricting us to only the row key is very limiting. We currently have to maintain our own secondary indexes for other columns and this is very cumbersome, it should be a feature of the platform.

Currently the C: drive / root volume size is fixed as 30 GB which also includes the Operating System. Of course there are complex and pain ways to resize the root volume size upto 120 GB, but that is really really hard.

If there is a step in the VM launch wizard which will ask for the root Volume size of say 30 GB min and 120 GB min (if not more) and then create the VM. It will be really amazing.

This is a great feature in SQL Server that seems to have been hijacked for debugging or something in SQL Azure. It would be great to have this feature back. It would be better to invent some new way to provide this debugging in SQL Azure that doesn't introduce a conflict