Back in the old days, MVC3 was not supported out of the box because the corresponding DLL files had to be added by you manually (or installed as a launch task). Nowadays, MVC-dll is all used using the MVC3 template, so there is no difference what you need to do between asp.net and deploying asp.net mvc. The main roles on the Internet and roles are only the Windows 2008 Server virtual machines, and the deployment process is the same. The most important part at startup is to make sure that your storage connection strings point to the "real" storage, and not to the storage device (for example, the diagnostic connection string). In addition, the default session state is due to using SQLExpress, which does not work on Windows Azure, so you need to either use the Azure SQL database (plus the correct connection string) in web.config, or change the session state to use Cache (again, change web.config).