KUDU Console In Azure

This article will help you understand what KUDU console is in Azure and how to work with it.

Introduction
 
This article will help you understand what KUDU console is in Azure and how to work with KUDU.
 
KUDU Console
 
KUDU Console is a debugging service for Azure platform which allows you to explore your web app and surf the bugs present on it, like deployment logs, memory dump, and uploading files to your web app, and adding JSON endpoints to your web apps, etc.
 
To access the KUDU console of a Web App, you should be the admin for that particular Web App. Using your Azure login credentials, you can access the KUDU console of your Web App, by entering https://#####.scm.azureWeb Apps.net
 
Note: ##### is the name of your Web App.
 
Developer Requirements
  1. Windows Azure account (Click here to get a temporary Azure account for free)
  2. Visual Studio 2015 – optional (If you don’t have a Web App hosted on your account)
  3. Web Browser
Click here to learn how to host a Web App using Visual Studio.
 
Follow the below steps to access the KUDU console of your Web App.
 
Note:
  • Here, in this demo, I will be working on my own Web App.
  • #### refers to the Web App name.
Step 1: Open your web browser and go to https://www.####.scm.azurewebsites.net
 
 
Step 2: Enter your Azure login credentials over here (Login to the Azure account where your web app has been hosted).
 
 
This will take you to the KUDU Troubleshooting Console page of Azure related to your Web App.
 
 
 
Step 3:
 
Now go to the Debug Console. Debug Console can be accessed by two ways, either via CMD or via PowerShell. Here, we will be working with PowerShell.
 
Debug Console --> PowerShell.
 
 
 
This page with PowerShell will appear.
 
Step 4:
 
Enter the command powershell –command get-process
 
 
 
Here, you can see the process running on your website. You can find the changes when you give a request at your website, using Id-PID of the W3WP process.
 
If the changes happens, then the website has a chance of crashing and you need to troubleshoot to find the cause.