.Net application development specialists
asp.net, c#, vb.net, html, javascript, jquery, html, xhtml, css, oop, design patterns, sql server, mvc and much more
contact: admin@paxium.co.uk

Paxium is the company owned by myself, Dave Amour and used for providing IT contract development services including


  • Application development - Desktop, Web, Services - with Classic ASP, Asp.net WebForms, Asp.net MVC, Asp.net Core
  • Html, Css, JavaScript, jQuery, React, C#, SQL Server, Ado.net, Entity Framework, NHibernate, TDD, WebApi, GIT, IIS
  • Database schema design, implementation & ETL activities
  • Website design and hosting including email hosting
  • Training - typically one to one sessions
  • Reverse Engineering and documentation of undocumented systems
  • Code Reviews
  • Performance Tuning
  • Located in Cannock, Staffordshire
Rugeley Chess Club Buying Butler Cuckooland Katmaid Pet Sitting Services Roland Garros 60 60 Golf cement Technical Conformity Goofy MaggieBears Vacc Track Find Your Smart Phone eBate Taylors Poultry Services Lafarge Rebates System Codemasters Grid Game eBate DOFF

Open Kudu (Advanced Tools) for App Service & Azure Functions

Fastest way (direct URL)

Replace <app-name> with your site/function app name and open: 

https://<app-name>.scm.azurewebsites.net

Examples: myapi → https://myapi.scm.azurewebsites.net, contoso-func → https://contoso-func.scm.azurewebsites.net

From the Azure portal (when it’s in the menu)

  1. Open your **Web App** or **Function App** resource.
  2. Left menu → Development Tools → Advanced Tools (Kudu).
  3. Click Go › to launch Kudu in a new tab.

If you can’t see it in the menu

  • Use the portal’s top search bar and type “Advanced Tools” or “Kudu” while your app is open.
  • Open the app’s Overview blade, copy the Default domain (e.g., myapp.azurewebsites.net), then paste in a new tab and add .scm. after the subdomain:
    https://myapp.scm.azurewebsites.net
  • Still can’t access? Ensure the app is started and that your role has at least Contributor access.

What you can do in Kudu

  • Debug console (CMD/PowerShell on Windows, Bash on Linux) to run commands.
  • File browser to view/edit/download files:
    • Code: /site/wwwroot
    • Logs: /LogFiles (Windows), /home/LogFiles (Linux)
    • Function-specific logs: /LogFiles/Application/Functions
  • Process Explorer to see running processes and environment variables.
  • Tools → Zip Push to upload/deploy a zip package (handy for quick tests).

Quick navigation tips

  • In the console, use cd site/wwwroot to reach your app code.
  • Download logs from Debug console → LogFiles (right-click → Download).
  • For Functions, check host.json and function folders under wwwroot.

Good to know

  • Kudu runs in the same sandbox as your app. You don’t get full admin rights.
  • On Consumption/Flex plans, the file system can be ephemeral (don’t store state there).
  • If Kudu won’t load, confirm the app is running and that outbound access isn’t blocked by a VNet/IP restriction.

Troubleshooting

  • 403/401: your account lacks permissions. Ask for at least Contributor on the resource.
  • 404: check the URL (must include .scm.) and that the app name is correct.
  • Can’t find logs: verify the correct path (/LogFiles on Windows; /home/LogFiles on Linux) and that logging is enabled.