Azure Front Door endpoint deployment stuck at "NotStarted" - all routes provisioned but deployment won't start

Bentley cook 5 Reputation points
2025-12-01T22:35:39.0066667+00:00

Problem

Azure Front Door endpoint deployment status is stuck at "NotStarted" despite all resources being successfully provisioned. The managed certificate cannot provision because deployment hasn't started, making the site inaccessible.

Environment

  • SKU: Standard_AzureFrontDoor

Current Status

Working:

  • All 4 routes created and enabled - ProvisioningState: "Succeeded"
  • All origin groups exist and are configured
  • All origins configured
  • Custom domain exists
  • DNS correctly configured (CNAME points to Front Door endpoint)

Blocked:

  • Endpoint deployment status: "NotStarted" (stuck for extended period)
  • Custom domain validation: "Pending"
  • Managed certificate: Not provisioned (secret: null)
  • Site inaccessible due to SSL certificate error

What I've Tried

  1. Toggled routes enabled/disabled to trigger deployment
  2. Recreated custom domain
  3. Verified DNS configuration (CNAME correct)
  4. Made small configuration changes to force refresh
  5. All resources show "Succeeded" provisioning state

Additional Context

  • Azure portal shows message about "AFD Service Management restrictions" and extended propagation times (up to 45 minutes)
  • Deployment has been stuck well beyond the expected propagation window
  • This appears to be a platform-level issue, not a configuration problem

Question

Has anyone encountered this issue? Are there any known workarounds or ways to manually trigger Front Door endpoint deployment? Should I open a support ticket, or is there something I'm missing in the configuration?

Terraform Configuration

Using Terraform with azurerm_cdn_frontdoor_endpoint and azurerm_cdn_frontdoor_route resources. All resources provision successfully, but deployment never starts.

Azure Front Door
Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Thanmayi Godithi 2,455 Reputation points Microsoft External Staff Moderator
    2025-12-02T03:47:24.5433333+00:00

    Hi @Bentley cook,

    Thank you for reaching out on Microsoft Q&A forum.

    This appears to be a cosmetic bug. As long as the provisioning state shows as "Succeeded", you can ignore the deployment status, and it will not impact the AFD in any way.

    Could you please share the details requested over "Private message".

    You can find the "Private message" option right under your question.

    User's image

    Kindly let us know if the above helps or you need further assistance on this issue.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".


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.