Azure Front Door Standard: Deployment Status Remains NotStarted Despite Successful Provisioning

Question

Azure Front Door Standard: Deployment Status Remains NotStarted Despite Successful Provisioning

AdminYardee-0702 0

Problem description

I am experiencing an issue where my Azure Front Door Standard endpoint and route are stuck in a deployment status of 'NotStarted' since the initial report on September 19, 2026. Despite the provisioning state showing 'Succeeded' for both the endpoint and route, requests to the Front Door URL return HTTP 404 errors with 'x-cache: CONFIG_NOCACHE'. I have verified that the origin (Azure Blob Storage) responds correctly with HTTP 200 directly. I am seeking guidance on why the deployment status isn't progressing and how to resolve the issue to ensure proper routing and accessibility.

Environment

Azure Front Door Standard resource, with one endpoint and default route, located in the specified region (not explicitly provided). The origin is an Azure Blob Storage account.

What I've already tried

I verified the Front Door configuration through Azure CLI, confirming that the route is enabled, linked to the default domain, uses the path pattern '/*', forwards HTTPS traffic, and points to the correct origin. The origin host header matches the Blob Storage hostname, and the health probe points to a valid resource that responds with HTTP 200. I also disabled and re-enabled the endpoint, but this did not change the reported state. Additionally, I tested the Blob Storage origin directly and received HTTP 200, while the Front Door URL continues to return HTTP 404 with 'x-cache: CONFIG_NOCACHE'.

Current status

I am looking for assistance to understand why the deployment status remains 'NotStarted' and to identify steps to complete the deployment successfully so that the Front Door URL serves content as expected.

0 comments

1 answer

Your answer

Answer 1

Hello @AdminYardee-0702

Based on what you've described, you should separate provisioning state from deployment state.

Azure Front Door exposes both properties independently. provisioningState: Succeeded confirms that the ARM resource/configuration was created successfully, while deploymentStatus represents the deployment of that configuration. The current REST API explicitly defines NotStarted, InProgress, Succeeded, and Failed as separate deployment states.

Since your endpoint and route have remained NotStarted since September 19, don't focus further on the Blob origin yet. A healthy origin returning HTTP 200 doesn't explain why the Front Door configuration itself hasn't entered InProgress/Succeeded.

First, capture the complete state directly from ARM:

az afd endpoint show \
  --resource-group <resource-group> \
  --profile-name <profile-name> \
  --endpoint-name <endpoint-name>

az afd route show \
  --resource-group <resource-group> \
  --profile-name <profile-name> \
  --endpoint-name <endpoint-name> \
  --route-name <route-name>

Confirm these values in particular: enabledState, provisioningState, deploymentStatus, linkToDefaultDomain, patternsToMatch, and originGroup

Your /* route, linkToDefaultDomain: Enabled, and correct origin group would normally be the relevant pieces for traffic arriving on the default azurefd.net hostname.

One clarification regarding x-cache: CONFIG_NOCACHE: that header by itself doesn't mean the request failed because Front Door could not reach the Blob origin. CONFIG_NOCACHE indicates that caching isn't enabled/applicable for that route/request. The HTTP 404 is the important symptom here.

Also, check the Activity Log for the Front Door profile around the original deployment time and look specifically for Microsoft.Cdn operations that failed or remained pending. Save the operation/correlation IDs if any are present.

Since you've already disabled/re-enabled the endpoint without changing the state, don't repeatedly delete/recreate it or toggle the configuration. If both resources continue to show:

provisioningState: Succeeded

deploymentStatus: NotStarted

for an extended period, with no configuration operation currently running, open an Azure support request for Azure Front Door / Microsoft.Cdn and ask them to investigate the configuration deployment state on the service side. Include the profile resource ID, endpoint and route resource IDs, deployment timestamps, Activity Log correlation IDs, and the x-azure-ref header from one of the 404 responses.

Microsoft has separate troubleshooting guidance for Front Door 404 responses, but the usual routing-rule scenario is less convincing here because you've already confirmed that the route exists, is enabled, uses /*, and is linked to the default domain.

If you post the sanitized output from az afd endpoint show and az afd route show, particularly those six properties above, we can check whether anything at the ARM configuration level is still preventing deployment.

References:

Azure Front Door – AFD Endpoints Get REST API

Azure Front Door – Routes Get REST API

Azure Front Door troubleshooting documentation

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.