Skip to content

.NET Guide

This guide covers the end-to-end path for running ASP.NET Core applications on Azure App Service.

Main Content

flowchart TD
    A[01 Local Run] --> B[02 First Deploy]
    B --> C[03 Configuration]
    C --> D[04 Logging & Monitoring]
    D --> E[05 Infrastructure as Code]
    E --> F[06 CI/CD]
    F --> G[07 Custom Domain & SSL]
  1. 01 - Local Run
  2. 02 - First Deploy
  3. 03 - Configuration
  4. 04 - Logging and Monitoring
  5. 05 - Infrastructure as Code
  6. 06 - CI/CD
  7. 07 - Custom Domain and SSL

Advanced Topics

Use .NET recipes to apply identity, data, networking, and deployment patterns.

Run It in the Portal

Portal view: App Service Plan overview (hosting tier for the .NET guide)

App Service Plan overview blade showing the Linux plan asp-test-20251107 in Korea Central with Pricing tier "Premium0 V3", App Service Plan kind "Linux", Status "Ready", Operating system "Linux", and 1 instance; the right-side charts show CPU Percentage and Memory Percentage time-series for the plan and a list of the apps and slots hosted on the plan including app-test-20251107 and its staging slot.

The App Service Plan overview blade is the Portal view of the hosting tier this .NET guide deploys onto. This particular screenshot was captured from a Python deployment, so the visible App Service Plan kind: Linux and Operating system: Linux reflect that deployment; for the ASP.NET Core 8 path in this guide the equivalent values read Windows because the .NET tutorial uses --runtime "DOTNETCORE:8.0" on a Windows App Service plan. The remaining plan-level fields — Pricing tier: Premium0 V3, Status: Ready, the instance count, and the right-side CPU Percentage / Memory Percentage charts — are the same surfaces you use to verify plan health regardless of OS, along with the hosted-apps list showing app-test-20251107 and its staging slot attached to the same plan.

See Also

Sources