Overview This blog post walks through creating a React Azure Static Web App with an Azure Function App API backend. The React website gets a random number from a Azure Function App and displays on the Random Number button. The gif below shows the React websites behaviour. Background I have been learning Azure Static Web Apps over a long period of time, a few years now, and I am documenting my journey through 30 Days of Static Web Apps: #30DaysOfServerless | Azure Static Web

If you've ever had to manually toggle Power Automate flows on and off across multiple solutions, you'll know how tedious it gets. Click into the flow, wait for the page to load, turn on/off and repeat. Twenty times. It's slow and frankly beneath anyone's dignity. We wrote a small set of PowerShell scripts to automate exactly this, and this post walks through the problem they solve and how to use them together. The scripts can be downloaded from our Powershell Repo on GitHub

Sometimes, deploying Azure Static Web Apps via the CLI (SWA CLI) fails with unhelpful errors or no errors at all. This post describes how I modified the SWA CLI to improve logging and ultimately diagnose a silent deployment failure. The Problem In my case, I created a sample Static Web App with a home.html file instead of the expected index.html. As a result, deployments failed silently when running the following command: