Sign in to track progress and bookmarks.
Azure App Service is the default choice for hosting .NET web applications. It's a Platform-as-a-Service (PaaS) that handles patching, security, and scaling for you.
This is the 'Killer Feature' of App Service. You can create a **Staging Slot**, deploy your .NET code there, verify it, and then perform a **Zero-Downtime Swap** with Production. If anything goes wrong, you can swap back instantly. This is 'Blue-Green' deployment at its simplest.
Do not store connection strings in your `appsettings.json`. Use the **Environment Variables** (Configuration) section in the Azure Portal. These settings are injected into your .NET app at runtime and override your local settings. Combine this with **Key Vault References** for maximum security.
Q: "Should I host on Windows or Linux?"
Architect Answer: "For modern .NET (Core 2.1+), always choose **Linux**. Linux App Service plans are significantly cheaper (sometimes 50%) and usually offer better cold-start performance for containerized apps. Only use Windows if you are hosting legacy .NET Framework 4.x applications."
Quizzes linked to this course—pass to earn certificates.
On this page
1. Deployment Slots 2. Managed Configuration 3. Architect Insight