Azure Front Door Standard - DeploymentStatus stuck at NotStarted, edge never publishes configuration

Question

Azure Front Door Standard - DeploymentStatus stuck at NotStarted, edge never publishes configuration

Angel Alday 20

We are experiencing a persistent Azure Front Door (Standard) deployment issue.

The Front Door profile provisioningState is Succeeded, but all data-plane resources

(endpoint, routes, origin groups, origins) remain permanently in DeploymentStatus = NotStarted.

As a result:

Requests to the default *.z01.azurefd.net hostname always return HTTP 404
Response header shows: x-cache: CONFIG_NOCACHE
Edge error page says: "We weren't able to find your Azure Front Door Service configuration"

This issue persists across:

Multiple endpoints (original endpoint deleted and a new endpoint recreated)
Valid routes (/resolve, /resolve/*)
Valid origin groups and origins
No WAF / security policies attached
No errors or warnings in Activity Log
Profile SKU: Standard_AzureFrontDoor

The issue has been stable for many hours and does not resolve with time or configuration changes.

It appears the configuration is not being published to the edge (control plane OK, data plane not updated).

Please investigate and repair the edge deployment for this Front Door profile or advise remediation.

0 comentarios

Respuesta aceptada por el autor de la pregunta

0 respuestas adicionales

Su respuesta

Answer 1

Hi @ Angel Alday

Welcome to Microsoft Q&A Platform.

The error you encountered is not related to DeploymentStatus = NotStarted. If you are receiving an HTTP 404 error when accessing the default Azure Front Door (AFD) endpoint may be due to AFD Route and Origin configuration.

The Front Door configuration is active, routes are matched, and the origin is selected correctly. The issue is caused by backend path handling when using , where the constructed backend request does not match an existing endpoint on the origin. Adjusting the originPath or route patterns resolves the issue.

To resolve the issue configure AFD origin path and pattern to match like below

AFD Route Config:

/* means it will accept any request path, such as /api/health

Imagen del usuario Origin Group Config: User Image Result:

User Image

x-cache: CONFIG_NOCACHE does not mean the configuration is missing, t simply indicates the response was **not served from cache. Pleaseand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.