Azure Front Door Standard stuck at DeploymentStatus NotStarted with HTTP 404

Pascal ZIMMER 0 Reputation points
2026-09-29T14:51:55.7633333+00:00

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.

``

Azure Front Door
Azure Front Door

An Azure service that provides a cloud content delivery network with threat protection.

0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.