Currently, all shared websites must end with *.azurewebsites.net

Think even shared websites should support multiple bindings per site. The current implementation restriction *.azurewebsites.net is ridiculous and this way this all shared service is just "demoware" - no real sites will use this.
Dotnetnuke for example, is multi-tenant by design. but in this service it is just interesting for testing.

If a Role is .NET only then a whole VM is overkill. How about having the option to deploy a role to a Process or AppDomain. This should be cheaper to run and make deployment much faster.

Allow users to create dev or staging environments that can be deployed to first to validate changes and then swapped with the production site.

Need support for ICMP features like Ping in Azure Websites, Azure Mobile Services thru node.js, Web/Worker Roles/Cloud Services.

We know there is a way to add MIME type using web.config but if possible is it add platform site as default to avoid miss configuration?

The trust settings for web sites doesn't allow for defining custom SSL certificate validation, for example when calling 3rd party web services, specifically by using the ServicePointManager.ServerCertificateValidationCallback API. Please consider either allowing that API or maybe a more sophisticated model of including defining custom trusted certificates or CAs as part of the web.config.