Learning to Hugo Part 5: Azure Static Webapp


This is the fifth part of the learning to Hugo series detailing my journey to getting this site up and running! Typical dev approach I just installed Hugo and got going. But I have learnt a few things along the way that have improved my development time and hopefully these things will help you.

In this section I'm going to explain how to set up a static webapp to host my hugo site.

Health & safety warning

I'm no web dev! My world is data and so this stuff is outside my area of expertise. I'm learning as I go and so the info I'm sharing is my interpretation of that in a way that makes sense for me as a data-person-doing-web-dev. Some of the technical aspects might be a little misunderstood and I'd love to hear from you in the comments if you think there's a better way or if I've misunderstood a concept. Hopefully outlining my understanding of it might make it easier for someone wanting to give it a go. If you want advanced CSS understanding or web development skills though these are not the posts you're looking for!

obi wan kenobi saying these are not the posts you're looking for

obi wan says these might not be the posts you're looking for

Prepare your repository

Before creating your static webapp, you need to push your changes to github so that it can be picked up by the webapp. I’m not going to cover that here but note that it doesn’t matter if your repository is public or hidden, this will still work.

Provision a static webapp

Go to the Azure Portal and search for the static web apps option to create a new resource. At time of writing the service was still in preview…it probably isn’t by the time you come to read this.

screenshot of the first option screen of creating a webapp

First set of options are which subscription, which resource group, a name for your app and the region you want it hosted. The name given here just names the resource, it doesn’t have any affect on your published site.

screenshot of the initial configuration of your webapp, which asks for the subscription, resource group, and region you want to create the webapp in, and also the name of the webapp

At the bottom of the first set of options, the app requests you to sign in with github, this is to permit the app to create workflows and assign secrets to your repository so that when you apply changes to your repository they are pushed to your webapp.

screenshot of the authorisation request between your static webapp and github

Once you have granted access to github, you can select the repository and branch you want to use. This simply means which branch will be used to deploy to the webapp, I’m using the main branch of my repository.

screenshot of the configuration page, once authorisation given, you can then select which organisation, repository and branch from github

You then need to tell the static app which build presets need to be used. Since I’m using Hugo, that is the preset I’m going to use. The app location is the path to the root of your hugo files in the repository and the app artifact location is the directory in which the built version of the site will exist. By default, Hugo builds to the public folder.

screenshot showing the configuration options once you have selected hugo for build presets, you are asked the app location, api location, and output location, the api location is not filled in as it is not applicable here

Once you have completed the configuration steps, the static app will be provisioned and workflow files will be created within your repository and the site will start being built. You can see the status of the build and deployment by opening the workflow file in your repository, a yellow dot indicates that the workflow is running, a green dot indicates that the workflow has completed successfully and a red dot indicates that the workflow has failed. In the screenshot below, you can see that the workflow is running.

screenshot showing the code that represents the build workflow in github, there is a small yellow dot at the top of the workflow representing the current status of the workflow, which is running

If I click on the dot I will get a summary of the steps that are running and the output of each step. In the screenshot below, you can see that the build step is running.

screenshot showing a summary window that has appeared in front of the workflow, there are two steps - build and deploy, and close pull request - build and deploy is running, close pull request is skipped

Clicking on the details link will show me more information of the build steps. Once the build is complete, a green tick will appear. Your static app will now be available to browse, but first we need to find the URL of the site! Each static app by default has a random url until you assign it to your own domain. You can find out what that url is in two ways. First, the build summary will show you the url of the site if you expand the build and deploy step…

screenshot of the workflow activity details, the left pane shows a summary of each job and the right pane shows each step that has occurred as part of that job, each step has a tick next to it representing a completed step. There is an arrow next to each step meaning that you can expand the step to see the full logging details returned

Navigate all the way to the bottom of the summary where one of the final messages will show the URL…

the final message in the step says 'deployment completed, visit your site at'

You can also find the url of your site from the summary section of the Azure resource…

screenshot showing the overview section of the static webapp on the azure portal. In the right hand pane is a URL block that reads

Custom Domain

The next thing to do is to assign a custom domain to your site. Right now your site url will be something like and whilst that might be an interesting talking point, it’s not very memorable. So let’s assign a custom domain. I’m not going to cover purchasing a domain, but hopefully you have a nice domain name to assign to your site. I’m also going to walk through how to set this up using Cloudflare which I use across multiple sites. To use Cloudflare you need to change the nameservers of your domain to point to Cloudflare. If you don’t want to do this, you can use your domain provider to assign a CNAME record to your site. I expect the steps will be relatively similar.

Configuring CNAME records

Our objective here is to direct my preferred domain name to where my site is hosted at, if you’re following along you need to use your new domain name and your static app url. Go to the DNS section and create two CNAME records. The first directs to your static app url and needs to be configured with www in the name…

the DNS management section of cloudflare, a CNAME record has been created as described above

The second CNAME record will be set up to redirect the apex domain to the www domain. The name of the record will be the apex domain and the value will be the www domain. In my case, the name is @ (which represents root) and the value is

the DNS management section of cloudflare, a CNAME record has been created with '@' as the name value and '' as the Target value

This is a neat trick that Cloudflare offers called CNAME flattening which allows you to redirect the apex domain to the www domain. This is useful because Azure Static Webapps doesn’t support apex domains.

Set up redirect rule

Last thing on Cloudflare is to set up a redirect rule. The purpose of this is to simply direct any url using the apex domain i.e. to the corresponding page of the www domain i.e. . To do this, go to the page rules section under rules. Create a new rule with the following settings

the page rules section displays a rule being created with the settings as described above

The purpose of this is to tell cloudflare that any URL that is targeted at should be sent to the same URL but with www in front of it. The pattern* means that any URL that starts with will be captured and the $1 grabs everything within the wildcard and adds it to the www version of the url. So if someone navigates to they will be redirected to pretty cool huh?

Assign domain to static app

Now that we have our domain set up, we need to assign it to our static app. Go to the custom domains section of your static app and add your domain name. For this section to work, you must have set up the CNAME records correctly. From the custom domains section I want to add a domain from another provider. The domain name must be the www version of the URL i.e.

the custom domain section of the webapp is open in the azure portal, has been entered as the domain name

Once you press next you will be instructed what CNAME record you need to create but since we’ve already done that you can just press add.

the next step instructs you how to create the CNAME, we can ignore this since we've already set it up

The webapp will validate your configuration and if everything has been set up properly it should be validated…

the final page of the custom domain configuration shows the CNAME record with a green tick meaning that the check has been completed and the CNAME record has been validated

You can now close down the custom domains section.

CNAME file in static folder?

I do not remember where I read this, but I also have a file in the static directory of my hugo site that is called CNAME and simply has my domain url in it. I can’t find a reference to it anymore. If you know if this is required or not, please let me know.

screenshot of visual studio code, a file is open called CNAME, it is located at the path ./static/ and has the url '' as the only contents of the file

Time to Test

Your new URL should now work. If everything is successful, both apex and www urls should direct to your site and any other urls should redirect to the same page. For example;


So now you should have the start of a nice blog site using your preferred domain name. You can now write posts in markdown and push them to your repository and they will be published to your site.

2023 update

I have been using Azure Static Webapps for a few years now and identified a few issues. I recently moved to Netlify (not because of these issues I might add) which I’ll write about shortly. In the meantime, here are are the blog posts I wrote about the issues I had with Azure Static Webapps:

  • 404 redirects
  • Environment specific config (I’ve not written this yet)