on:  Static websites
Search
List of notes
Published: August 2025
This article is part of a series on: Configuring Azure static web apps.
  1. Create a new Static Web App
  2. Use a custom domain
  3. Authorisation configuration
  4. Blocking an authentication provider
  5. Become co-owner of a subscription
  6. API configuration

Create a new Static Web App

Most descriptions show how to create a new Static Web App as click-through and assume that the source of the website is in a Github or Azure DevOps git repository. But the source actually is not relevant for the creation of the Static Web App proper.Creating a Static Web App in this way fails if there are authorization issues, e.g., if the Azure organisation of the Static Web App is a different one than the one the git repository is part of. That is confusing the first time this happens, as it suggests that you miss out on a lot of functionality. That is not the case: the portal tries to do two things at once that you easily can do one after the other.Here is the description for the first step: creating the Static Web App.

To create the Static Web App:

  • Go to the Static Web App section of the Azure portal.
  • Create a new app. Things to pay attention to in 2025:
    • Provide a name for the web app. This will only be visible in the Azure Portal.
    • Subscription is Pay-as-you-go, plan is Free: for hobby or personal projects. You may be asked to create the subscription of you have never done that.
    • Deployment details: choose Other; we are going to configure that in the next step.
    • Deployment authorization policy: Deployment token.
    • Azure Functions and staging details: choose West Europe. This is apparently only used for environments other than the production one, and for the API (Azure Functions) if that is part of the website.

This will create the Production environment, which is inactive at this point as there is nothing published yet. If you already know that you're going to need multiple environments: you cannot create a new environment via the portal, that has to be done by publishing to the new environment first. Once it has been created, it is available in the portal as well.

You can proceed with assign a custom domain or with publish to a Static Web App.