Amy’s Kapers

Building Quokkabot Part 3: Moving to Azure Static Web Apps

Last week I got the chance to speak at Microsoft Build, and do a first-look demo on their newly announced featured - Azure Static Web Apps. And as I didn’t get access to Static Web Apps until they same time everyone else did (the day before my demo), I got to showcase how simple it was the first time you used it (ok, so maybe it was the second time that I’d used it).

Deploying from GitHub

Using an existing static site, with information about Quokkabot, built with Eleventy, I set up the continuous deployment pipeline which uses a GitHub action to trigger the site to rebuild in Static Web Apps.

From the Azure Portal, create a new resource for Static Web App (currently in preview)

Select your Azure subscription and resource group (for now, Static Web Apps is free), you’ll need to authorise your GitHub account and select the repository and branch you’re deploying from.

Specify the details for the site build, my static site sits in the root folder of the repository, and builds out to a folder called _site. While I don’t have an API to include there yet, leaving the API location as is is fine (if they can’t find the api folder, they’ll ignore it.

Next, click Review + create to create the new resource.

This will automatically create a workflow file in your repo, with a GitHub action to build the site and deploy it to Azure.

That’s it. You’re done.

Setting a Custom Domain

In the Azure portal, you can add a custom domain to your application. Click to Add a new domain, and setup the DNS records provided, then wait to verify the DNS changes.

Again, you’re done.

Adding an API back end

I already had a separate repository where I was running the Quokkabot back end on Azure Functions, so as Static Web Apps uses Azure Functions for the back end that was also simple to integrate, as it’s set up from the start.

I created a new folder in the static site project called api and copied all the files from the API repository over, then deployed the updates.

When the GitHub action detects the API folder, it will deploy that part of the project to Azure Functions. These functions then appear in the Azure portal with the static site.


Azure Static Web Apps has only been available for a week, is still in preview and therefore not suited to production apps. But so far this is a really great product, great integrations and simple and easy to use. There are a few gotchas or issues though

Node Modules

During the build process, Azure uses it’s own node_modules folder to install things in, __oryx_prod_node_modules, which as it wasn’t called node_modules, my Eleventy site tried to build out the content 🤦‍♀️. This was an easy fix though, by adding that folder to the .eleventyignore file, the build ignored it.

Azure Functions


While Static Web Apps does use Azure Functions for the API back ends, there’s a layer that sits between the two, which currently stops the API sending custom headers with the response (such as Content-Type). This has been lodged as an issue though and should be fixed shortly.

Update 1-June-2020: This issue has now been fixed, and Azure functions are now passing through custom headers.

You can see the live site at