Azure Static Website

The Azure Static Website template scaffolds a Pulumi project that stores site files in an Azure Blob Storage account configured for static website hosting and serves them through an Azure CDN Endpoint for low-latency delivery, caching, and HTTPS. The template ships with placeholder web content so the project deploys end to end out of the box.

Using this template

To use this template to deploy a website of your own, make sure you’ve installed Pulumi and configured your Azure credentials, then create a new project using the template in the language of your choice:

$ mkdir my-site && cd my-site
$ pulumi new static-website-azure-typescript

Alternatively, you can create and configure a new project with this template (static-website-azure-typescript) in Pulumi Cloud.

$ mkdir my-site && cd my-site
$ pulumi new static-website-azure-python

Alternatively, you can create and configure a new project with this template (static-website-azure-python) in Pulumi Cloud.

$ mkdir my-site && cd my-site
$ pulumi new static-website-azure-go

Alternatively, you can create and configure a new project with this template (static-website-azure-go) in Pulumi Cloud.

$ mkdir my-site && cd my-site
$ pulumi new static-website-azure-csharp

Alternatively, you can create and configure a new project with this template (static-website-azure-csharp) in Pulumi Cloud.

$ mkdir my-site && cd my-site
$ pulumi new static-website-azure-yaml

Alternatively, you can create and configure a new project with this template (static-website-azure-yaml) in Pulumi Cloud.

Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a finished project that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in index.js index.ts __main__.py main.go Program.cs Program.fs Program.vb App.java Pulumi.yaml for a closer look.

Deploying the project

The template requires no additional configuration. Once the new project is created, you can deploy it immediately with pulumi up:

$ pulumi up

When the deployment completes, Pulumi exports the following stack output values:

originHostname

The provider-assigned hostname of the Azure Blob Storage container.

originURL

The fully-qualified HTTP URL of the storage container endpoint.

cdnHostname

The provider-assigned hostname of the Azure CDN. Useful for creating CNAME records to associate custom domains.

cdnURL

The fully-qualified HTTPS URL of the Azure CDN.

Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed cdnURL, for example, can be used from the command line to open the newly deployed website in your favorite web browser:

$ open $(pulumi stack output cdnURL)

Customizing the project

Projects created with the Static Website template expose the following configuration settings:

path

The path to the folder containing the files of the website. Defaults to www, which is the name (and relative path) of the folder included with the template.

indexDocument

The file to use for top-level pages. Defaults to index.html.

errorDocument

The file to use for error pages. Defaults to error.html.

All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with pulumi config set:

Using your own web content

If you already have a static website you’d like to deploy on Azure with Pulumi, you can do so either by replacing placeholder content in the www folder or by configuring the stack to point to another folder on your computer with the path setting:

$ pulumi config set path ../my-existing-website/build
$ pulumi up

Cleaning up

You can cleanly destroy the stack and all of its infrastructure with pulumi destroy:

$ pulumi destroy

Learn more

• Browse other architecture templates in the Templates gallery.
• Explore the Azure Native provider API docs in the Pulumi Registry.
• Walk through Pulumi from the ground up in Pulumi Tutorials.
• Read the latest Azure posts on the Pulumi blog.