Azure Storage Static Website + Cloudflare

Sixate ships from Azure, accelerates at the edge.

This sample site is designed for a Cloudflare front door with an Azure Storage static website origin, using HTTPS, cache rules, WAF protections, and a Cloudflare-only firewall on the storage account.

Deployment flow Runtime status
Origin Azure Storage Static Website

Static content is served from the Azure `web.core.windows.net` endpoint.

Edge Cloudflare Proxy

Cloudflare provides TLS, caching, WAF, compression, and global edge routing.

Firewall Cloudflare CIDRs Only

The storage account is intended to accept origin traffic only from Cloudflare IP ranges.

Deployment

Use the repo tasks to deploy, publish, and re-lock the origin.

  1. Deploy Azure infrastructure with the VS Code infra task.
  2. Optionally allow your current public IP for a publish window.
  3. Upload this `site` folder into the `$web` container.
  4. Reapply the locked-down infra task to return to Cloudflare-only access.

Headers

Client-side request inspection

This widget reads browser and timing details from the current page load. After Cloudflare is configured, inspect the network response for headers such as `cf-cache-status` and `server`.