If worker roles could be scheduled, like windows task scheduler then we would massively reduce the required cpu time used.

Enables you to host more than one application on one Azure compute instance. Suitable for small departmental servers.

Live integration is configured in web.config of my Azure app. When I changed and created a new secret key, it demand me to rebuild the app and host it again. Looking for a facility to configure the web.config file or move all configurations into the Azure configuration file.

To allow hosting multiple (SSL) sites or domains for the same site on a single Windows Azure role.

Once Azure supports UDP for web and worker roles, it would be really nice to enable UDP multicast, at least for internal network traffic.

Some features of new .Net 4.5 (WCF support for websockets) will only be available from IIS8, which requires Windows Server 8 OS. Thus it would make sense to upgrade Azure to Server 8 ASAP.

Currently if you need to make a minor change to an ASPX file, javascript/css resource or web.config a full build and deploy on a local machine is required before the changes will be seen. This is not usually required when doing normal web development as the project folder is the same as the folder being run by IIS. This is extremely inconvenient and wastes a lot of time, especially on slower machines.

UDP endpoints could support low-cost communication with our embedded systems over cellular networks.

Add Ruby (and Rails) as a first class citizen to web roles.

Worker roles need often access to DirectX or DirectCompute libraries in order to perform CAD processing based on GPU even in case the cloud-hardware would not have graphic cards available.
The cloud hardware should insted provide CPU and GPU clusters.

At the moment an app running with as a sub-domain of cloudapp.net cannot use https for passing passwords or other secure info. It would be very cool if Microsoft provided a SSL certificate which was valid for all *.cloudapp.net URLs.

Deploying based on configuration would like Release or Debug (or a custom one) would be very clean if the ServiceConfiguration.cscfg had the same ability as the Web.config files where you can create Web.Release.config and Web.***.config files based on the configuration. This makes it easy to create settings based on the configuration, like which connection strings to use. One could be for production and another for staging...and when using diagnostics, you can set it to the correct storage accounts.

Allowing Worker Roles (or Web Roles, as well) to host more than a handful of services would keep costs down for light use services that can coexist with eachother.

scaling number of web/worker role instances has to be set in the configuration file. I would like to have the number of instances change on run-time without user's intervention based on pre-set rules. Rules can be defined for #of requests on a certain instance, cpu utilization or memory available.

When i update the web role (incresing web roles, starting, suspending, ...) there is a short moment (or pretty long) when the web role is not responding. Customers than may see just browser error page "the page is not accessible" or "the server is not responding". In my opinion there should by allways some nice, user-friendly, response like "We are currently upgrading your application, please wait a few minutes. Thanks" with company logo or something.

There are tons of scenarios when you need to open a specific tcp port to listen for specific communication - legcy apps integration, near real time communication , etc.

I understand that Azure plans to provide multiple web roles per instance. But, Azure also need to provide multiple worker roles per instance.

I see no reason to have an instance for each role, when my roles are sitting idle most of the time.

Why are we still waiting for .NET 4.5 support on Azure web/worker roles?