Instead of thinking about what might be supported in Azure, it might be more useful to think about your problems as you decided to port your application:
- Web applications. Since the web role contains IIS, you will usually not have a problem moving the asp.net or asp.net mvc share to the Azure site. There are some glitches you will encounter - see my answer to this question for more details.
- user interface. If your application has a certain result similar to the WinForms application, you will not be able to launch it, since you do not have video output.
- GPU dependencies. If you do some background processing, depending on the specific GPU, you wonβt be able to run on Azure VM.
- Registry and other system level access. If your application needs to update the registry or run MSI, you will not be able to install the application.
- Similarity of instances. If your application requires session sticking (for example, a registered user MUST visit the same server instance with every access), you will not be able to do this.
- COM interop. COM communication is very limited since you cannot install anything through the registry. If you rely on Excel services, you will not have this opportunity.
- SQL restrictions. Today, SQL Azure is limited to 50 GB and does not offer to configure a server instance. Also, although it supports a large set of SQL Server, it does not support 100% SQL Server, so it is possible that some of your sprocs no longer work. There is no SQL agent today, so you will need to recreate this functionality in your workflow.
This is just a quick look at some of the problems you might run into - I'm sure there are others.
Just keep in mind that Azure provides Windows 2008 Server images for your application to run, so if your application can run in this environment today and does not require the things I listed, you must be in very good shape.
David Makogon
source share