Azure Static Web Apps: vendor profile

In short

Azure Static Web Apps serves index.html for unmatched paths through navigationFallback, while responseOverrides set what a 404 returns, so a client-side app can hide real 404s. The pages read describe no prerendering for crawlers. The Dedicated plan was retired effective 2025-10-31, and the Free plan allows 3 staging environments.

At a glance

standards.txt azure-static-web-apps

llms-txt               = no statement
markdown-negotiation   = no statement
markdown-twin          = no statement
initial-html           = no statement
real-404               = partial
vary-accept            = no statement

0 supports, 1 partial or announced, 5 no statement.

Azure Static Web Apps Host, CDN or edge product

Microsoft's hosting for static front ends with managed Azure Functions APIs; a navigationFallback setting serves index.html for unmatched paths, and responseOverrides set what a 404 returns.

Type: Host, CDN or edge product
Operator, as the facts below state it: Microsoft
Home page: azure.microsoft.com/products/app-service/static, answered HTTP 200 on 2026-11-05
Last read: 5 November 2026

What it does for this layer

Microsoft describes Azure Static Web Apps as a service that deploys full stack web apps to Azure from a code repository, rebuilding on every push to a watched GitHub or Azure DevOps branch. [primary source] source, read 5 November 2026.
Microsoft says static web apps on the service are commonly built with Angular, React, Svelte, Vue or Blazor where server-side rendering is not required. [primary source] source, read 5 November 2026.
The navigationFallback section in staticwebapp.config.json returns a rewrite target such as /index.html for static file requests that match no deployed file, with an exclude list for paths that should not fall back. [primary source] source, read 5 November 2026.
Route rules in Azure Static Web Apps are not applied to requests that trigger navigationFallback. [primary source] source, read 5 November 2026.
The responseOverrides section defines a custom response when the server would otherwise return an error code, and Microsoft's examples rewrite 404 to a custom 404.html. [primary source] source, read 5 November 2026.
Microsoft's example configuration shows a disabled auth route returning a 404 that then falls back to /index.html with a 200 status code. [primary source] source, read 5 November 2026.
A globalHeaders section in Azure Static Web Apps adds HTTP headers to every response unless a route header rule overrides them. [primary source] source, read 5 November 2026.
Azure Static Web Apps comes in Free and Standard plans; the Free plan allows 250 MB per app, 3 staging environments and 2 custom domains, and the Dedicated plan was retired effective 2025-10-31. [primary source, 2025-10-31] source, read 5 November 2026.

Products and plans

Plans and prices as the vendor's own pages showed them on the date read.
Product	What it is	Price	As of	Source
Azure Static Web Apps	Static hosting with Git-triggered builds, managed Functions APIs, routing rules, fallbacks and response overrides.	Free tier, paid plans above it Free plan for personal projects; Standard plan cost is on the Azure pricing page	2026-11-05	source

Standards

The six standards this site tracks; no statement means the pages read said nothing.
Standard	Status	What the vendor's pages say	Source
llms-txt	no statement	No llms.txt feature in the Static Web Apps pages read.	none
markdown-negotiation	no statement	No Accept-header markdown feature in the pages read.	none
markdown-twin	no statement	No markdown copy feature in the pages read.	none
initial-html	no statement	Microsoft frames the service around apps where server-side rendering is not required; HTML is whatever the build emits.	none
real-404	partial	Without navigationFallback a missing file can return a 404 overridden by responseOverrides; with the fallback, unmatched paths get index.html.	source
vary-accept	no statement	Not covered in the pages read.	none

Checks on its own site

Plain-fetch checks ran on https://azure.microsoft.com/products/app-service/static; the Ora and Cloudflare scores cover the whole host azure.microsoft.com.

Readings of azure.microsoft.com, the vendor's own website, which describe that site and not the product.
Reading	Result	Date
Home page request	HTTP 200; H1 in the initial HTML: yes; 1,421 words; 0 JSON-LD blocks	2026-11-05
Request with Accept: text/markdown	HTTP 200, text/html, Vary: Accept-Encoding	2026-11-05
/llms.txt at the host root	HTTP 404, text/html, 92 KB	2026-11-05
A made-up path	HTTP 302, redirect to https://azure.microsoft.com/en-us/agent-ready-check-ydxgmirf, then HTTP 404	2026-11-05
Ora score, cached	51, grade C	2026-05-11
Cloudflare keyless scan	20, L1 Basic Web Presence	2026-11-05
Shared crawl row	outside the ranked slice; home page HTTP 200; H1 in the HTML: yes; 2,630 words; JSON-LD types: none; answers markdown: no; made-up path HTTP 404; llms.txt valid: no	2026-11-04

What it does not do

Azure Static Web Apps does not prerender client-side apps for crawlers or agents in the pages read; navigationFallback hands every unmatched path to index.html.

Related pages on this site

Sources

Azure Static Web Apps: home page https://azure.microsoft.com/products/app-service/static, read 5 November 2026
What is Azure Static Web Apps? | Microsoft Learn https://learn.microsoft.com/en-us/azure/static-web-apps/overview, read 5 November 2026
Configure Azure Static Web Apps | Microsoft Learn https://learn.microsoft.com/en-us/azure/static-web-apps/configuration, read 5 November 2026
Azure Static Web Apps hosting plans | Microsoft Learn https://learn.microsoft.com/en-us/azure/static-web-apps/plans, read 5 November 2026

Last reviewed 5 November 2026