Reference architecture: scalable .NET web application on Azure — Microsoft Azure for .NET Developers

14. Reference architecture: scalable .NET web application on Azure

Advanced★ Must knowLesson 14 of 14

Users → Azure Front Door (WAF, CDN, TLS)
      → App Service (or Container Apps) — autoscale, deployment slots, managed identity
          → Azure SQL (zone-redundant, failover group to paired region) via private endpoint
          → Azure Managed Redis (cache, sessions)
          → Blob Storage (files) via private endpoint
          → Service Bus (orders topic) → Functions / Container Apps workers (KEDA scale)
          → Key Vault (secrets, certificates), App Configuration (feature flags)
      → Application Insights + Log Analytics (alerts → Teams/on-call)
CI/CD: Azure DevOps / GitHub Actions + Bicep (IaC), workload identity federation

Reliability: zones + multi-region (active-passive with Front Door failover), health probes, retries/circuit breakers, queues to absorb spikes. Security: Entra ID auth, managed identities, private endpoints, WAF, Defender for Cloud. Cost: autoscale, reserved capacity for baseline, serverless for spiky workloads.