Warm up IIS applications in WebRole
By default the web application in a web role is not loaded until the first request is issued against the role. In large applications the loading time for the first page can be quite long which gives a very bad experience for users and search engines.
IIS provides some features to avoid this, but it complicated to use them in Azure:
I'd like to suggest the following:
Azure should support application warm up out of the box - when a role is restarted due to redeployment or maintainance, the warm up should be done automatically. The admin might specify a request URL that is called after the role started.
The default settings for application pool idle timeouts and recycling timeouts should be changed to infinity. web roles are typically not shared hosting environments where the idle timeouts make sense.
Michael CARBENAY commented
Adding a simple way to precompile asp.net website would be a great thing to add too : for quite large and complex apps, every page tends to take a few seconds to compile on first access.