Read on Twitter
Azure Static Web Apps is going to make your life easier and here’s why! (a thread) #MSBuild 
@msdev (1/16) https://azure.microsoft.com/services/app-service/static/
@msdev (1/16) https://azure.microsoft.com/services/app-service/static/
What you get – The speed of static front ends with the scaling of dynamic backends supported by a ton of features (2/16)
Easy publishing – It takes mere minutes to point your GitHub repository to Azure and publish a website (3/16)
Geographically distributed content – The static content is globally distributed putting static assets as close to your visitors as possible (4/16)
Serverless architecture – APIs are powered by Azure Functions brings automatic scaling to your back-end (5/16) https://docs.microsoft.com/azure/static-web-apps/apis
Custom domains & Free SSL – Beyond just being able to bring your own domain, you also get a free SSL cert that automatically renew (6/16) https://docs.microsoft.com/azure/static-web-apps/custom-domain
Staging environments – When you create a PR against a chosen branch, a staging environment is created. Here, you can test changes to logic and layouts all before committing to production (7/16) https://docs.microsoft.com/azure/static-web-apps/review-publish-pull-requests
Authentication – You can integrate with several authentication providers: Azure Active Directory, Facebook, GitHub, Google, and Twitter (8/16) https://docs.microsoft.com/en-us/azure/static-web-apps/authentication-authorization
Authorization - You can define your own roles and apply them to both static content and API routes (9/16) https://docs.microsoft.com/azure/static-web-apps/authentication-authorization
Custom routes – From fallback routes to custom 404s to redirects – you have granular control over routes for static content and APIs (10/16) https://docs.microsoft.com/azure/static-web-apps/routes
Easy access to user information – You can get the login info of a user with from JavaScript in the browser to read from headers in a function (11/16) https://docs.microsoft.com/en-us/azure/static-web-apps/user-information
Control over builds and deployments – Based on GitHub Actions, you can configure your build and deployment workflows. You can even edit the workflow file directly in GitHub if you want
(12/16) https://docs.microsoft.com/azure/static-web-apps/github-actions-workflow
(12/16) https://docs.microsoft.com/azure/static-web-apps/github-actions-workflow
You don’t have to start from scratch – You can publish from Gatsby, Hugo, VuePress, Next.js, Nuxt.js and more (13/16) https://docs.microsoft.com/en-us/azure/static-web-apps/
Getting started is easy – Choose a front-end framework or no framework at all (14/16) https://docs.microsoft.com/azure/static-web-apps/getting-started
Digging in is easy too! – There are interactive tutorials that cover Angular, React, Svelte or Vue as well as Gatsby - https://docs.microsoft.com/en-us/learn/modules/publish-app-service-static-web-app-api/ https://docs.microsoft.com/en-us/learn/modules/create-deploy-static-webapp-gatsby-app-service/ (15/16)
And lastly - it’s worth noting that even though Azure Static Web Apps is in preview, this great set of docs was made possible through a collab from @slace, @burkeholland, @chris_noring, @codebeast, @craigshoemaker, @ggailey777, @john_papa, @manekinekko, @sinedied (16/16)
