Deploying ASP.NET Core to Azure App Service

Introduction

Azure App Service is the fastest path to production ShopNest SaaS — managed PaaS with scaling, slots, and SSL without managing IIS yourself.

After this article you will

• Choose App Service plan (F1/B1/P1 cost in INR)
• Deploy via VS publish and GitHub Actions
• Configure connection strings in Portal
• Use deployment slots and Managed Identity
• Enable logging and custom domain

Prerequisites

• Article 60 — Docker
• ShopNest solution builds and tests pass locally

Concept deep-dive

Managed Identity: App Service authenticates to Azure SQL without password in connection string — Authentication=Active Directory Managed Identity.

Deployment slots: Deploy to staging, smoke test, swap to production — zero-downtime.

Hands-on — ShopNest Production SaaS Web App

1. Create App Service + publish ShopNest.Web.
2. Application settings: ConnectionStrings, Jwt__Key (never in code).
3. Enable staging slot; swap after validation.
4. Custom domain + free managed certificate.
5. Stream logs: az webapp log tail.

Common errors & best practices

• Connection string in appsettings.Production committed — use Portal settings.
• F1 cold start and no custom domain SSL on free tier limits.
• Always On disabled on Basic — app sleeps.

Interview questions

Q: App Service vs VM?
A: PaaS — Microsoft patches OS; you deploy DLL/container only.

Q: Slot swap?
A: Instant traffic switch staging↔production after warm-up.

Summary

• App Service PaaS for ShopNest SaaS production
• Secrets in Portal not source control
• Managed Identity removes SQL passwords
• Slots enable safe releases

Previous: Docker
Next: CI/CD with GitHub Actions

FAQ