Combining the powers of Azure SWA and APIs
summary
Azure Static Web Apps integrates APIs two ways: managed API = Azure Functions (consumption, single function app, limited runtimes) or bring-your-own = Functions/App Service/Container Apps/API Management linked under a fixed /api route with same-origin calls, 45s HTTP timeout and no WebSockets. Authentication flows via X-MS-CLIENT-PRINCIPAL header (base64 client principal), role invites and built-in providers. Demos show Blazor WASM calling managed and BYO APIs, GraphQL via HotChocolate, gRPC using grpc‑web with special CORS/headers, container CI to ACR via GitHub Actions, SW CLI local emulation, and Data API Builder for direct DB endpoints. Some integration quirks and CI setup required.
AI-written summary · about
chapters (16)
- 0:00Azure Static Web Apps intro
- 3:22Why use Azure SWA
- 10:04Managed API in SWA
- 13:57Demo: managed API
- 18:16Bring your own API
- 19:47Demo: external API
- 23:00Auth in SWA
- 28:01Demo: role-based access
- 33:00SWA with App Service
- 34:26Demo: GraphQL with ACA
- 44:57gRPC with SWA
- 47:29Demo: gRPC integration
- 51:23Local dev with SWA CLI
- 53:26Database connections in Azure Static Web Apps
- 57:22Demo: DB-driven API
- 57:44Summary & Q&A
related talks
59mAzure Static Web Apps for the Enterprise
27mAzure Static Web Apps for the Enterprise
26mBuilding your Brand Using Azure Static Webapps, One Step at a Time
26mMastering Azure Statis Web Apps code, config, deploy
45mDeploying your Static Web App with Your Favorite Framework in Minutes
08mDevOps + Azure Static Web Apps
36mAzure Static Web Apps
49mDeploying Apps to the Cloud At Scale
