Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Deploying your portal with Azure Static Web Apps

Last updated: 8/26/2026
Deploy your portal by connecting your GitHub repository to Azure Static Web Apps. For more information, see the Azure Static Web Apps documentation.

Before you begin

  • You have the relevant rights on Microsoft Azure.
  • You have generated your API Portal repository.

Procedure

  1. Log in to your Azure account and open the Static Web Apps service.
  2. Click Add to create a new static web app.
  3. In the Project details section, select your subscription and resource group.
  4. In the Static Web App details, enter a name for your web app and select a region.
  5. Click Sign in with GitHub to link your GitHub account to your web app and click Authorize Azure-App-Service-Static-Web-Apps.
  6. Once your account is linked, select the organization, repository and branch to use to build your portal.
    In this example the organization is jsmith, the repository is api-portal, and the branch is main.
  7. In the Build Presets drop-down list, select Hugo, then enter the required location details.
    This parameter allows Azure Static Web Apps to automatically use the build configuration provided in the GitHub repository.
    Build Details page.
  8. Click Review + create.
  9. Make sure that your configuration is correct and click Create.

Results

Your portal is deploying and a GitHub Action automatically starts on your repository.
The GitHub action is visible in the Actions tab.
Once it is completed, you can click the URL provided on Azure Static Web Apps to access your portal.
The URL is available in the Overview page.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here