Azure Front Door rule sets stuck in deploymentStatus=NotStarted — geo‑routing rules not executing at edge

Anatoly Bulatov 20 Reputation points
2026-09-22T07:02:44.5866667+00:00

Two production rule sets attached to Azure Front Door routes are not deploying to the edge. Their deploymentStatus remains NotStarted indefinitely, even though provisioningState is Succeeded.

As a result:

RouteConfigurationOverride actions never execute

Requests fall through to the default origin group

Geo‑routing based on jurisdiction headers does not work

All traffic is pinned to eastus2, ignoring regional origin groups

This is not a configuration error. We have already simplified conditions, re-saved rules, detached/re-attached rule sets, and validated AGC health. Only rule set deployment is stuck.

We request backend redeploy / sync of the affected rule sets and confirmation of the root cause.

Azure Front Door
Azure Front Door

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

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Taz 10,126 Reputation points MVP Volunteer Moderator
    2026-09-22T08:26:36.6733333+00:00

    Hi Anatoly,

    provisioningState: Succeeded and deploymentStatus: NotStarted are separate states in Azure Front Door. Microsoft’s API documentation confirms that deploymentStatus can be NotStarted, InProgress, Succeeded, or Failed.

    If the rule sets have remained NotStarted indefinitely and the rules are not executing at the edge, this points to a deployment issue rather than the rule conditions themselves.

    I would check the Front Door Activity Log for any failed or pending Microsoft.Cdn operations. If there is no active operation and the status remains NotStarted, open an Azure Support request for Front Door and provide the profile, rule set IDs, timestamps, and Activity Log correlation IDs. Microsoft can check and resync the edge configuration from the service side.

    Was this answer helpful?

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.