I would like to allow my employees to view the database directly in order to troubleshoot issues in the code. However, in a production environment I don't want them to be able modify and delete table entities and blobs accidentally.

Certainly a clear backup strategy is necessary, but it would be nice to be able to prevent this as much as possible.

If we could have two different secret keys for storage, one for read/write access and one for read-only I could protect the read/write key and provide employees with the read-only key.

Search is the important part of any system. Azure must need this facility for high scalable system.

The cache service is just too expensive to use for a significant amount of data. Especially since it first uses memory from instances we've already paid for!

Right now as a developer I feel a bit in the dark of what is coming next to azure. There are really great ideas on here, a small handful have been confirmed.

I have been told to wait for PDC 2010 - seem arbitrary. We arn't launcing an iPod here! There are things that are needed here, there is no reason to keep us in the dark.

Create API's to be able to monitor the health of DataSync and recover from any problems - which really means be able to perform changes /setup of DataSync through API's. Ideally I'd like the health info to be able to feed back to system center.

It is necessary to allow changing vmsize without repackaging. You can allow to overwrite it in service configuration file or come with better idea.

CloudPageBlobs should have a CURRENT snapshot that always directly follows the latest version of the blob it is refrencing. This would allow for many read-only mounts of the VHD with out having to manage the create/delete cycle of time stamped labels. Additionally this mount would reduce the unmount/remount cycle that moves around drive letters and can mess up previously opened files.

I have developed an application on Adobe Flex platform and running it on the Windows Azure platform.Although Microsoft haven't released Officialy the support for Action Scripts and MXML on the Azure platform but I have developed it and Microsoft should release officially its support as its running fine.And soon there will be a SDK for Flash Builder.

Allow more support for consuming requests in JSON and returning responses in JSON.

As a majority of rich web apps use Javascript, I would only image this would be huge.

There are lots of scenarios where WCF is an overkill, and a simple HTTP listener could reduce the round-trip time, reduce costs, and enable us the users with a more suitable, tailor made solution.

We have the need for ultra-fast record range retrieval from table storage (a la on-site SQL Server) from our web roles in the same data center. This is driving a data-intensive BI engine that relies on low-latency access to massive streams of data. Currently, we are looking to MongoDB to fill this gap.

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.

It is a bit harrowing to realize that you missed something out in your cscfg after you have deployed your app on the cloud. Sure...there is a feature wherein you can tweak the cscfg file without having to redeploy the package. But most of the times if new settings have been added to cscfg then same must be reflected on to csdef...thus eventually even if you do manipulate cscfg as per your needs you still have to redeploy the app because there is no facility to modify csdef.....

It is far too easy to make a configuration mistake that leads to huge costs. For instance, selecting instance size in VS2010 is a dropdown and selecting an Extra Large instance instead of Extra small instance is very easy. There is no warning. This should harder and more intuitive (e.g. a slider with color coding, green for low cost red for high cost). Also, you should be able to set a quota. One so you get a warning when you exceed certain costs, one to undeploy automatically if you exceed certain costs.

We should be able to fully customize the VPN gateway parameters for phase 1 & 2 negotiations:

* Specify the pre-shared key
* Lifetime values
* Encryption
* Static IP address that won't change if the gateway is deleted and recreated
* etc.

I would like to be able to provide access to the blob service *somewhat* directly instead of proxying the calls through another service.
I'm thinking of smart client applications that would allow my clients to login using ASP.NET authentication and browse blobs and tables for which they have the authority to view.