There is a nice set of troubleshooting and analysis tools for use with Windows Azure Web Sites called KUDU.  Information about that tool set can be found here.

It is useful for capturing a memory dump, as explained here, looking at deployment logs, viewing configuration parameters and much more.

To access your KUDU console, using your DEPLOYMENT credentials, navigate to https://*****.scm.azurewebsites.net where ***** is the name of your WAWS.  Once authenticated, you should see a page similar to the one illustrated with Figure 1.

Figure 1, KUDU Windows Azure Web Site troubleshooting console

Clicking on the Debug Console, then PowerShell open a console similar to that shown in Figure 2.

Figure 2, Windows Azure Web Site PowerShell console

Enter the following command and you can see the processes running on your web site, results are shown in Figure 3.

  • powershell –command get-process

Figure 3, View Windows Azure Web Site processes using PowerShell

You can look at the Id-PID of the W3WP process and see if it changes when you run a request.  If it does, the process is likely crashing and that needs to be analyzed further to see why.