An Azure service that provides a cloud content delivery network with threat protection.
Azure Front Door Standard stuck at DeploymentStatus NotStarted with HTTP 404
Hello,
I am experiencing an issue with a newly created Azure Front Door Standard configuration.
The Azure Front Door resources are provisioned successfully, but the endpoint and route remain with DeploymentStatus = NotStarted, and the Front Door endpoint returns HTTP 404.
Configuration:
Profile:
dse-frontdoor-prod
Endpoint:
dse-ecosysteme-prod
Route:
dse-web-route
Origin:
zimmer54310.github.io
Origin path:
/demainsite-ecosysteme
Route configuration:
- EnabledState: Enabled
- PatternsToMatch: /*
- SupportedProtocols: Http, Https
- ForwardingProtocol: HttpsOnly
- HttpsRedirect: Enabled
- LinkToDefaultDomain: Enabled
The GitHub Pages origin works correctly when accessed directly and returns HTTP 200.
However, the Azure Front Door endpoint returns HTTP 404.
Azure CLI confirms:
- ProvisioningState: Succeeded
- DeploymentStatus: NotStarted
The Azure Activity Log confirms that the route creation was accepted with HTTP 201 (Created).
Correlation ID:
4e2b8a3c-3553-4259-b326-3e6bb0ab162f
The route resource is:
dse-web-route
The origin, origin group, endpoint and route have all been created successfully.
Azure diagnostics did not detect an issue.
Could you please advise why the Front Door configuration remains in DeploymentStatus = NotStarted and whether this requires intervention on the Azure Front Door service side?
I have not deleted or recreated the configuration because I want to preserve the current state for troubleshooting.
Thank you.
``