I have read plenty of literature in this context (see links below). The presence of classic vs new Azure management portal, Roles vs App Services, Azure Website vs Azure Web
With App Service, you can't RDP or install 3rd party software.
If you need to do that, look at Virtual Machines. Another option is using Cloud Services' Web or Worker Role (look for the startup task).
While you cannot RDP into Web App instances, you can connect to them via kudu and get a command prompt, by visiting yoursite.scm.azurewebsites.net
. You can also get to this through the portal:
This will give you several tools (such as process explorer, environment explorer, command prompt, and more). It's not an RDP replacement, as it's not designed to let you access specific instances. It's also not the way you should be installing/changing software (aside from general testing). But... it's as close to RDP as you'll get, with web apps. Here's what the console window looks like, which opens via the browser:
RE:Can I RDP to Azure App Service Web App underlying compute resource?
No, you are not allow to RDP into the machine. You application is running within a sandbox, depending on your plan, one machine might running multiple sandbox from different user.
RE: Can I install custom third party software components (e.g. Crystal Reports) to Azure App Service Web App underlying compute resource?
No, the machine will upgrade periodically, content might be reset. Also user that app is running on will not have the privileged to install application. If your application is depending on other dependencies, e.g asp.net web application, you should specify all dependencies during build time (nuget).
Check the first two reference you provide, they are talking about Azure Virtual Machine, not Azure App Service, where Azure Virtual Machine is SaaS, Azure App Service is a PaaS. If you are looking for something in the middle, please try Azure Cloud Service, it supports RDP and I believe you should be able to install third party apps with on start script.