Azure Static Web Apps for the Enterprise
summary
Claims that Azure Static Web Apps run in enterprise produce a reproducible recipe: deploy a standard (paid) tier (~€9/month) resource with a small Bicep module, run three pipelines (infrastructure, custom domain, code deploy) in GitHub Actions, use AZ CLI and the Static Web Apps CLI to publish a .NET 9 Blazor site and API, persist secrets and deploy tokens via az staticwebapp, attach Azure DNS with CNAME/TXT validation (apex token + sleep loop), connect Cosmos DB, and enable Auth0 + custom Azure Function roles for stable identities.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:49Proving enterprise use
- 5:06Infrastructure with Bicep
- 11:30Deploying the app
- 16:50Custom domain setup
- 25:59Deployment pipeline
- 37:21Authentication & enterprise
- 39:11Conclusion and book announcement
related talks
46mAzure Static Web Apps - From Zero to Deployed App In 60 Minutes
19mHow Static Web Apps saved time and money!
28mBuild Serverless Apps with Blazor
26mServerless & Deploying to the Cloud with VSCODE
36mCloud First Web Apps in Azure
59mServerless frontend, serverless backend, serverless security!
55mServerless Azure In The Enterprise
01h 03mServerless and App Service Security on Azure
