A deployment to your Azure Web App is failing, and the app won’t start. You need to inspect running processes, view environment variables, and obtain the generated deployment script that App Service would use for your runtime stack, all from the platform tools. Which Kudu actions should you use?

The Kudu Process Explorer directly shows running processes, their command lines, and resource usage, which is crucial for diagnosing why an app isn't starting. The Kudu Environment page provides a comprehensive view of all environment variables and app settings, essential for verifying configuration issues. Kudu's "Download deployment script" tool generates the exact script App Service uses for deployment, allowing you to inspect the build and deployment steps for errors. The App Service Configuration blade exports ARM templates, not deployment scripts, and doesn't directly show running processes or environment variables. The Kudu Debug console can be used to run commands, but iisreset is for IIS-based apps and doesn't directly help in viewing environment variables or deployment scripts; you'd use other Kudu tools for those specific tasks.